Skip to main content
A page on your storefront, such as /home/pages/spring-wellness-guide, is two records: the page, which holds its title, slug, description, and status, and a page template, a Liquid file in your theme that decides what the page looks like. fluid pages create creates both and links them, so the new page renders through a template of its own instead of the theme’s default page template.

​
How a page and its template fit together

  • The page is the content record. Its slug sets the URL, and its status decides whether shoppers can see it.
  • The page template belongs to a theme. It is a Liquid file like any other template in the theme, so you edit it the way you edit the rest of the theme.
  • One template can serve many pages, but each page created here gets its own, named after the page’s title.
  • A page with no template of its own renders through the theme’s default page template.
The template is versioned separately from the page. Editing the page’s title or description doesn’t change its template, and saving the template doesn’t change the page.

​
Before you start

  • Your token needs update permission for Pages to create and change pages, and for Themes to create and edit page templates.
  • Decide which theme the template goes in. The CLI uses the active theme unless you pass --theme with another theme’s name or ID.
  • Install and sign in to the CLI:
Every fluid pages command prints JSON. Failures print a JSON error on stderr and exit with a non-zero code.
Prefer to answer questions? Run fluid pages walk in a terminal. It asks for the title, slug, template, and theme one at a time, shows a summary before it creates anything, then offers to publish the page and replace its template’s Liquid. Type < to go back, > to skip, and ? for a menu.

​
Steps

1

Create the page and its template

This changes your storefront, so the CLI asks for confirmation unless you pass --yes. In order, it:
  1. creates a page template in the theme, named spring-wellness-guide after the title;
  2. creates the page as a draft, with the slug spring-wellness-guide;
  3. assigns the template to the page;
  4. reads both back to confirm they are linked.
The template starts as a minimal layout that shows the page’s title and description. To start from your own Liquid instead, pass --content-file page.liquid, or copy an existing page template in the same theme with --template-from <name or ID>. Pass --slug or --template-name to choose those names yourself.By default the page also loads the theme’s stylesheets, so it matches the rest of your storefront. Pass --blank to leave them out.The page stays a draft. Add --publish to publish it in the same run, or publish it in the last step once the template is ready.
2

Check the page and its template

The output shows the template’s ID, its theme, the pages it is assigned to, and its Liquid. fluid pages show spring-wellness-guide shows the page itself.
3

Edit the template

This replaces the template’s Liquid and publishes the new version, so it changes your storefront and needs --yes. Leave out --publish to save the change as a draft version of the template without making it live, then run the command again with --publish when it is ready. Repeat until the page shows what you want.For sections, blocks, and settings, work in the theme itself: see the Theme developer guide, the Fluid CLI for themes, and the Page Editor.
4

Publish the page

This makes the page visible on your storefront. To take it down again, run fluid pages unpublish spring-wellness-guide --yes, which turns it back into a draft.

​
What the status means

The result of create reports how the template is linked in assignment, and the page’s state in status:

​
Troubleshooting

  • A step fails after the template was created. The CLI removes the draft page and the template it just created, and the error says so. If removing them also fails, the error names what is left so you can delete it.
  • The error says the link couldn’t be read back. The CLI keeps the draft page and the template and prints their IDs. Check them with fluid pages show and fluid pages template before you retry, so you don’t create a second pair.
  • Your session expires partway through. The CLI keeps whatever it created and prints the IDs. Sign in again, then check or delete them.
  • fluid pages template says the page has no template of its own. The page renders through the theme’s default page template, or its template is in a theme that isn’t active. Pass --template-id with the template’s ID.
  • The page looks unstyled. It was created with --blank, which leaves out the theme’s stylesheets. Delete it and create it again without --blank.

​
Delete a page

The page comes off your storefront immediately. Its template stays in the theme, because another page may use it, and the output gives its ID as templateId when the template is in the active theme. Once no other page uses the template, delete it with fluid themes templates delete <template ID>.

​
Use the API directly

The CLI makes these calls in order, each authenticated with a Bearer token:
  1. Creates a theme template, with the theme’s ID and the page template type.
  2. Create a Page as a draft.
  3. Updates themeable records to be used by the specified template, adding the new page.
  4. Company Page show and Retrieves a theme template, to confirm the link from both sides.
  5. Update a Page to publish it.
If a later step fails, Destroy a Page and Deletes a theme template remove what was created. Get the active theme finds the theme to use, and Updates a theme template with Publishes the template edits and publishes the template’s Liquid.