Content pages

A page can be a parent of other pages by specifying it as the parent in the Child Page’s record. A child page can also act as a parent for other pages allowing you to create a hierarchy of pages. You can create links to any page using its path and can also create a list of page links using the featured pages Content Block Template.

Publishing a page

There is no publish step and no publish checkbox. A page goes live as soon as you save it, when it becomes reachable at its store URL path.

:::note Hiding pages from the navigation and menus does not unpublish a page. It removes the page from automatically generated navigation and footer lists, and from the generated sitemap, but the page still works at its path and still appears in on-site search results. To stop a page being reached at all, use Require Login? or delete the page. :::

Add content to your page

Other than Title and Subtitle (which are optional), all of the page content lives in the content body field. You can put your page content directly in there, or using the short code snippet that is there by default, render each of the content blocks related to that page in their specified order.

This is the code you would see in the content body field unless you have replaced it with other content:

{{ content_page | render_content_blocks }}

To add content blocks to the page:

1. From the Page Content Blocks related list, click New.
2. Search and select the content block you wish to add.
3. Specify the position of the content block in relation to the other content blocks on that page.
4. Make sure the Usage Type is Page Content.
5. Click Save.

Serving alternate content types

By default, pages render as HTML. You can serve a page as a different content type by including a file extension in the page Path field.

When an alternate content type is used: - The page renders without the standard HTML layout (no header, footer, or theme wrappers) - The Content Body field is rendered as-is using Liquid, so you can generate dynamic content - The current_request.content_type Liquid variable returns the MIME type for the current request

Example — generating a plain text robots.txt:

Create a page with Path robots.txt and Content Body:

```liquid

User-agent: * Disallow: /checkout Disallow: /account

Sitemap: https://{{ current_store.domain }}/sitemap.xml ```