@czi-sds/mcp 0.16.0 → 0.17.0

package/data/zeroheight-exports/Field-Inputs.md

@@ -1,1405 +0,0 @@
-# Field Inputs
-
-Field Inputs are elements that allow users to type within them, providing an area for users to enter content and information or perform a search.
-
-## Overview
-
-## Field Input Variants
-
-| There are two Field Input variants available for designers to use—Search Inputs allow users to enter text to perform a search and Text Inputs provide a free-form space for users to type in information as needed. Follow the usage criteria accompanying each variant as a guide for selecting the correct Text Input for any given use case. |     | **Jump to variant:** Rounded Search Square Search Text |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | ------------------------------------------------------ |
-
----
-
-## Rounded Search Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ GEN EPI Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ---------------------- |
-
-Used in CZ GEN EPI for top-level searches and when searching within Tables.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-### Rounded Search Input Intent States
-
-The `intent` prop is used to communicate the response state of the user's search inquiry.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete search.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete search.
-
-Use `intent: warning` to communicate when a user needs to be alerted that their search needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
----
-
-### Rounded Search Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Rounded Search Input spacing**
-
----
-
----
-
-## Square Search Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ GEN EPI Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ---------------------- |
-
-Used in CZ GEN EPI for searches constrained to the element the Input is placed within such as Dropdown Menus or Forms.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-### Square Search Input Intent States
-
-The `intent` prop is used to communicate the response state of the user's search inquiry.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete search.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete search.
-
-Use `intent: warning` to communicate when a user needs to be alerted that their search needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
----
-
-### Square Search Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Square Search Input spacing**
-
----
-
----
-
-## Text Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ GEN EPI Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ---------------------- |
-
-### Text Field Input
-
-The Text Field Input is meant to fit one line of text and should be only used when there is a limited amount or a single line's worth of content intended for the user to input.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-### Text Area Input
-
-The Text Area Input is meant to fit multiple lines of text and should be used when there is the potential that the user will want or need to input more than a single line's worth of content.
-
-It includes a handle in the bottom right corner that the user can grab and drag to expand its size.
-
-It can be set to accept a specific number of characters in case there is a need to limit how much content the user can enter.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-### Text Input Intent States
-
-The `intent` prop is used to communicate the response state of the text the user has input.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete input.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete input.
-
-Use `intent: warning` to communicate when a user needs to be alerted that the content they've input needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
----
-
-### Text Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Text Input spacing**
-
----
-
-## Code
-
-## Field Input Components
-
-| Below you will find an interactive Storybook iframe for Field Inputs. Tabs within each iframe provide a different set of tools: The Controls tab allows you to see and adjust all available props. The Actions tab shows you data displayed by event handler arguments. |     | **Jump to component:** InputSearch InputText |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -------------------------------------------- |
-
----
-
-> These components appear as they are in the default SDS codebase. Once imported into the CZ GEN EPI codebase, use a theme file to enable the CZ GEN EPI visual appearance customization.
-
-### InputSearch
-
-Storybook
-
----
-
-### InputText
-
-Storybook
-
----
-
-Field Inputs are elements that allow users to type within them, providing an area for users to enter content and information or perform a search.
-
-## Overview
-
-## Field Input Variants
-
-| There are two Field Input variants available for designers to use—Search Inputs allow users to enter text to perform a search and Text Inputs provide a free-form space for users to type in information as needed. Follow the usage criteria accompanying each variant as a guide for selecting the correct Text Input for any given use case. |     | **Jump to variant:** Rounded Search Square Search Text |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | ------------------------------------------------------ |
-
----
-
-## Rounded Search Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ ID Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ----------------- |
-
-Used in CZ ID for top-level searches and when searching within Tables.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-### Rounded Search Input Intent States
-
-The `intent` prop is used to communicate the response state of the user's search inquiry.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete search.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete search.
-
-Use `intent: warning` to communicate when a user needs to be alerted that their search needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
----
-
-### Rounded Search Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Search spacing**
-
----
-
----
-
-## Square Search Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ ID Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ----------------- |
-
-Used in CZ ID for searches constrained to the element the Input is placed within such as Dropdown Menus or Forms.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-### Square Search Input Intent States
-
-The `intent` prop is used to communicate the response state of the user's search inquiry.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete search.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete search.
-
-Use `intent: warning` to communicate when a user needs to be alerted that their search needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
-**InputSearch**
-
----
-
----
-
-### Square Search Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Square Search Input spacing**
-
----
-
----
-
-## Text Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In CZ ID Codebase |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ----------------- |
-
-### Text Field Input
-
-The Text Field Input is meant to fit one line of text and should be only used when there is a limited amount or a single line's worth of content intended for the user to input.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-### Text Area Input
-
-The Text Area Input is meant to fit multiple lines of text and should be used when there is the potential that the user will want or need to input more than a single line's worth of content.
-
-It includes a handle in the bottom right corner that the user can grab and drag to expand its size.
-
-It can be set to accept a specific number of characters in case there is a need to limit how much content the user can enter.
-
-Click on each state below to enter inspect view and get details on its code attributes and any global styles it uses.
-
-| **Default** | **Hover** | **Focus** | **Disabled** |
-| ----------- | --------- | --------- | ------------ |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-### Text Input Intent States
-
-The `intent` prop is used to communicate the response state of the text the user has input.
-
-Use `intent: default` to communicate when a user has entered an accepted or complete input.
-
-Use `intent: error` to communicate when a user has entered an incorrect or incomplete input.
-
-Use `intent: warning` to communicate when a user needs to be alerted that the content they've input needs attention.
-
-| **Default** | **Error** | **Warning** |
-| ----------- | --------- | ----------- |
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
-**InputText**
-
----
-
----
-
-### Text Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Text Input spacing**
-
----
-
-## Code
-
-## Field Input Components
-
-| Below you will find an interactive Storybook iframe for Field Inputs. Tabs within each iframe provide a different set of tools: The Controls tab allows you to see and adjust all available props. The Actions tab shows you data displayed by event handler arguments. |     | **Jump to component:** InputSearch InputText |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -------------------------------------------- |
-
----
-
-### InputSearch
-
-Storybook
-
----
-
-### InputText
-
-Storybook
-
----
-
-Field Inputs are elements that allow users to type within them, providing an area for users to enter content and information or perform a search.
-
-## Guidelines
-
-## Field Input Components
-
-| There are two Field Input components available to use—Search Inputs allow users to enter text to perform a search and Text Inputs provide a free-form space for users to type in information as needed. |     | **Jump to variant:** Search Input Text Input |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -------------------------------------------- |
-
-### Visual Preview
-
-**Preview_Guidelines_InputSearch**
-
----
-
-**Preview_Guidelines_InputText**
-
----
-
----
-
-## Search Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In Code |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ------- |
-
-### Search Input Styles
-
-**InputSearch_Styles_Rounded**
-
----
-
-**InputSearch_Styles_Square**
-
----
-
----
-
-### Live Instance
-
-Interact with the live instance below and adjust the available props to better conceptualize how it will appear in product:
-
-Default
-
----
-
-### Search Input – Rounded
-
-Use Search Input – Rounded as part of top-level or primary application searches such as instances where the user will be searching across the entire product or platform.
-
-After users enter text into the Search field, an `XmarkCircle` icon appears; if clicked the field is reset to default.
-
-| Default | Hover | Focus | Default (user input) | Disabled |
-| ------- | ----- | ----- | -------------------- | -------- |
-
-**InputSearch_Rounded_Default**
-
----
-
-**InputSearch_Rounded_Hover**
-
----
-
-**InputSearch_Rounded_Focus**
-
----
-
-**InputSearch_Rounded_User Input**
-
----
-
-**InputSearch_Rounded_Disabled**
-
----
-
----
-
-### Search Input – Square
-
-Use Search Input – Square for searches constrained to the element the Input is placed within such as when used in Dropdown Menus or Panels, or within the body or main content area of applications.
-
-After users enter text into the Search field, an `XmarkCircle` icon appears; if clicked the field is reset to default.
-
-| Default | Hover | Focus | Default (user input) | Disabled |
-| ------- | ----- | ----- | -------------------- | -------- |
-
-**InputSearch_Square_Default**
-
----
-
-**InputSearch_Square_Hover**
-
----
-
-**InputSearch_Square_Focus**
-
----
-
-**InputSearch_Square_User Input**
-
----
-
-**InputSearch_Square_Disabled**
-
----
-
----
-
-### Search Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Search spacing**
-
----
-
----
-
-### Intent Variations
-
-Use Default to communicate that the user has yet to enter a response or the response is valid, Negative to communicate when a user has entered an incorrect or incomplete response, and Notice when a user's response needs attention.
-
-Optionally, Intent Messages can be displayed to further communicate why a Negative or Notice intent was triggered. For more information see Intents.
-
-Each intent is demonstrated below using the Rounded variant for reference. Regardless of variant, the colors used are the same:
-
-| Default | Negative | Negative + Intent Message | Notice | Notice + Intent Message |
-| ------- | -------- | ------------------------- | ------ | ----------------------- |
-
-**InputSearch_Intent_Default**
-
----
-
-**InputSearch_Intent_Negative**
-
----
-
-**InputSearch_Intent_Negative + Message**
-
----
-
-**InputSearch_Intent_Notice**
-
----
-
-**InputSearch_Intent_Notice + Message**
-
----
-
----
-
-## Text Input
-
-|     | In Figma |     |     | Meets Accessibility |     |     | In Code |
-| --- | -------- | --- | --- | ------------------- | --- | --- | ------- |
-
-### Text Input Types
-
-**Text Input_Field**
-
----
-
-**Text Input_Area**
-
----
-
----
-
-### Live Instance
-
-Interact with the live instance below and adjust the available props to better conceptualize how it will appear in product:
-
-Default
-
----
-
-### Text Input – Field
-
-Text Input – Field is designed to fit one line of text and should be only used when there is a limited amount or a single line's worth of content intended for the user to input.
-
-| Default | Hover | Focus | Default (user input) | Disabled |
-| ------- | ----- | ----- | -------------------- | -------- |
-
-**TextInput_Field_Default**
-
----
-
-**TextInput_Field_Hover**
-
----
-
-**TextInput_Field_Focus**
-
----
-
-**TextInput_Field_User Input**
-
----
-
-**TextInput_Field_Disabled**
-
----
-
----
-
-### Text Input – Area
-
-Text Input – Area is meant to fit multiple lines of text and should be used when there is the potential that the user will want or need to input more than a single line's worth of content.
-
-It includes a handle in the bottom right corner that the user can grab and drag to expand its size.
-
-It can be set to accept a specific number of characters in case there is a need to limit how much content the user can enter.
-
-| Default | Hover | Focus | Default (user input) | Disabled |
-| ------- | ----- | ----- | -------------------- | -------- |
-
-**TextInput_Area_Default**
-
----
-
-**TextInput_Area_Hover**
-
----
-
-**TextInput_Area_Focus**
-
----
-
-**TextInput_Area_User Input**
-
----
-
-**TextInput_Area_Disabled**
-
----
-
----
-
-### Text Input Spacing
-
-These rules establish how much margin should exist between and around elements.
-
-**Text Input spacing**
-
----
-
----
-
-### Text Input Intent Variations
-
-Use Default to communicate that the user has yet to enter a response or the response is valid, Negative to communicate when a user has entered an incorrect or incomplete response, Notice when a user's response needs attention, and Positive when a user's response is accepted or correct.
-
-Optionally, Intent Messages can be displayed to further communicate why a Negative, Notice, or Positive intent was triggered. For more information see Intents.
-
-| Default | Negative | Negative + Intent Message | Notice | Notice + Intent Message | Positive | Positive + Intent Message |
-| :-----: | :------: | ------------------------- | :----: | ----------------------- | :------: | ------------------------- |
-
-**InputText_Field_Default**
-
----
-
-**InputText_Field_Negative + Message**
-
----
-
-**InputText_Field_Negative**
-
----
-
-**InputText_Field_Notice**
-
----
-
-**InputText_Field_Notice + Message**
-
----
-
-**InputText_Field_Positive**
-
----
-
-**InputText_Field_Positive + Message**
-
----
-
-**InputText_Area_Default**
-
----
-
-**InputText_Area_Negative**
-
----
-
-**InputText_Area_Negative + Message**
-
----
-
-**InputText_Area_Notice**
-
----
-
-**InputText_Area_Notice + Message**
-
----
-
-**InputText_Area_Positive**
-
----
-
-**InputText_Area_Positive + Message**
-
----
-
-## Code
-
-## Control Input Components
-
-| There are two Field Input components available to use—`InputSearch` allows users to enter text to perform a search and `InputText` provide a free-form space for users to type in information as needed. |     | **Jump to component:** InputSearch InputText |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -------------------------------------------- |
-
-### Visual Preview
-
-**Preview_Code_InputSearch**
-
----
-
-**Preview_Code_InputText**
-
----
-
-> **Note:** The code examples below must install dependencies before displaying and may take extra time to load
-
----
-
-## InputSearch
-
-### SDS Source Code
-
-The component's source code in the SDS codebase can be found here.
-
-### SDS vs MUI
-
-SDS's `InputSearch` is built on MUI's `TextField` component, with `type="search"`. It also has the SDS "search" icon automatically included, aligned to the right end of the field.
-
-The following props are available to MUI's `TextField` component, but do not work the same way (or at all) for SDS's `InputSearch` component:
-
-- **`variants`\*\***:\*\* SDS's `InputSearch` component is not set up to support values for this prop (aside from `outlined`, `InputSearch` default), and using other values available to MUI (`filled`, `standard`) may result in unreliable outputs
-- **`size`\*\***:\*\* SDS's `InputSearch` component is not set up to support values for this prop (aside from `small`, `InputText`'s default), and using other values available to MUI (`medium`, `large`) may not have reliable outputs
-- **`required`\*\***:\*_ SDS's `InputSearch` does not render the expected asterisk (_) following the label when this prop is `true`
-- **`select`\*\***:\*\* SDS's `InputSearch` is not set up to support this boolean prop
-- **`hiddenLabel`\*\***:\*\* The `label` ("Search", by default) for SDS's component is included within the search field, not outside of it, and the MUI `hiddenLabel` prop will not hide the label
-
-The following functionality is available to both MUI's `TextField` component and SDS's `InputText` component, but SDS uses different prop names, shown below:
-
-- **`intent`\*\***:\*\* This prop is the way you can set colors for SDS's `InputText`, based on its error state. It takes `default` (default, gray), `error`, or `warning` as values. The related MUI-color-setting prop, `color`, has no effect for `InputText` in SDS.
-
-SDS's `InputSearch` has an additional `sdsStyle` prop to help with setting SDS-specific styles, which takes `square` (default) or `rounded` as values.
-
-### MUI Documentation
-
-Documentation for the underlying MUI `TextField` component can be found here.
-
-### Props
-
-Any custom SDS props and MUI props required for implementation are found on the table below. See the MUI documentation for additional optional props.
-
-| Name           | Type          | Default                                      | Description                                                                                            |
-| -------------- | ------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------- |
-| `disabled`     | `boolean`     | `false`                                      | When set to `true`, the component becomes disabled and cannot be interacted with.                      |
-| `handleSubmit` | `func`        | `function(value: string) => void`            | This function is called when the Search icon is clicked, allowing user to handle the search operation. |
-| `id`           | `string`      | `-`                                          | Specifies the unique `id` for the input element, needed for accessibility.                             |
-| `intent`       | `"default"` ` | "negative"` `                                | "notice"` `                                                                                            | "positive"`                                                                                  | `"default"` | Alters the border color and visual intent of the search input. |
-| `label`        | `string`      | `-`                                          | Although hidden, this `label` is provided for accessibility purposes.                                  |
-| `onChange`     | `func`        | `function(event: React.ChangeEvent) => void` | Defines the action to be taken when the input value changes.                                           |
-| `placeholder`  | `string`      | `"Search"`                                   | Sets the `placeholder` text displayed within the input element.                                        |
-| `sdsStyle`     | `"rounded"` ` | "square"`                                    | `"square"`                                                                                             | Determines the visual style of the component, with options for `rounded` or `square` design. |
-| `value`        | `string`      | `-`                                          | The value of the `input` element, required for a controlled component.                                 |
-
-### Code examples
-
-#### **Default InputSearch**
-
-This example has the minimum props needed for the `InputSearch` component.
-
-**/styles.css**
-
-```css
-body {
-  font-size: 13px;
-  font-weight: 400;
-  letter-spacing: 0.08px;
-  line-height: 20px;
-  text-transform: none;
-  font-family: "Inter", sans-serif;
-}
-
-h1 {
-  font-size: 1.5rem;
-}
-
-.app {
-  padding: 20px;
-}
-```
-
-**tsconfig.json**
-
-```json
-{
-  "include": ["./**/*"],
-  "compilerOptions": {
-    "strict": true,
-    "esModuleInterop": true,
-    "lib": ["dom", "es2015"],
-    "jsx": "react-jsx"
-  }
-}
-```
-
-**/App.tsx**
-
-```tsx
-import { InputSearch } from "@czi-sds/components";
-import { Box } from "@mui/material";
-import "./styles.css";
-
-function App() {
-  return (
-    <div className="app">
-      <Box sx={{ width: 300 }}>
-        <InputSearch id="search-input" label="search" placeholder="Search" />
-      </Box>
-    </div>
-  );
-}
-
-export default App;
-```
-
-**/index.tsx**
-
-```tsx
-import React from "react";
-import { createRoot } from "react-dom/client";
-import { ThemeProvider as EmotionThemeProvider } from "@emotion/react";
-import { StyledEngineProvider, ThemeProvider } from "@mui/material/styles";
-import { Theme } from "@czi-sds/components";
-import CssBaseline from "@mui/material/CssBaseline";
-import useMediaQuery from "@mui/material/useMediaQuery";
-
-import App from "./App";
-
-const container = document.getElementById("root");
-const root = createRoot(container!);
-
-const RootApp = () => {
-  const prefersDarkMode = useMediaQuery("(prefers-color-scheme: dark)");
-  const theme = prefersDarkMode ? Theme("dark") : Theme("light");
-
-  return (
-    <StyledEngineProvider injectFirst>
-      <ThemeProvider theme={theme}>
-        <EmotionThemeProvider theme={theme}>
-          <CssBaseline />
-          <App />
-        </EmotionThemeProvider>
-      </ThemeProvider>
-    </StyledEngineProvider>
-  );
-};
-
-root.render(
-  <React.StrictMode>
-    <RootApp />
-  </React.StrictMode>
-);
-```
-
-**/public/index.html**
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <link rel="preconnect" href="https://fonts.googleapis.com" />
-    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
-    <link
-      href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"
-      rel="stylesheet"
-    />
-    <link
-      href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&display=swap"
-      rel="stylesheet"
-    />
-  </head>
-  <body>
-    <div id="root"></div>
-  </body>
-</html>
-```
-
-**/package.json**
-
-```json
-{
-  "dependencies": {
-    "react": "^18.0.0",
-    "react-dom": "^18.0.0",
-    "react-scripts": "^4.0.0"
-  },
-  "devDependencies": {
-    "@types/react": "^18.0.0",
-    "@types/react-dom": "^18.0.0",
-    "typescript": "^4.0.0"
-  },
-  "main": "/index.tsx"
-}
-```
-
----
-
----
-
-## InputText
-
-### SDS Source Code
-
-The component's source code in the SDS codebase can be found here.
-
-### SDS vs MUI
-
-Like SDS's `InputSearch` (which is also built upon the same MUI component), the following props and options do not work the same way (or at all) for SDS's `InputText` component even though they are available to MUI's `TextField` component.
-
-- **`variants`\*\***:\*\* SDS's `InputText` component is not set up to support values for this prop (aside from `outlined`, `InputText`'s default), and using other values available to MUI (`filled`, `standard`) may result in unreliable outputs
-- **`size`\*\***:\*\* SDS's `InputText` component is not set up to support values for this prop (aside from `small`, `InputText`'s default), and using other values available to MUI (`medium`, `large`) may not have reliable outputs
-- **`required`\*\***:\*_ SDS's `InputText` does not render the expected asterisk (_) following the label when this prop is `true`
-- **`select`\*\***:\*\* SDS's `InputText` is not set up to support this boolean prop
-
-The following functionality is available to both MUI's `TextField` component and SDS's `InputText` component, but SDS uses different prop names, shown below:
-
-- **`sdsType`\*\***:\*\* This is the SDS-equivalent of MUI's boolean `multiline` prop, and takes `textField` (default) or `textArea` as values
-- **`hideLabel`\*\***:\*\* This is the SDS-equivalent of the `hiddenLabel` prop used in MUI; both are boolean with the default not including them (value of `false`)
-- **`intent`\*\***:\*\* This prop is the way you can set colors for SDS's `InputText`, based on its error state. It takes `default` (default, gray), `error`, or `warning` as values. The related MUI-color-setting prop, `color`, has no effect for `InputText` in SDS.
-
-### MUI Documentation
-
-Documentation for the underlying MUI `TextField`component can be found here.
-
-### Props
-
-Any custom SDS props and MUI props required for implementation are found on the table below. See the MUI documentation for additional optional props.
-
-| Name          | Type            | Default       | Description                                                                       |
-| ------------- | --------------- | ------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ----------- | -------------------------------------------------------------- |
-| `disabled`    | `boolean`       | `false`       | When set to `true`, the component becomes disabled and cannot be interacted with. |
-| `hideLabel`   | `boolean`       | `false`       | If `true`, the label is hidden.                                                   |
-| `id`          | `string`        | `-`           | Specifies the unique `id` for the input element, needed for accessibility.        |
-| `intent`      | `"default"` `   | "negative"` ` | "notice"` `                                                                       | "positive"`                                                                          | `"default"` | Alters the border color and visual intent of the search input. |
-| `label`       | `string`        | `-`           | The `label` for the input element.                                                |
-| `placeholder` | `string`        | `-`           | Sets the `placeholder` text displayed within the input element.                   |
-| `sdsType`     | `"textField"` ` | "textArea"`   | `"textField"`                                                                     | Defines the type of component to render, with options for a text input or text area. |
-
-### Code examples
-
-#### **InputText – Text Field**
-
-This component represents the text field variant of the `InputText` component.
-
-**/styles.css**
-
-```css
-body {
-  font-size: 13px;
-  font-weight: 400;
-  letter-spacing: 0.08px;
-  line-height: 20px;
-  text-transform: none;
-  font-family: "Inter", sans-serif;
-}
-
-h1 {
-  font-size: 1.5rem;
-}
-
-.app {
-  padding: 20px;
-}
-```
-
-**tsconfig.json**
-
-```json
-{
-  "include": ["./**/*"],
-  "compilerOptions": {
-    "strict": true,
-    "esModuleInterop": true,
-    "lib": ["dom", "es2015"],
-    "jsx": "react-jsx"
-  }
-}
-```
-
-**/App.tsx**
-
-```tsx
-import { InputText } from "@czi-sds/components";
-import { Box } from "@mui/material";
-import "./styles.css";
-
-function App() {
-  return (
-    <div className="app">
-      <Box sx={{ width: 300 }}>
-        <InputText
-          id="search-input"
-          label="Label"
-          placeholder="Enter your text"
-          hideLabel
-        />
-      </Box>
-    </div>
-  );
-}
-
-export default App;
-```
-
-**/index.tsx**
-
-```tsx
-import React from "react";
-import { createRoot } from "react-dom/client";
-import { ThemeProvider as EmotionThemeProvider } from "@emotion/react";
-import { StyledEngineProvider, ThemeProvider } from "@mui/material/styles";
-import { Theme } from "@czi-sds/components";
-import CssBaseline from "@mui/material/CssBaseline";
-import useMediaQuery from "@mui/material/useMediaQuery";
-
-import App from "./App";
-
-const container = document.getElementById("root");
-const root = createRoot(container!);
-
-const RootApp = () => {
-  const prefersDarkMode = useMediaQuery("(prefers-color-scheme: dark)");
-  const theme = prefersDarkMode ? Theme("dark") : Theme("light");
-
-  return (
-    <StyledEngineProvider injectFirst>
-      <ThemeProvider theme={theme}>
-        <EmotionThemeProvider theme={theme}>
-          <CssBaseline />
-          <App />
-        </EmotionThemeProvider>
-      </ThemeProvider>
-    </StyledEngineProvider>
-  );
-};
-
-root.render(
-  <React.StrictMode>
-    <RootApp />
-  </React.StrictMode>
-);
-```
-
-**/public/index.html**
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <link rel="preconnect" href="https://fonts.googleapis.com" />
-    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
-    <link
-      href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"
-      rel="stylesheet"
-    />
-    <link
-      href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&display=swap"
-      rel="stylesheet"
-    />
-  </head>
-  <body>
-    <div id="root"></div>
-  </body>
-</html>
-```
-
-**/package.json**
-
-```json
-{
-  "dependencies": {
-    "react": "^18.0.0",
-    "react-dom": "^18.0.0",
-    "react-scripts": "^4.0.0"
-  },
-  "devDependencies": {
-    "@types/react": "^18.0.0",
-    "@types/react-dom": "^18.0.0",
-    "typescript": "^4.0.0"
-  },
-  "main": "/index.tsx"
-}
-```
-
----
-
-#### InputText – Text Area
-
-This component represents the text area variant of the `InputText` component.
-
-**/styles.css**
-
-```css
-body {
-  font-size: 13px;
-  font-weight: 400;
-  letter-spacing: 0.08px;
-  line-height: 20px;
-  text-transform: none;
-  font-family: "Inter", sans-serif;
-}
-
-h1 {
-  font-size: 1.5rem;
-}
-
-.app {
-  padding: 20px;
-}
-```
-
-**tsconfig.json**
-
-```json
-{
-  "include": ["./**/*"],
-  "compilerOptions": {
-    "strict": true,
-    "esModuleInterop": true,
-    "lib": ["dom", "es2015"],
-    "jsx": "react-jsx"
-  }
-}
-```
-
-**/App.tsx**
-
-```tsx
-import { InputText } from "@czi-sds/components";
-import { Box } from "@mui/material";
-import "./styles.css";
-
-function App() {
-  return (
-    <div className="app">
-      <Box sx={{ width: 300 }}>
-        <InputText
-          id="search-input"
-          label="Description"
-          placeholder="Enter your text"
-          sdsType="textArea"
-        />
-      </Box>
-    </div>
-  );
-}
-
-export default App;
-```
-
-**/index.tsx**
-
-```tsx
-import React from "react";
-import { createRoot } from "react-dom/client";
-import { ThemeProvider as EmotionThemeProvider } from "@emotion/react";
-import { StyledEngineProvider, ThemeProvider } from "@mui/material/styles";
-import { Theme } from "@czi-sds/components";
-import CssBaseline from "@mui/material/CssBaseline";
-import useMediaQuery from "@mui/material/useMediaQuery";
-
-import App from "./App";
-
-const container = document.getElementById("root");
-const root = createRoot(container!);
-
-const RootApp = () => {
-  const prefersDarkMode = useMediaQuery("(prefers-color-scheme: dark)");
-  const theme = prefersDarkMode ? Theme("dark") : Theme("light");
-
-  return (
-    <StyledEngineProvider injectFirst>
-      <ThemeProvider theme={theme}>
-        <EmotionThemeProvider theme={theme}>
-          <CssBaseline />
-          <App />
-        </EmotionThemeProvider>
-      </ThemeProvider>
-    </StyledEngineProvider>
-  );
-};
-
-root.render(
-  <React.StrictMode>
-    <RootApp />
-  </React.StrictMode>
-);
-```
-
-**/public/index.html**
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <link rel="preconnect" href="https://fonts.googleapis.com" />
-    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
-    <link
-      href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"
-      rel="stylesheet"
-    />
-    <link
-      href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&display=swap"
-      rel="stylesheet"
-    />
-  </head>
-  <body>
-    <div id="root"></div>
-  </body>
-</html>
-```
-
-**/package.json**
-
-```json
-{
-  "dependencies": {
-    "react": "^18.0.0",
-    "react-dom": "^18.0.0",
-    "react-scripts": "^4.0.0"
-  },
-  "devDependencies": {
-    "@types/react": "^18.0.0",
-    "@types/react-dom": "^18.0.0",
-    "typescript": "^4.0.0"
-  },
-  "main": "/index.tsx"
-}
-```
-
----