How this help center works
The content model, the article blocks, and how search and translations stay in sync, demonstrated on one page.
In Getting started · Updated July 25, 2026
This article documents how the help center itself is wired, and it doubles as a showcase: every block type available in the article editor is used on this page.
Content model
Two collections drive everything. Categories fill the hub grid, and articles belong to exactly one category. An article's optional group name clusters it into a card on the category page, the featured flag lifts it into Top articles on the hub, and nothing shows on the site until published is ticked.
Writing an article
Create it in the admin
In /admin, add a help article: title, one-sentence excerpt, a category, and optionally a group name and order.
Build the body from blocks
Write prose and headings, then insert blocks where they help: callout (six color presets), step-by-step, table, accordion, and images from the media library.
Publish
Tick published. The page, its table of contents, and the search index all update on save; there is no deploy step.
“Good help articles answer the next question too, the one the reader did not know to ask yet.”
Common questions
How does search stay in sync?
Every save flattens the whole body (including block content) into a hidden searchText field per language. The search endpoint matches against title, excerpt, and that flattened text, so results can never drift from the content.
How do Arabic translations work?
Title, excerpt, body, and group are localized fields. Switch the locale picker in the admin to Arabic and translate; anything untranslated falls back to English on /ar automatically.
Where does the table of contents come from?
The On this page rail is generated from the H2 headings in the body. Use H2 for main sections and H3 for sub-points that should not appear in the rail.
How do I add a new callout color?
Presets are defined once in the frontend callout component and mirrored as options on the callout block. Adding one is a small code change; editors then see it as a new choice in the select.
Keep this article updated as the system evolves; it is the onboarding page for anyone who writes help content.