Text blocks
Text blocks are the words on your page — headlines, paragraphs, labels, and the buttons that turn reading into action. They're the most-used blocks in any storefront.
The blocks
| Block | What it puts on the page |
|---|---|
Heading | The main title of a section. One per section is usually right — several competing headings make a page hard to scan. |
Subheading | A smaller line under a heading, for the sentence that explains it. |
RichText | A paragraph block with formatting — bold, links, lists. This is where most of your writing goes. |
Quote | A pulled-out quotation. Useful for a customer line you want people to actually read rather than scroll past. |
Badge | A small coloured label — "New", "Sold out", "Bestseller". Loses its force if everything has one. |
Tag | A compact label, usually for categorising rather than drawing attention. |
KeyValue | A label-and-value pair, for specifications: Material — Cotton. Several stacked read as a spec sheet. |
PriceDisplay | A price, formatted in your store currency, including any sale styling. |
ContactInfo | Your contact details as a block — email, phone, address. |
EmojiBlock | A large emoji as a graphic. A quick way to add personality without needing an illustration. |
Button | A single call to action. One primary button per section — a second competing button splits the decision. |
CTAPair | Two buttons together, a primary and a secondary. For "Buy now" beside "Learn more". |
What happens — and what doesn't
- Each text block has its own inspector controls — typography, spacing, alignment.
- A Button or CTAPair links somewhere — a page, a product, a payment link, or an external URL.
- Text inherits your store's typography theme by default, then can be tuned per block.
What's the difference between a Heading and Rich Text?
A Heading is a single headline. Rich Text is a block of formatted paragraph text with bold, links, and lists. Use headings for titles and rich text for body copy.
How do I add a call-to-action button?
Use the Button block (or CTAPair for two side by side) and point it at a page, product, payment link, or external URL from the inspector.
What this screen looks like in every state
| State | When you'll see it | What you see, and what to do |
|---|---|---|
| Empty | You haven't created anything here yet | “No pages found” — with a shortcut to create the first one. Nothing is wrong; there's just nothing to show yet. |
| Loading | The screen is fetching your data | A skeleton in the shape of the finished page. It should be brief — if it persists, the load has failed rather than stalled. |
| Error | The data couldn't be loaded | A message with a retry. Retry first: most of these are a dropped request, not a broken store. If it repeats, the outage is upstream and reloading won't help. |
| No access | Your role doesn't include this screen | A permission notice instead of the page. An owner or admin can grant access under Settings → Team. |
When something goes wrong
These are the messages this screen can show you, and what each one means.
| If you see | What to do |
|---|---|
| "…" is reserved for a built-in store page (like cart or checkout). Choose a different slug. | Retry the action. If it keeps happening, contact support with what you were doing. |
| Cannot delete the shop page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Delete the product to remove this page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Page title is required. | A required field is blank. Fill it in and save again. |
| This page is protected and cannot be deleted. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |