Build the template in the right order
Here is the process broken into clear steps. Take them one at a time and check each off before continuing.
- Create or choose the collection and add a few representative records.
- Create the collection detail page and place the primary title, image and content connections.
- Add metadata fields such as slug, excerpt and publish date before styling the header.
- Add related content only after the primary page works on mobile and desktop.
- Preview multiple records and test direct URLs, not only the first record in the canvas.
Keep the template resilient
CMS content varies. Set sensible max widths, allow headings to wrap, and use conditional visibility for optional sections. A template that only works for one record is not a finished dynamic page.
Launch checks
The list below breaks this down into the parts that matter most. Read through each one and note anything that applies to your own setup.
- Readable, stable slugs are generated for each record.
- The page title and description change with the record.
- Images have useful alt text or are decorative by design.
- A missing related record does not break the page.
- The sitemap contains the pages you intend to index.
Diagnosing a broken dynamic page
Follow the sequence below from start to finish. The order matters: later steps assume the earlier ones are done.
- Open several different records directly by URL, not just from the canvas preview.
- Check the record with the shortest and longest title against the header layout.
- View a record with every optional field empty to confirm nothing collapses or overlaps.
- Confirm the browser tab title and meta description update per record rather than repeating one static value.
When to split into a second template
If two content types share a collection but need noticeably different layouts, such as a short news update and a long-form case study, consider separate collections with their own templates rather than adding conditional sections to one template indefinitely.