Section BlocksDocs
Sign in
Section Blocks DocumentationPublic Reference

Guides by role: Editors, Template Builders, Developers & DevOps

Learn how Dual-JSON sections, Record Lists, declarative Components JSON (`Accordion`, `Tabs`, `Card`), public REST APIs, and the 4 Netlify deployment modes fit together end-to-end.

Audience: Copywriters, Content Strategists, Marketing Managers

Authoring pages, content JSON, record lists & project themes

Workspaces, Projects & Role Permissions
Every site lives in its own isolated Project with role-based permissions enforced on the server.
OwnerEditorRBAC

Section Blocks separates work into Projects (`My Projects`). Each Project owns its own Pages, Sections, Schemas, Records, Ordered Lists, List Views, Themes, and Publishing state.

Project access is controlled per user with two project roles: Owner and Editor. Platform Super Admins can also manage platform-wide accounts and view global collections.

CapabilityEditorOwner
Edit Copy / Content JSON on Pages & SectionsYesYes
Add, reorder & delete Records and Ordered ListsYesYes
Edit Template JSON (when unlocked or unlinked)Project settingYes
Manage Project Settings, Live/Snapshot Mode & API TokensNoYes
Invite / remove Project MembersNoYes
Sitemap Hierarchy & Page Metadata
Organize clean hierarchical URLs and per-page SEO metadata from the Sitemap & Pages tabs.
URL RoutingSEO Meta

Pages use path-based slugs (`/` for Home, `/about`, `/products/saas-cms`, etc.). The Sitemap tree builds multi-level navigation automatically from URL path segments.

Each Page stores its own `title`, `meta_description`, `meta_image`, and `og_image`, which SSR and SSG frontend builds output automatically in document `<head>` tags.

  • Always keep Home at slug `/` so preview sites and SSG crawlers resolve the index route cleanly.
  • Nested slugs such as `/docs/getting-started` automatically create parent/child navigation groups.
  • Deleting or renaming a page slug increments the project version and takes effect immediately in `live` publish mode (or on next Snapshot publish in `snapshot` mode).
Dual-JSON Sections: Safely Editing Content Without Breaking Design
Every section splits layout markup (`template`) from editable text/URLs (`content`) matched by stable `contentId` keys.
Dual-JSONSave Boundary

In the Page Editor, every section stores two independent JSON documents: Template JSON (HTML tags, Tailwind utility classes, structural layout) and Content JSON (keyed text strings, button labels, URLs, and image HTTPS links).

Content editors can modify strings inside Content JSON (including empty strings when hiding optional labels) with confidence that responsive grids, spacing, and typography stay untouched. Every save validates both JSON trees together against the server allowlist.

Content JSON (what editors update safely)json
{
  "headline": {
    "id": "headline",
    "name": "Hero Headline",
    "value": "Launch structured pages without deployment risk"
  },
  "cta_label": {
    "id": "cta_label",
    "name": "Primary CTA Label",
    "value": "Start building"
  },
  "cta_href": {
    "id": "cta_href",
    "name": "Primary CTA Link",
    "value": "/pricing"
  }
}
Schemas, Records & Ordered Lists
Model repeating content (FAQs, Team Members, Testimonials, Pricing Tiers) once and reuse it in multiple views.
RecordsOrdered Lists

Under Records & Lists, define a Record Schema (typed fields such as text, markdown/long text, URL, boolean toggle, number, or select options) and create Records conforming to that schema.

An Ordered List groups Records in an intentional drag-and-order sequence. Reordering an item or editing a record automatically updates every linked List View and synced page section.

  • One Ordered List can power multiple List Views — e.g., an FAQ list shown as a compact Accordion on Home and a searchable full Directory on `/faq`.
  • Boolean fields like `defaultOpen` automatically expand matching Accordion items on first paint.
Theme Studio, Live vs. Snapshot Publishing
Customize shadcn color tokens and Google Fonts in Theme Studio, then choose Live draft updates or immutable Snapshot releases.
Theme StudioLive vs. Snapshot

Theme Studio manages light and dark CSS variables (`--background`, `--foreground`, `--primary`, `--card`, `--border`, `--radius`, Google Fonts families) scoped safely to `[data-project-theme]` inside CMS previews and `:root` / `.dark` on deployed frontends.

Under Settings & Access (`access`), Owners control Publish Mode: `live` reflects saved changes immediately on live/SSR requests, while `snapshot` freezes a versioned release bundle (`snapshot_version`) so editors can stage multi-page edits safely before clicking Publish Snapshot.