Blog

Blog posts are Markdown files in the storefront's public/blog folder, not database records.

The admin at Content → Blog lists them and edits three things in each file — the title, the description, and the body — and rewrites the file on save.

A post is published at /blog/ plus its filename.

Because the file is the source of truth, the admin is an editor for part of it rather than an owner of all of it. Everything the editor does not touch survives a save untouched.

Writing a post

1. Open Content → Blog. Tabs split the list into All, Published, and Drafts.
2. Open a post and edit its title, description, and body. The body uses a visual Markdown editor.
3. Save.

Only three things are rewritten on save — the title line, the description line, and the body:

title
description
body

Every other detail in the file — the cover image, the publish date, the author, any linked products — is left exactly as it was.

Adding a post

There is no New post button, because a new post is a new file.

Adding one means adding a .md or .mdx file to public/blog with the fields the storefront expects.

Required:

title
description
publish date
author block

Optional:

cover image
update date
list of product slugs to show inside the post

Hiding a post

Mark it as a draft in the file. A draft post is:

• Not listed
• Not served at its URL
• Not built as a page

It cannot be found or indexed. There is no half-hidden state.

A future date does not hold a post back

A post whose publish date is in the future shows a Draft badge in the admin, but it is still live on the storefront.

The date orders the list. It does not gate the post, and there is no scheduler.

If you want a post held until a date, it has to be a draft until then.

When the visual editor is bypassed

Some posts open as raw Markdown instead of in the visual editor.

That happens when the post contains components or Markdown tables. The visual editor cannot represent either, and would strip them out on save — so it steps aside rather than quietly destroying them.

What the description does

The description is what search engines and social previews show, so keep it under about 160 characters.

Each post also emits article structured data built from:

• Its title
• Its description
• Its cover image
• Its publish date
• Its author

Deciding where to make a change

Use the admin editor for wording — the title, the description, the body. That is the whole of what it can change.

Edit the file directly for anything else: the cover image, the publish date, the author, the linked products, or the draft flag that hides the post.

Add a file, not a post, when you want something new. There is no button for it because there is nothing in a database to create.

Before reaching for the admin, the question is:

Is the thing I want to change one of the three lines the editor rewrites, or does it live elsewhere in the file?

Related