When to use Templates vs Sections: a decision tree
Last updated September 14, 2026
Building your first Studio thing? Go to Getting Started. The numbered Quickstarts walk you through building both a Section and a Template. This page is a decision reference for later, when you're planning a new piece and need to pick which one it should be.
Two building blocks, two jobs.
Decision tree
Click to enlarge
Quick reference
| You want to | Use |
|---|---|
| Build a page tied to one entry of a content type | Template |
| Build a reusable block | Section |
| Reuse one section across different content types | Section with a linked schema |
| Let template authors drop custom content inside a section | Section Slot |
| Let template authors tweak a value inside a section per template instance | Expose Section Prop |
What renders where
| Component | Goes on | Renders |
|---|---|---|
| <StudioCanvas /> | One special "canvas" route | Sections, for preview while authoring |
| <StudioComponent /> | Your real page routes | Templates as pages visitors see |
A typical Studio-powered app ships both.
Next
- Composition concepts: how Studio models page structure
- Templates: content-type-driven pages
- Sections: reusable blocks