Content

The part of the platform where you say what kinds of things exist and how they are shown. Nothing here requires code.

Content typesDescribe a kind of record once; the form, address, listings and permissions follow.FieldsWhat a record holds, how it is edited, and how it renders.TaxonomyVocabularies and terms — the axes content is browsed by.ListingsPages, blocks, tables, feeds, calendars and boards from the same definition.MediaImages and styles, video, documents, 3D models, charts and maps.Media typesDescribing a new kind of asset — a certificate, a datasheet.MapsYour own records on a base layer.3D modelsA model a reader can turn.ChartsLive data, with the question a listing would ask of it.LayoutWhere fields and blocks sit on a page.Menus and addressesNavigation, aliases, redirects and meta tags.FormsCollecting things from visitors, and where they go.Revisions and moderationWhat changed, who changed it, what needs approval.SearchWhat is searchable, and what search may return.

The shape of it

Three ideas, and everything else is a consequence:

A type is described, not written. Fields, form, display, address, revisions, permissions and translations come with being a type.

What to show and how to show it are separate. The same records become a page, a card grid, an RSS feed and a kanban board without being queried twice.

Visibility is answered once. Published, in this organization, of a public type — one gate, used by listings, references, search, feeds and addresses alike. There is no second place where a rule could be forgotten.