Product data and the content around it — size guides, care instructions, shipping policies, buying guides, a blog — usually live in different systems and drift apart. minipim can hold both, so your storefront reads products and pages from one API.

Turn on Content pages in Settings and a Content section appears in the sidebar.

Content types you define

Every organization starts with three content types — Page, Post and Other — each with a Body, SEO title, SEO description, SEO keywords and Summary, and an Author on posts. They’re ordinary attribute families, so you can rename fields, add new ones, or create a “Recipe” or “Lookbook” type with its own fields, without code.

A real editor

The body editor is rich text that stores clean Markdown:

  • Headings, bold, italic, strikethrough, lists, quotes, inline code and tables.
  • Links, with a per-link Open in new tab option.
  • Images by button, paste or drag-and-drop.
  • Markdown shortcuts as you type, Markdown paste, and a raw Markdown source view.

Because it’s Markdown, your storefront can render it with whatever components it likes.

Drafts and publishing

Each page has a title, slug, status (draft, active or archived), a publish date and tags, plus categories from the same tree as your products, and media. Drafts can be saved incomplete; the type’s required fields must be filled before a page goes active.

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

For your storefront

GET /v1/content/by-slug/{slug} returns a page by its slug (pass status=active to skip drafts), and the list endpoint filters by type, category and channel and sorts by publish date. Content changes fire webhooks like products do. See the headless integration.

Already have a BigCommerce blog? The BigCommerce connector imports web pages and blog posts — body, SEO fields, author, dates, tags and thumbnails.

Good to know

  • No embeds: iframes and custom HTML aren’t supported in the editor.
  • No scheduled publishing yet — the publish date is a field, not a timer.
  • No version history for pages.