Brainerce HelpContent pages and blog
Write FAQs, footers, announcements and static pages once and let every storefront read them, plus publishing blog posts.
Two sidebar entries hold the words on your storefront that aren't product copy.
Content
Content holds reusable pieces your storefront reads: edit once, and every site that uses it updates.
There are six kinds:
| Type | Typical use |
|---|---|
| FAQ | Question-and-answer lists. |
| Footer | Footer links and text. |
| Header | Header text and navigation copy. |
| Announcement | The bar across the top of the site: sales, shipping cut-offs, holiday notices. |
| Rich text | A block of formatted copy a storefront can drop anywhere. |
| Page | A full static page: About, Shipping Policy, Terms. |
Create one with New content, pick the type, and write it. Each entry is Draft or Published; only published entries reach your storefront.
Deleting is permanent, and storefronts fall back to defaults. If a site expects your announcement entry and it's gone, it renders whatever it was built to show when there's nothing, usually nothing at all. Unpublish rather than delete when you just want something to stop showing.
Your storefront has to read it
Content entries are data, not rendered pages. A vibe-coded storefront fetches them through the SDK and decides how to display them. If you add an FAQ entry and nothing appears on your site, the entry is fine; the site isn't asking for it yet. That's a change to make in your storefront code (or a prompt for your AI builder).
Blog
Blog publishes articles. Create one with New post, write it, and publish.
As with Content, your storefront renders posts however it likes. Brainerce stores the article and exposes it through the SDK; the layout is yours.
Deleting a post is permanent.
Blog post SEO: title, description, and social image
Every blog post has its own search and social settings, right in the post editor:
| Field | What it controls |
|---|---|
| Slug | The address of the post, for example /blog/summer-care-guide. Auto-derived from the title; you can edit it. Renaming a slug is safe: the old address automatically redirects (301) to the new one. |
| SEO title | The headline Google shows for this post. Falls back to the post title when empty. |
| SEO description | The snippet under the headline in Google results. 150 to 160 characters works best. |
| OG image | The image shown when the post is shared on WhatsApp, Facebook, or X. Falls back to the cover image when empty. |
Static Pages (About, Shipping Policy, …) have the same three SEO fields in their editor: a page's SEO section holds its title, description, and OG image.
Published posts are added to your storefront's sitemap automatically, and Brainerce pings search engines (IndexNow) the moment a post goes live, so you don't submit anything by hand. See Get found on Google for the full picture.
Which one to use
- Something that appears in the furniture of the site, such as a footer, header, announcement bar or FAQ block → Content.
- Something that is an article with a date → Blog.
- Something that describes a thing you sell → that's a product, not either of these.
What's next?
- Connect your storefront explains how a storefront reads any of this.
- Media library holds images to use in posts and pages.