Back
Step 2: New Field Types
When forking fields and field types to replace Legacy Rich Text, you can choose between these two new field types:
- Rich Text (v2): A what-you-see-is-what-you-get (WYSIWYG) rich text editor, based on Lexical.dev
- Markdown: A field type using GitHub Flavored Markdown
Details about each field type are below, along with recommended use cases:
| Field Type | Use Cases | Supported Data Types on Import | Storage Format | Supported Data Types on Export | Currently Supports Computed Field Values? |
|---|---|---|---|---|---|
| Rich Text (v2) | Authoring content directly in Yext | JSON Abstract Syntax Tree (when importing via Entities API or File Upload) Yext-Flavored-Markdown and HTML (when importing via Connectors — requires a transform to convert to JSON AST) |
JSON AST | JSON AST HTML |
No |
| Markdown | Authoring content externally and importing into Yext Users who prefer to author content in Markdown |
Markdown and HTML (via Entities API, File Upload, Connectors) | Markdown | Markdown HTML |
Yes |
<% elem.innerText %>