Run it

Edit pages and blocks

Create content pages, edit them visually in blocks, translate them, and publish without breaking the theme.

Pages are the editorial content your storefront serves alongside the catalog: the homepage, service pages, landing pages for a campaign, the terms, the contact page. Each is built from blocks and edited visually.

Before you begin. The visual editor needs a theme that supports it, active on a verified domain. Without one, the Pages list will tell you so and the edit action is unavailable. See Themes and branding.

Pages, blocks and templates

  • A page is one addressable piece of content with a title, a slug, a type and a status.
  • A block is one element inside it: a heading, a text section, an image, a product teaser, a table. Blocks stack, and some blocks contain others.
  • A template is the starting arrangement of blocks for a page type, so a new landing page begins as a landing page rather than as a blank sheet.

The theme decides which block types exist and how each one looks. You decide which ones a page uses and in what order. That division is what stops content work from producing a page that does not match the rest of the shop.

Create a page

  1. Go to Experience Studio › Pages and select New page.
  2. Enter a Title and a Slug, the URL segment, lower case and hyphenated: about-us. Leave the slug empty and it is derived from the title.
  3. Pick a Type. standard unless the theme offers something more specific.
  4. Create it. The visual editor opens straight away.
Changing the slug of a published page changes its URL. Anything linking to the old one breaks: a printed catalog, a customer's bookmark, a Google result, a QR code on a datasheet. Decide the slug before you publish, and set up a redirect if you must change it afterwards.

Edit it

The editor renders the real page from the real theme, so what you arrange is what buyers see. Two controls at the top matter more than they look:

  • The domain selector decides which storefront the page is previewed in. If you run several, check the page in the one it is actually for.
  • The language selector switches which translation you are editing.

Work in blocks: add one, move it, edit its content in place, remove it. Group related blocks into a section when the theme supports it. Blocks you want on several pages, such as a standard call-to-action or a footer promo, can be saved to a reusable library rather than rebuilt each time.

Translate it

A page carries a translation per language, each with its own title, slug and status. Switch language in the editor and edit that version.

Two things to know:

  • The languages available come from the market's locales, never from the page itself. See Languages and markets.
  • When you change the source-language content, the translations are flagged as out of date rather than silently diverging. Treat that flag as a work list.

Draft, review, publish

A page is draft, published or archived.

Work in progress is held as a draft against the page, with an owner; the Pages list shows open drafts and who holds them. That is the mechanism that stops two people quietly overwriting each other, so check it before you start editing a page somebody else is in.

For review, share a preview rather than publishing: a preview link grants access to the unpublished page and expires. Comments can be left on individual blocks and resolved, which keeps feedback attached to the thing it is about instead of in an email thread.

When it is right, publish. If the campaign has a date, schedule it instead of setting an alarm for yourself.

Every published version is kept, so a page can be rolled back to an earlier one. This is the safety net that makes it reasonable to let non-technical colleagues edit a live shop.

What to check

  1. Open the published page on the real domain, in a private browser window.
  2. Check it on a phone.
  3. Check each language you published, not only the one you edited.
  4. Follow every link in the page. Internal links to products and categories break when a code changes; content links break when somebody renames a slug.

When it does not work

  • No edit action, or "No visual editor available": the theme active on the domain does not support it. Check Installed Themes.
  • The page does not appear in the shop: it is still a draft, or the translation you published is not the language you are looking at, or the page belongs to a different market.
  • The page looks broken: a block was put somewhere the theme did not anticipate. Undo, or roll back to the last published version, rather than fighting it.
  • You deleted the wrong page: deletion is a soft delete. Ask support before you rebuild it from memory.

Next

Run it

The weekly storefront work: editing pages and blocks, building enquiry forms, and the transactional mail that answers them.

Forms and email

Build the enquiry forms a B2B storefront needs, route what they capture to a person, and manage the mail that goes back out.