Practical answers, not long threads
Short, focused articles that solve specific problems without unnecessary theory.
Built from real questions
The knowledge base grows from real issues encountered in production, not hypothetical scenarios. Articles are often written after patterns show up in support or internal discussions.
How to guides
Clear steps for common tasks, from basic content updates to everyday admin work in Posts, Menus and other modules.
Troubleshooting
Fix issues without digging through logs blindly. Articles focus on symptoms, causes and concrete resolutions.
Best practices
Lessons learned from real deployments, covering structure, permissions and long term maintenance.
How the knowledge base is organized
The knowledge base complements the main documentation and tutorials. Documentation explains concepts, tutorials walk through full setups, while the knowledge base answers specific, focused questions.
By topic
Articles can be grouped around areas such as content editing, admin workflows, security and integrations, using the same structure as the main modules.
By audience
Entries can be tagged internally as most relevant for editors, admins or developers, so you can quickly point the right people to the right answers.
By frequency
Commonly referenced topics are kept short and easy to scan, while more advanced subjects link out to deeper docs when needed.
Powered by the Q&A module
Knowledge base articles are managed as structured entries in the Q/A content management module. This keeps questions, answers and publishing status consistent with the rest of the admin.
Structured entries
Each article has a clear title, body and language. Editors can search, filter and update content from one place.
Published vs pending
Draft articles stay hidden until they are reviewed and marked as ready to publish, following the same pattern used across the admin.
Module level control
Access to the knowledge base module is controlled through roles in the Users module, so only trusted editors can change public answers.
What makes a good article
Articles are written to be practical first. They describe a problem, show how to recognize it and provide a repeatable way to fix or avoid it.
Focused scope
One article solves one problem. If a topic grows too large, it is split into separate entries with clear titles.
Step by step format
Whenever possible, solutions are described as ordered steps that can be followed and checked quickly.
Links to deeper resources
For broader context, articles can link to the main documentation, tutorials or specific modules such as Security and bots.
Typical knowledge base topics
Over time, the knowledge base can cover the everyday questions your team and clients ask most often.
Content and navigation
Articles about managing posts, categories and menus, using modules like Posts, Categories and Menus.
SEO and visibility
Short answers about page titles, meta descriptions and indexing behaviour, backed by the SEO module.
Admin configuration
Everyday settings, feature flags and environment details, referencing Settings and related modules.
Who the knowledge base is for
Editors and content teams
Quick answers on how to structure pages, posts and navigation without diving into full technical documentation.
Admins and project owners
Articles that clarify permissions, modules and day to day admin operations across the system.
Developers and integrators
Pointers to common pitfalls and integration notes, often linking to API and integrations for deeper details.
Kept in sync with changes
When modules evolve, the knowledge base can be updated alongside the main documentation and changelog. This keeps answers relevant as the product grows.
Linked to releases
New or changed behaviour from releases can be reflected in updated articles instead of leaving old advice online.
Clear deprecation notes
When a pattern is no longer recommended, articles can be marked as outdated and point to newer approaches.
Consistent tone
Knowledge base entries follow the same straightforward tone as the rest of the resources so teams always know what to expect.
Turn repeating questions into clear answers
Use the knowledge base to capture solutions once, then share them across your team and projects instead of rewriting the same replies.
