Publish content with the CMS
Write, publish and organise blog posts, legal pages, a changelog and a roadmap in English and Chinese from the admin console.
The CMS module publishes your blog at /blog (with an RSS feed at /blog/rss.xml), legal pages at /legal/<slug>, a /changelog and a /roadmap. Every save keeps a revision and runs SEO checks.
Before you begin
- A project that runs locally. See Quick start. The
cmsmodule is part of the base repository and shows as CMS under Content in the admin sidebar. - An admin account with
cms.readto open the pages andcms.writeto create or save entries and add taxonomy terms. The Content Manager role holds both.
Footer links need published entries
The public footer links to /blog, /legal/privacy and /legal/terms. Publish the privacy and terms legal entries after installing, or those links lead to a not-found page.
Create an entry
Start a new entry
Go to Content → CMS (/admin/cms). On the Posts tab, click New entry and choose the Type: Blog post, Page, Legal, Changelog, Roadmap or Showcase. The type cannot be changed later.
Fill in the fields
- Title, Excerpt and Markdown for the content. Markdown renders
#and##headings and paragraphs. - Slug: saved in lower case with other characters turned into hyphens, so
Launch Notesbecomeslaunch-notes. - Locale: English or 中文. A Chinese entry appears under
/zh. - Category and Tags (comma separated): free text.
- SEO title and SEO description.
- OG image: the social preview image path or URL. Leave it blank to keep the current image.
Create it
Click Create entry. The entry is saved with its first revision and opens in the editor. Type, slug and locale must be unique together; creating never replaces an existing entry.
Publish an entry
Open the entry
Click the entry's title on its tab to open the editor. Roadmap entries have no tab; open one at /admin/cms/editor/cms_roadmap_<locale>_<slug>.
Publish
Set Status to Published and click Save content. The entry appears on its public page for that locale.
Setting it back to Draft or Archived removes it from listings, and its page shows the not-found state. The first publish date is kept and reused when you publish again. Every save records a revision; the Revisions card shows the count.
| Tab | Shows |
|---|---|
| Posts | Blog posts, published on /blog |
| Pages | Page and showcase entries |
| Changelog | Entries published on /changelog |
| Legal | Entries published on /legal/<slug> |
| Taxonomy | Categories, tags and modules with usage counts |
| SEO | Check results from every save |
Fix SEO warnings
Open the SEO tab
Every save adds three checks for the entry: an SEO title between 10 and 70 characters, an SEO description between 50 and 160 characters, and a kebab-case slug.
Fix and save again
A check that does not pass shows warn. Adjust the field in the editor and click Save content.
Add taxonomy terms
Open Taxonomy
Open the Taxonomy tab.
Fill in Add term
Choose the Type (Category, Tag or Module) and the Locale, and fill in Label, Slug and, optionally, Description.
Save
Click Add term. The term appears in the table; its usage counts entries whose category or tags match its slug.
Verify
- Create a Blog post, set Status to Published and click Save content.
- Open
/blog: the post is listed, opens at/blog/<slug>, and appears in/blog/rss.xml. - In the repository, run
pnpm validate:cms.
Troubleshooting
"An entry with this type, locale and slug already exists."
New entry found an entry with the same type, locale and slug. Open the existing entry from its list, or use a different slug.
"CMS slug, locale, and type must be unique."
Another entry already uses that type, slug and locale. Change the slug.
A post or legal page shows "not found"
The entry is a draft or archived, or its locale does not match the URL. Set Status to Published and open a Chinese entry under /zh.
An entry does not appear on /blog
Listings show only published entries whose locale matches the URL. A Chinese entry appears on /zh/blog, not /blog.
"No CMS entry has this id."
The editor address points at an entry that does not exist. Open the entry from its list.