static-cms/website/content/docs/widgets/string.md

---
label: "String"
target: string
---

The string widget translates a basic text input to a string value. For larger textarea inputs, use the text widget.

- **Name:** `string`
- **UI:** text input
- **Data type:** string
- **Options:**
  - `default`: accepts a string; defaults to an empty string
- **Example:**
    ```yaml
    - {label: "Title", name: "title", widget: "string"}
    ```
New design for the widgets section in the docs (#866) * Initial commit for the new widgets section * Placing all the widgets and refining the CSS and Hugo logic * Initial commit for the new widgets section * Placing all the widgets and refining the CSS and Hugo logic * Rebased and updated the info according to @verythorough contribution * Fixing the yaml codes for the relation and select widget sections * Merging with widgets.md and app.j * Fixing some silly mistakes (sorry!) * Following @verythorough contributions :) * Adding the markdown widget and fixing the widgets container background * Adding the URL functionality and myself as a contributor :) * Adding myself as a contributor :) 2018-01-03 20:14:15 -02:00			`---`
docs(fix): revert prettier formatting on markdown files (#1612) Prettier formatting our markdown files is causing bugs because of the differences between Gatsby's parser and Prettier's. Also, Prettier formats the inline code-blocks containing example CMS configs, but the formatting it uses doesn't really make much sense or match the suggested CMS config style. It doesn't actually make much sense to format the docs anyway, since we use the CMS itself to edit/generate them. 2018-08-14 11:33:13 -06:00			`label: "String"`
convert website from hugo to gatsby (#1369) 2018-07-25 07:47:26 -04:00			`target: string`
New design for the widgets section in the docs (#866) * Initial commit for the new widgets section * Placing all the widgets and refining the CSS and Hugo logic * Initial commit for the new widgets section * Placing all the widgets and refining the CSS and Hugo logic * Rebased and updated the info according to @verythorough contribution * Fixing the yaml codes for the relation and select widget sections * Merging with widgets.md and app.j * Fixing some silly mistakes (sorry!) * Following @verythorough contributions :) * Adding the markdown widget and fixing the widgets container background * Adding the URL functionality and myself as a contributor :) * Adding myself as a contributor :) 2018-01-03 20:14:15 -02:00			`---`

			`The string widget translates a basic text input to a string value. For larger textarea inputs, use the text widget.`

			- Name: `string`
			`- UI: text input`
			`- Data type: string`
			`- Options:`
			- `default`: accepts a string; defaults to an empty string
			`- Example:`
docs(fix): widget example code layout on Site (#1606) * Fix widget example layout * Stop running MarkDown through Prettier. 2018-08-14 07:37:07 -07:00			```yaml
docs(fix): revert prettier formatting on markdown files (#1612) Prettier formatting our markdown files is causing bugs because of the differences between Gatsby's parser and Prettier's. Also, Prettier formats the inline code-blocks containing example CMS configs, but the formatting it uses doesn't really make much sense or match the suggested CMS config style. It doesn't actually make much sense to format the docs anyway, since we use the CMS itself to edit/generate them. 2018-08-14 11:33:13 -06:00			`- {label: "Title", name: "title", widget: "string"}`
docs(fix): widget example code layout on Site (#1606) * Fix widget example layout * Stop running MarkDown through Prettier. 2018-08-14 07:37:07 -07:00			```