Content 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:

TypeTypical use
FAQQuestion-and-answer lists.
FooterFooter links and text.
HeaderHeader text and navigation copy.
AnnouncementThe bar across the top of the site: sales, shipping cut-offs, holiday notices.
Rich textA block of formatted copy a storefront can drop anywhere.
PageA 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. Publish asks you to confirm and says the entry appears on every connected storefront within about 5 minutes, not instantly. Unpublish moves it back to draft and storefronts fall back to their defaults until you republish.

Who can do what. Opening Content needs View content; creating, editing, publishing and deleting need Manage content. Owner and Manager have both. Staff and Viewer can only look.

Fields every entry has

FieldWhat it takes
NameAn admin-facing label, up to 200 characters. Not shown on your storefront.
KeyLower-case letters, digits and hyphens, starting with a letter, up to 64 characters (main, shipping-faq). It cannot be changed after you save. Use main for the primary entry of a type: a new Header or Footer starts with main, and any other type starts with main only while it has none, then main-2, main-3. Two entries of the same type cannot share a key ("Key already in use for this type").
DescriptionOptional admin note, up to 1000 characters.
Sales channelsEmpty means visible on every channel. Pick channels to restrict it, up to 50.
PositionA whole number, 0 or more, the sort order within the type.
StatusDraft (admin only) or Published.
Custom fieldsOptional extra key and value pairs your storefront can read. A key starts with a lowercase letter and uses letters, digits and underscores only; a value is text.

The list shows every entry in one table, with columns for Name, Key, Type, Description, Status, Channels ("All channels" or a count), Position, Items (the number of questions in an FAQ, columns in a footer or navigation items in a header; a dash for the other types), Custom fields (a count) and Updated. The search box at the top of the dashboard narrows the list by name, key, description or type. There is no type filter and no Translations column on the list: to see only one type, type its name from the Type column into the search box, and open an entry to see its translations when Multi-Language is on.

What each type holds

TypeFields and limits
FAQ1 to 200 items, each a Question (up to 500 characters) and an Answer (up to 10,000). Add question and Remove.
Footer1 to 8 columns, each with a Column title (up to 100) and 1 to 50 links (Label up to 100, URL up to 2000, a path like /about or a full address). An optional Copyright line (up to 300) and up to 20 Social links (Platform up to 40 characters, URL a full address starting with https://).
HeaderAn optional Logo (Image URL up to 2000, Alt text up to 200), 1 to 30 Navigation items (Label up to 60, URL up to 2000) and an optional Call to action (Label up to 40, URL).
AnnouncementMessage (up to 500 characters), Severity (Info, Warning or Success), Dismissible by the user, optional Scheduling (Starts at and Ends at; the end must be after the start, otherwise the entry is not saved) and an optional Call to action (Label up to 60, URL up to 2000).
Rich textAn HTML body up to 200,000 characters. Brainerce does not clean a Rich text or Page body when you save it (that is how a custom design survives), so storefronts are expected to clean this HTML before showing it, and you should avoid inline scripts. Link and image address fields in Content (footer and header links, the announcement button, the Open Graph image) refuse javascript: and data: addresses.
PageURL slug (lower-case letters, digits and hyphens, up to 80; leave blank to derive it from the name; a name with no Latin letters or digits, such as a Hebrew-only name, cannot be turned into a slug, so type one in Latin letters), Title (up to 200), Body (up to 500,000 characters) and an SEO section: SEO title (up to 70), Meta description (up to 200) and Open Graph image URL (up to 2000).

An empty FAQ, footer or header is refused: each needs at least one item, column or navigation entry. The FAQ, rich text and page editors have an AI Content helper that writes or improves your text and uses AI credits.

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. An AI-built 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).

Pages with a custom design open in text-only mode

A page built by a developer or an AI builder often carries its own design: sections, columns, classes and tracking attributes inside the page body. The visual editor cannot keep all of that. If it rewrote the page when you save, the design on your storefront could disappear, and typing one letter is enough.

