Pages

Learn how storefront pages are created, composed from blocks, published or kept as drafts, and how renaming a slug keeps the old URL working.

A storefront page is a database record with a name, a slug, meta fields, and a layout of block rows.

Custom pages serve at /pages/ plus their slug, and renaming one keeps the old URL working.

Blog posts are a separate thing — Markdown files on disk — and the images both use live in the media library, in your own S3 bucket. Any S3-compatible bucket will do; it is yours, not a hosted asset service.

Pages sit in the same database as your orders and products. There is no separate CMS to run or keep in sync, which is the reason a page can point at a live collection or feed and stay correct without anything being copied between systems.

Where it lives

Storefront → Pages
Content → Blocks → Page layout

The page record holds the name, slug and meta fields. The layout — which blocks sit in which rows — is composed on the second screen.

Draft or published

A page is one or the other.

Create it with Publish now off and it stays a draft. A draft is:

Still viewable by a signed-in admin
Marked as a preview
Served with instructions not to index it

So a draft can be reviewed in place by a signed-in admin without being indexed.

A page cannot be published empty

Publishing is refused when:

The layout has no blocks
The layout points at blocks that have been deleted

The reason is shown on the page. There is no way to put an empty page live by accident.

Product and collection index pages are editable too

The routes that ship with the storefront get a page record automatically, so you edit their layouts alongside your own. Draft and published apply only to pages you create — built-in routes always render, and the home page cannot be deleted.

Old URLs keep working

Change a slug and the previous one is kept on the record.

Requests to the old slug are permanently redirected to the current URL, including after several renames.

Slugs are unique, so no two pages can compete for the same address.

SEO fields per page

Each page has a meta title and a meta description:

meta title        70 characters
meta description  320 characters

A live search preview shows how they will read, against the page's canonical URL.

AI generation fills the two fields in the form for you to review. It never saves on its own — what goes live is what you accept.

Building a page

In Storefront → Pages, create the page. The slug follows the name until you edit it yourself, and the URL it will serve at is shown under the field.
Open the layout editor and compose the page's rows of blocks — a product feed block is what turns a page into an endless product stream.
Set the meta title and description on the page's detail screen, then publish.

Deciding what to create

Create a page when the thing you are making is part of the storefront and composed of blocks — a landing page, an about page, a campaign destination.

Write a blog post instead when it is an article. Those are Markdown files on disk, not page records, and they are not composed of blocks.

Edit a built-in route's layout rather than making a copy of it. Product and collection index pages already have a page record waiting.

Rename a slug freely. The old address keeps redirecting, and it survives being renamed more than once.

The question before you create anything is:

Is this a composed storefront page, or an article — and does a built-in route already cover it?