Templates

Templates eliminate repetition for content-driven pages: write the layout once, connect it to a content type, and every entry of that type gets its own URL and rendered page automatically. A single template ensures every blog post, product page, or author profile looks consistent without duplicating structure.

After working through this chapter you can create a connected template, configure its URL pattern, compose it from sections and registered components, and bind those components to real CMS entry data.

In This Chapter

Start here (Chapter overview): Understand the template-to-content-type relationship, how templates fit into Studio’s architecture alongside freeform pages and embedded compositions, and when a connected template is the right choice.
The connected content type: How a template binds to one content type, where its URL pattern comes from, and how to edit it, including the exact form location for custom preview URLs (in your stack, under Settings, then Visual Experience, then Preview URL).
Using sections and components in a template: Compose a template on the canvas with the palette, canvas, and right panel, bind components to entry data, and understand Save versus Deploy.

Quick tip: You don’t need to build every template from scratch. Sections (reusable, data-aware layout blocks) snap into templates and bind to entry fields automatically. Once you understand how templates and sections work together, repeating yourself across pages becomes the exception rather than the rule.