This protection is on for every store, existing and new. It is only off for a store that explicitly opted out. When it is on:

  • A page that the visual editor would change opens in text-only mode. The editor shows the label Text only. Your design stays as it is. and lists the words of the page as blocks you can edit in place: headings, paragraphs, list items, table cells, quotes, links and buttons, and the description of an image. Nothing is changed by opening it.
  • Only the text you edit is written back. Every other part of the page stays exactly as it was stored. If a change could not be applied safely, nothing is changed and the editor says so.
  • A page that has no text to edit says There is no text to edit on this page. Use Edit HTML source for it.
  • Edit HTML source opens code view, where you edit the HTML exactly as it is stored. It is not reformatted. Back to text editing returns to the blocks.
  • An image that has several sizes set in the code cannot be replaced from the editor; it is replaced in the code.
  • The visual editor is not offered for these pages, and there is no button that converts them to it. Full-screen editing is not available on these stores either.
  • Opening a page, clicking inside it, or switching between text and code view and saving does not change the page. Saving with no change sends nothing.

Brainerce does not convert existing pages by itself, and it does not keep earlier versions of a page. Pages made of headings, paragraphs, lists, links and basic formatting open in the visual editor. A page with an image the editor inserted, a video or embedded player, a table made elsewhere, comments, or any custom design opens in text-only mode, because the visual editor would rewrite those too. If a page lost its design before this protection was on for your store, Brainerce does not keep earlier versions, so restore it from your own copy or a backup and edit it as code from now on.

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.

Who can do what. Opening Blog needs View blog; creating, editing, publishing, duplicating and deleting need Manage blog. Owner and Manager have both; Staff and Viewer can only look.

The list is one table with columns Image, Title, Excerpt, Author, Category, Tags, Status, Channels, Published and Updated; dates are shown in your dashboard language. There is no title search and no Draft, Scheduled or Published filter on the list, and a post with no category simply has an empty Category cell (the word "Uncategorized" is not shown). Title, excerpt, author, category and tags can be edited in the cell; the excerpt is plain text.

Blog post fields

FieldWhat it takes
TitleUp to 200 characters.
URL slugLetters (any language), digits and hyphens, starting with a letter or digit, up to 200 characters. Made from the title; must be unique.
CategoryFree text, up to 80 characters.
ExcerptA short summary for post listings, up to 500 characters.
BodyUp to 500,000 characters. The AI Content helper can write or improve it and uses AI credits. When you save, scripts, event handlers (such as onclick) and javascript: links are removed from the body and the excerpt, and so are embedded players (an iframe or a video tag): a blog post cannot hold one. Headings, lists, links, images, tables, quotes, code and text colour and alignment are kept.
Cover image and Cover image alt textAn image address (up to 2048 characters) and alt text (up to 200). Add cover image picks from your media library. An address that starts with javascript: or data: is refused; use a full https:// address.
AuthorUp to 100 characters.
TagsPress Enter or comma to add each one.
Publish dateEmpty publishes immediately when you click Publish. A date in the future schedules the post: its status shows Scheduled and it goes live at that time.
Sales channelsEmpty shows the post on every channel. Up to 50.
StatusDraft, Scheduled or Published. Unpublish returns a post to draft.

With Multi-Language on, a Translations section holds a version of the post for each language.

Duplicate (in a post's row menu, or for several selected posts at once) makes a draft copy with "(Copy)" added to the title and "-copy" added to the slug (a post called "Summer care guide" becomes "Summer care guide (Copy)"). The copy is never published and has no publish date, so it cannot appear on your storefront until you publish it. Use it as a starting point for a similar article.

Deleting a post is permanent. Content and Blog have an Export and import button next to New content and New post for editing many entries in a file (see Edit your data in a file). It appears only when your role may export that data and the store has it switched on, so if you do not see it, ask an owner. The list also has a Channels column so you can choose which storefronts see each entry.

Blog post SEO: title, description, and social image

Every blog post has its own search and social settings, right in the post editor:

FieldWhat it controls
SlugThe 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 titleThe headline Google shows for this post, up to 70 characters. Falls back to the post title when empty.
SEO descriptionThe snippet under the headline in Google results, up to 200 characters. 150 to 160 characters works best.
OG imageThe image address shown when the post is shared on WhatsApp, Facebook, or X, up to 2048 characters. 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?