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

PartPurpose
CategoriesGroup related articles and set the order customers see on the public home page.
ArticlesProvide a title, formatted content, and short excerpt for lists and search.
Draft / Published statusControls whether an article is private working content or visible on the public site.
SettingsControls 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.

  1. A Getting Started category with setup and first-use guidance.
  2. A short account or access section for common sign-in questions.
  3. Documentation for the three to five workflows customers use most.
  4. A troubleshooting article for each high-volume support issue.
  5. Billing, cancellation, privacy, and contact policies where relevant.