Documentation

Content modelling

Schema types, the page-builder pattern, Portable Text, references and validation — the decisions that shape everything downstream.

  1. Schema types

    Documents, objects and fields, defined with defineType and defineField exactly as in any Sanity project — and validated by the platform where it matters.

  2. The page-builder pattern

    Compose pages from section objects the frontend can render, instead of from free-form rich text. The pattern most real Sanity projects use, and the rules that keep it working.

  3. Portable Text

    Rich text as structured data: blocks, styles, lists, decorators, annotations and embedded objects — and why that beats storing HTML.

  4. References, slugs and what the platform enforces

    Strong references must resolve and published slugs must be unique. Both are enforced on write and publish by the platform itself, not only by the Studio.

  5. Initial-value templates

    Give “create new” a head start: a page pre-composed with the sections a landing page needs, or an article pre-filed in a category.