Skip to main content
Rich Text fields store structured JSON. Use the converter that matches where the content will be consumed:

Retrieving the editor config

Some conversions need the sanitized editor configuration because enabled features define the available nodes and transformers. editorConfigFactory provides five ways to retrieve one.
Each method takes one object. This table lists every option and the methods that accept it: Every method returns the sanitized editor config. fromField returns it directly; the others return a promise.

Default editor config

Build the package’s default feature set against your FrogBot config:

Config from a sanitized field

fromField is synchronous and accepts a Rich Text field whose editor has already been sanitized:

Config from features

Build a configuration from a feature list without instantiating a reusable editor provider:
This method also accepts isRoot, lexical, and parentIsLocalized options.

Config from an editor provider

Use fromEditor when you already have a reusable editor provider:
Prefer fromFeatures when you only need the feature list. fromEditor also accepts isRoot and parentIsLocalized.

Config from an unsanitized field

Use fromUnsanitizedField while you have a field with an editor provider rather than a sanitized adapter:
This method also accepts isRoot and parentIsLocalized.

Read a sibling field config in a hook