Sections

Reusable blocks with linked schemas (a declaration of the data shape a section expects — think of it as the section’s contract with any template that drops it) and exposed props (per-instance overrides authors can tweak without touching code).

On This Chapter

• Start here — Chapter overview — What sections are, why they exist, and how they fit between components and templates.

Binding sections to data

• Binding to CMS — The canonical page: linked schema (declaring the shape), auto-binding (matching shape to drop location), and Section Data (rooting one placement at a document, on templates and freeform pages alike).
• Linked schema — Declare the data shape a section expects so Studio can structurally match it onto a template.
• Auto-binding by drop location — How Studio resolves bindings against the scope at the drop point (page root, Repeater, Modular Block).

Opening sections up to template authors

• Expose Section Props — Surface individual component props for per-instance overrides on a template.

Continue

• Continue to Smart Containers — Repeaters, Condition Blocks, and Section Slots: the primitives that turn static layouts into data-driven ones.

See Also

• Section Data reference — every Section Data rule in one lookup table
• Back to docs home
• Templates — Where sections get composed into full pages.