Size guides, care instructions, shipping policies, buying guides and blog posts can live in minipim right beside the products they talk about, so your storefront reads everything from one place.

1. Turn content pages on

In Settings, tick Content pages. A Content pages entry appears in the sidebar, and three content types are created for you: Page, Post and Other.

Coming from BigCommerce? The BigCommerce connector can import your web pages and blog posts — bodies, SEO fields, authors, dates, tags and thumbnails — so you start with what you already have.

2. Write a page

Click New page, choose its type, and give it a Title — the slug is created from it, and you can change it.

The body editor is rich text that saves clean Markdown:

  • Type Markdown as you go (## for a heading, - for a list) or use the toolbar.
  • Add links — tick Open in new tab for links that should open separately.
  • Add images with the toolbar, by pasting, or by dragging them in.
  • Build tables, quotes and lists from the toolbar.
  • Switch to Edit markdown source when you want to see exactly what’s saved.

The editor doesn’t support embeds — iframes and custom HTML are removed — so video players and widgets belong in your storefront’s templates.

3. Fill in the rest

Every type comes with SEO title, SEO description, SEO keywords and a Summary, and posts have an Author. Add Tags, Categories (the same tree as your products, so a “Running” guide can sit beside running shoes) and Media for a hero image.

A page can be org-wide or belong to one channel, so two storefronts can each have their own “Shipping” page.

4. Publish

Pages start as draft and can be saved incomplete. Set the status to active to publish — at that point the type’s required fields must be filled in. Use archived to retire a page without deleting it.

Set the published date to control the order posts appear in; there’s no scheduled publishing, so set a page active when it should go live.

How it reaches your site

Your storefront looks pages up by slug and only shows active ones; every change fires a webhook so the site can refresh. Your developer will find the details in the headless integration.