Every page in a shop is a list of blocks. You add them, put them in the order you want, and fill in what each one needs. The storefront renders them top to bottom.
Pages live under Pages in the admin. A new page starts as a draft, so it is invisible to customers until you publish it.
The blocks
Things you write
Heading — a section title with an optional line above it, left or centred.
Text — paragraphs. Basic HTML is allowed: wrap paragraphs in <p>, use
<strong> and <a href>.
Image — one picture, with optional caption, and a full-bleed toggle that runs it edge to edge. Upload a new file or pick one you have already used.
Call to action — a headline, a line of copy and a button, on a dark panel.
Spacer — empty vertical room, 8 to 200 pixels.
Things that read your shop
Products — a grid of live products from your catalogue. Choose a category or leave it on Everything, and how many to show. It reads the catalogue when the page loads, so it is never out of date.
Hero banner — the full-bleed banner. Give it its own image and words, or leave any field empty and it falls back to your theme's hero. A blank hero block is exactly the theme's, which is what the home page uses.
Category grid — tiles for your categories, each linking to that category in the listing. Set the heading, pick which categories to show, choose two to five columns, and decide whether it appears on phones.
Product rails, Featured collection, Customer photos, Newsletter, Marquee, Mobile greeting, Mobile chips — the storefront's own sections. They take their content from your theme, catalogue and feed, so there is nothing to fill in: what they offer is a position in the order.
Working with images
Two ways to put a picture in a block:
- Upload — drop a file in. It goes to your image library and is used straight away.
- Choose one you already uploaded — opens the library, filtered by folder, and reuses that exact image. Worth preferring when the same banner belongs on several pages: a second copy is a second thing to replace later.
Ordering and removing
Each block has ↑ ↓ to move it and × to remove it. Changes are kept locally until you press SAVE PAGE, so reordering four blocks is one save, and abandoning an experiment means leaving without saving.
Uploads are the exception — a picture is in your library the moment you pick it, whether or not you save the page.
Writing a page as JSON
A page is a list of sections, and the editor will take that list as a file. Import JSON in the page editor accepts any of three shapes:
[ { "type": "heading", "data": { "text": "HELLO" } } ]
{ "blocks": [ … ] }
{ "title": "About", "slug": "about", "blocks": [ … ] }
Only the sections are used — the title, the address and whether the page is published are never changed by an import.
Each section is { "type": …, "data": { … } }. The id is optional and made
up where it is missing. Every type and every setting it takes is listed in
Sections, which is the page to hand to an assistant if
you want it to write a section list for you: give it that reference and the
shape above, and paste back what it writes.
Before anything is applied the dialog says what it understood — how many sections, which types, and which were skipped because this store has no such section. Then choose:
- Replace the page — the imported sections become the page.
- Add to the end — they are appended to what is already there.
Nothing is saved either way until you press Save page, so an import that turns out wrong costs a Close without saving.
Export does the other half: it copies the page you are looking at as JSON (or downloads it, if the clipboard is refused). The quickest way to a file worth editing is to take the page that already exists and change it.
Columns and tabs carry their own sections, nested the same way, up to three deep — past that the parts are kept and their contents dropped, which is what the storefront does with a page that arrives too deep anyway.
Addresses
A page called "Size Guide" lives at /size-guide. You can change the address
in the editor.
Two kinds of page behave differently:
- Home is the front page. It cannot be renamed, unpublished or deleted, because a shop with no front page has nothing to serve.
- Built-in pages — the listing and the cart — are rendered by the storefront's own code. They appear in your Pages list so you can rename them and put them in menus, but they have no blocks.
Addresses the storefront already uses — /account, /bag, /product and so
on — are refused, because a page there would exist and never be reachable.
Putting a page in the menu
Publish it, then go to Menus. Your published pages appear under Add a link. Build the menu you want, then pick it under Themes → Header.
A menu item can be hidden rather than deleted, which is how you keep a seasonal link ready without showing it.