Model your content once
A content model in BetterCMS is the named set of fields behind a page type, a collection or a component. You author that definition once, and the editor form, the API response and the rendered page all come from it.
Your stack. Your rules. Everyone moves faster.
What the content model gives you
-
Three kinds of model
A page type, a collection or a component. Each one holds many records or exactly one.
-
28 field types
Six families: text, choice, media, relations, structure, advanced. Cardinality is a property of the field, not a separate type.
-
References with faces
A reference resolves each record from its title field. The picker shows the cover image beside it.
-
Groups that nest
Put related fields in a group, and a group inside a group. The entry form insets each level so the depth reads.
-
Conditions stored as data
Show a field or require it when another field matches. The rule is stored as data, not written in code.
-
Validation per field type
Required, unique, character count, pattern, enum and range. A link field can refuse a javascript: URL outright.
-
A content model is the named set of fields behind a page type, a collection or a component. You author it once and the entry form, the API response and the page all follow it.
-
No. The schema builder is a canvas. You drag fields into place and see the entry form your editors will get before you save it.
-
The change is reviewed against real records before it lands, so you can see which entries a rename or a retype would touch.
-
Yes. Entry types are generated from your own content model, so a typed client picks the change up rather than drifting away from it.