Overview
The Knowledge base is your organization's customer-facing article library. It is separate from the Scrambl Help Center you are reading now: the Scrambl Help Center explains Scrambl, while your Knowledge Base explains your own products, services, policies, and support processes.
How content is organized
| Part | Purpose |
|---|---|
| Categories | Group related articles and set the order customers see on the public home page. |
| Articles | Provide a title, formatted content, and short excerpt for lists and search. |
| Draft / Published status | Controls whether an article is private working content or visible on the public site. |
| Settings | Controls whether the site is live and sets its title, description, accent color, and public URL. |
A good information architecture
- Organize around customer goals, not your internal departments.
- Use category names such as Getting started, Billing, and Troubleshooting.
- Give each article one primary question to answer.
- Put the shortest path to success near the top, then add context and edge cases.
- Use the same words customers see in your product and emails.
Publish deliberately: Keep the public site disabled while building the initial library. Enable it after the navigation, core articles, links, and mobile layout have been reviewed.
Recommended launch set
- A Getting Started category with setup and first-use guidance.
- A short account or access section for common sign-in questions.
- Documentation for the three to five workflows customers use most.
- A troubleshooting article for each high-volume support issue.
- Billing, cancellation, privacy, and contact policies where relevant.