Instance · CMS
Pages Introduction
Last updated 1 November 2026
Each address on your site, with its content, layout, search and sharing settings and access rules.
A page is one address on your site, such as /about or /products/42. In the CMS you set its address, its content, the layout around it, and how it appears in search results and social shares. Pages reuse partials and layouts, so most of a new page is already built.
Where to find pages
In the admin, open CMS and choose Pages. The docs.insites.io instance had 63 pages on 1 November 2026.
The parts of a page
| Tab | What you set |
|---|---|
| Details | The address (slug), the request method, the layout and the format |
| Content | The page body, in Liquid |
| Sitemap | Whether the page is in the sitemap, with its priority and how often it changes |
| Metadata | The meta tags for search engines |
| Open Graph | The title, description, image and type used when the page is shared |
| Schema | Structured data for search engines |
| Security | Authorization policies that decide who may open the page |
| Cache | How long the page is cached, and how |
Example: a page in code
app/views/pages/about.liquid
---
slug: about
layout: application
metadata:
page_name: About us
---
<h1>About us</h1>
{% render 'shared/team_list' %}metadata.page_name is the name shown in the CMS list. Set it in the file, so it survives every deploy.
Common mistakes
- A blank name in the page list. Pages added in code need
page_namein their metadata. - Leaving a members page with no policy in Security. A page with no policy is public.
- Expecting the sitemap to list a page on its own. Turn it on in the Sitemap tab.