Build From a Template
One design serving every blog post, including the ones you have not written yet.
Some content keeps arriving. You will write blog posts for years, and building a page for each one by hand is not a plan.
A template page is one page that serves many addresses. You design it once — what surrounds the content, how it is introduced, what follows it — and every item of that content type gets a page automatically, at its own address, with its own title and search-engine data.
Before You Begin
- A fragment that renders the content you are templating — fragments live in your library
- Some of that content already created, so you can check the result
Steps
Choose a content type
The content types are grouped. Blog offers a blog post page, a category page and a blog home page, and these are the ones available now.
The Commerce, Content and Team groups are visible but marked Coming Soon — product and listing pages, events, FAQs, glossary terms, team directories and profiles. They are shown so you can see what is planned; they cannot be selected yet.
Each card shows the address pattern it produces, like /blog/:category/:slug.
Pick the fragment that renders the content
A fragment is the piece that displays the actual content — the post itself, with its title, body and images. Choose the one that suits.
If no compatible fragment exists you are told so, with a link to create one. The template cannot work without one, because the fragment is the part that changes per address.
Check the URL pattern
The pattern is shown and comes from the content type. Segments written like :slug and :category are replaced per address — so /blog/:category/:slug becomes /blog/engineering/why-we-rebuilt-our-api for one post and something different for the next.
This is what makes one page serve thousands. Nothing is generated per post.
Name it and describe the surrounding sections
Page Name is for your own pages list.
Additional Sections is where you describe what should surround the content — a newsletter call to action, related posts, an author biography, a back-to-the-blog link. This is optional, and it is what makes a blog feel like part of your site rather than a bolted-on feed.
Watch for the duplicate warning
If your site already has a template page for this content type, a note tells you that building a new one replaces it.
One template per content type is the rule — two pages both claiming /blog/:category/:slug could not both win.
Generate, then check it against real content
Once it is built, open one of the addresses it serves — a real blog post — rather than reviewing the template in the abstract. A template looks fine with placeholder content and reveals its problems with real content, especially a post much longer or shorter than you imagined.
Result
A page marked Template in your pages list, showing its URL pattern instead of a slug, serving every item of that content type.
