Reference
Pages and themes
Overview
Your agent can build and restyle the content of StoreFront pages, create and copy pages, change which containers a template includes, replace store menus, and change a theme's applied colors and fonts. It edits the same content the Visual Builder edits, so what it builds stays editable there.
This area covers:
- Page bodies and theme containers, such as a page's main content, a header, a footer or a hero section.
- Pages: creating, copying, moving and renaming pages, their settings, attributes and images, and the items and blog posts assigned to them.
- Templates: finding which template a page uses, copying a template so one page can have its own layout, and wiring a container into a template.
- Store menus, which are what a menu element renders.
- Theme attributes: a theme's applied colors, fonts and settings.
- Themes: listing themes, checking an upgrade, and duplicating a theme (optionally upgrading the copy).
- Site attributes and search engine settings, such as the site title, SEO description, Canonical Links, Schema.org and Prevent Indexing, and reading sitemaps.
- Catalog search facets: which facets show and their headings.
- Reusable sections: saving and installing fragments in the element library, and local recipes.
Example requests
- "Add a headline and a button to the /about page on my test theme, preview it, and wait for me before pushing."
- "Rework the site header: logo left, a mega menu with the top categories, cart and account on the right. Collapse it to a drawer on mobile. Show me a preview."
- "Duplicate the active theme, upgrade the copy, and tell me what conflicts the upgrade leaves."
- "Change the theme's accent color to the brand green #2F5D3A on the inactive theme, and show me the result."
- "Add a Sale link to the footer menu."
- "Create a /fall landing page with a hero and a four-item product grid."
Commands
| Command | What it does |
|---|---|
sf pages list, sf pages get | List pages with their settings, or read one page's attributes and image slots |
sf pages create, sf pages duplicate | Create a page under an existing parent, or copy a page with its body and settings |
sf pages move | Move or rename a page and the pages under it, optionally redirecting the old addresses |
sf pages settings, sf pages attributes, sf pages images | Change page settings, attributes and images |
sf pages items, sf pages blog-posts, sf pages selectors | Change which items and blog posts a page shows |
sf pull, sf push | Read and write a page body or theme container with a guarded push |
sf template find, sf template create, sf template wire | Find a page's template, copy a template, or add a container to one |
sf menus list, sf menus pull, sf menus push | Read and replace a store menu |
sf theme-attributes get, sf theme-attributes set | Read and change a theme's colors, fonts and settings |
sf themes, sf themes upgrade-check, sf themes duplicate | List themes, preview an upgrade, or copy a theme |
sf site get, sf site attributes, sf site seo, sf site seo-set, sf site sitemaps | Read and change site attributes and search engine settings, and read sitemaps |
sf search facets get, sf search facets set | Read and change the catalog search facets |
sf library search, sf library install, recipe instantiate | Find and reuse saved sections |
Live and shared changes
- A page body, such as
/about/body.cjson, belongs to no theme, so every write to it is live. - Page settings, attributes and images, site attributes, menus and search facets are shared by every theme. Changes to them are live at once and need
--liveand publish permission. - Page data, site attributes and theme attributes have no protection against a later save elsewhere. The admin's General screen saves the whole storefront and can overwrite a site attribute change, and the Design panel can overwrite a theme color or font change. Menus and search facets are guarded by the version the agent read.
- A new page is live as soon as it exists, unless it is created hidden.
- A theme container on an inactive theme can be written and previewed before anyone sees it. The active theme needs
--liveand publish permission. - A template change affects every page that uses that template.
What it cannot do
- Activate a theme. The agent can build and preview on an inactive theme; you activate it in the admin.
- Delete a page. Create, copy, move and rename work; deleting a page is done in the admin. The agent can hide a page and redirect its address first.
- Change the order of search facets. The order is fixed.
- Create a storefront or change its domains or SSL.
What needs approval
- Moving or renaming a page with
sf pages move. - Any template write:
sf template create,wire,unwireandmove, with a fresh authenticator code each time. - Turning Canonical Links or Schema.org off, or Prevent Indexing on or off, with
sf site seo-set.
See Changes that need approval for the full list.
Related documentation
- StoreFront Visual Builder: the merchant guide to the editor
- Upgrade a theme: how theme upgrades and merge conflicts work
- Menus: how store menus are set up in the admin
- Files and assets: images and theme files
Was this page helpful?