webiny-api-cms-content-models

Implement a class satisfying ModelFactory.Interface, use the fluent builder to declare fields, layout, and API names, then export it via ModelFactory.createImplementation(). Register the file in webiny.config.tsx with an Api.Extension src prop including the full .ts extension.

List fields created with .list() require the plural renderer variant, such as textInputs, lexicalEditors, files, or objectAccordionMultiple. Pairing .list() with a singular renderer renders the wrong component and the field fails to save values.

Use fields.ref() with .models([{ modelId: "..." }]) to restrict which models can be referenced, and pick a renderer family: dialog, autocomplete, or inline radio/checkboxes. When querying via the SDK, ref fields need double values. nesting like values.author.values.name.

Build failures commonly occur when the Extension src prop omits the .ts file extension or when the file uses a named export instead of export default for createImplementation(). Both the full path and default export are required.

Yes, use .rules() with FieldRule objects. accessControl rules match the current identity or team, while condition rules reactively compare other field values using operators like ==, contains, or isEmpty, with hide or disable actions.

Object and dynamicZone sub-fields are inline and use a single values. prefix, such as values.author.name. Only ref fields use double values. nesting because they resolve to another entry; mixing these up silently returns null.