Content types
A content type describes a kind of record: a page, a product, a machine, a certificate, a service contract. You describe it once, and the platform supplies the rest — a form to create it, an address to reach it, revisions, permissions, translations and a place in listings.
This is the sentence the whole platform rests on: new kinds of things are configured, not programmed.
Creating one
Back office → Structure → Content types → Add.
You give it a name and a machine name. The machine name is what
configuration refers to it by, so it is worth choosing calmly: machine
rather than machine_new_2.
The flags that change everything
Four switches decide how a type behaves. They are small and they are not subtle.
| Flag | When it is on |
|---|---|
| Public | Records may be listed publicly — a catalogue, a blog, a product range |
| Addressable | Records may be reached at their own address, even when the type is not publicly listed |
| Composite | Records are parts of other records rather than pages of their own |
| Embeddable | Records may be placed inside other pages |
Public and addressable are not the same question
"May a visitor open this at its own address?" and "may this appear in a public listing?" are genuinely different. A product variation is the example that forced the distinction: each variation needs a real address a customer can be sent to, but a listing of variations is exactly what would publish your cost price. Addressable, not public.
Fields
A type is its fields. Add them under the type's Fields tab; each has a kind (text, number, date, reference, file, image…), a label, and settings that belong to that kind.
See Fields for what each kind does and where its settings live.
Publication
A record is visible publicly when two things are true: it is published, and it carries a publication stamp.
Published without a stamp means invisible
A record marked published but missing its stamp is filtered out everywhere — listings, references, search, its own address. The symptom looks like a broken listing rather than a data problem, which is exactly what makes it expensive. If content has vanished from a listing, check the stamp before you check the listing.
What you get for free
Because a type is described rather than written, every type receives the same machinery:
- a create and edit form, with your fields in your order
- an address, answered by the platform's one address rule
- revisions and a change trail
- per-organization permissions
- translation into every configured language
- availability to listings, search and exports