Content
Store pages: about, shipping, terms, and the pages you add
Store pages at `/dashboard/pages` are the static backbone of your storefront: the about, shipping, and terms pages that ship with every new store, plus any custom pages you add — a size guide, a wholesale inquiry page, a care-instructions hub. They use the same rich editor as the blog, they render with your active theme, and they live at clean URLs under your store path. ## The pages you already have Every store starts with three pages included at signup: - **About** — your story, written as a sensible starting draft you should personalize - **Shipping** — delivery times, methods, and costs - **Terms** — the legal baseline for selling Find them under **Pages** in the dashboard. Edit them like any other page: fill in your real shipping promises, put actual people in the About page, and have someone sane read the terms before launch day. These three pages answer the majority of pre-purchase questions, which is why they exist from minute one. ## Create a custom page 1. Open **Pages** → **New Page**. 2. Give it a **title** and a **slug** — the slug becomes the URL, so "size-guide" lives at `/<storeSlug>/pages/size-guide`. 3. Compose in the **rich editor**: headings, paragraphs, images, links, tables, lists. Paste from a document and the formatting survives. 4. Pick a **template type**: - **Default** — a standard content page - **Contact** — the page plus a working contact form; messages submitted through it arrive in your dashboard inbox (**Messages**) with the visitor's details attached 5. Click **Save**. The page is live immediately at `/<storeSlug>/pages/<slug>`. ## How pages render Custom pages render **themed** — the active theme draws the header, footer, navigation, and typography around your content, so a page never looks like it came from somewhere else. Change themes and your pages change clothes with the store; no re-exporting, no re-styling. Pages are also served with your store's SEO settings applied, so titles and meta descriptions are editable from the SEO Suite's on-page optimizer. ## What happens next - Add important pages to your store navigation through the theme's navigation settings — the theme footer and header menus are where shoppers actually look. - Use the **Contact** template for any page whose job is to start a conversation: wholesale, custom orders, press. The form is wired to the dashboard inbox, so nothing needs plumbing. - Keep slugs short and stable. The URL is part of the page's identity — links, QR codes, and print materials will point at it for years. ## Tips - One page, one job. "Shipping & Returns & FAQ" becomes a scroll nobody finishes; split them and link between them. - The rich editor handles images well, but resize before uploading — a 4,000-pixel photo of a size chart wastes every visitor's data. - Reuse the terms and shipping pages as chatbot fuel: FAQ entries and docs that quote your real policies keep the storefront chatbot's answers accurate. ## FAQ **Can I use raw HTML instead of the editor?** The rich editor covers headings, images, tables, links, and layout for virtually everything a static page needs. For anything beyond that, the editor's output stays clean and theme-consistent — custom pages are designed to render correctly inside every theme without hand-written markup. **What is the difference between a page and a blog post?** Pages are standing content — the answer changes rarely and the URL matters. Posts are dated content in the blog feed with tags, likes, and comments. A size guide is a page; "new arrivals this week" is a post. **Do included pages count against any limit?** No. The About, Shipping, and Terms pages are part of every store, and plan limits that apply to products or blog posts do not touch store pages.