Buuk is help-center infrastructure with an editorial gate. Content lives in a workspace. Editors draft, organize, and review. Customers only see published pages on the public site, in search, in Ask AI, and in the widget.
1. A workspace is the unit of docs
Each workspace has a name, a slug, branding, members, and collections. The public URL looks like app.getbuuk.com/help/your-slug. On Growth you can attach a custom hostname such as docs.yourproduct.com.
Owners and editors can publish. Viewers can read drafts in the dashboard without changing live pages.
2. Collections are how the public site is structured
A full docs site (this one) turns on five collections. You can enable a subset in Customise → site profile.
| Collection | Editor home | Public tab |
|---|---|---|
| Documentation | Articles | Help |
| FAQ | FAQ | FAQ |
| Guides | Docs → Guides | Guides |
| API reference | Docs → API Reference | API Reference |
| Changelog | Docs → Changelog | Changelog |
Sections and folders live under a collection. Leaf articles are pages. Folders are collapsible in the sidebar so a long nav stays scannable.
3. Draft, preview, then publish
- Create or import an article. Save is automatic. Version history keeps earlier snapshots.
- Preview the public layout from Help center preview. Preview does not make a draft public.
- Publish when the copy is ready. The URL stays stable as long as the slug does not change.
- Optional: schedule a publish time, or require editorial approval before anyone can ship.
4. AI is a writing assistant, not the publisher
Ask Buuk in the dashboard can draft an article, rewrite a section, or point you at settings. When a draft walks through product UI, Buuk can attach screenshots from your app URL — still only in the draft. Suggested updates turn tickets, Slack threads, GitHub releases, Linear issues, missed searches, and “not helpful” feedback into a review list.
Accept applies or opens a draft. Edit before you publish. Dismiss if the docs are already correct. Buuk never ships a suggestion on its own.
5. The public help center is the customer surface
- Search across published articles
- Optional AI answers grounded in those articles, with citations
- Helpful / not helpful feedback on each page
- Changelog reactions and comments (no Buuk login required)
- Optional embeddable widget with search, chat, announcements, and voice
6. Analytics close the loop
Reporting shows views and searches. Missed searches and unanswered Ask AI questions become suggested updates. Doc health and Freshness score pages that are thin, stale, or unverified so you know what to rewrite next.
A typical week
Ship product
Your app changes. GitHub releases, tickets, and Slack questions show up as usual.
Review suggestions
Open Suggestions. Accept the ones that should become docs. Leave the rest.
Edit and publish
Rewrite in the editor. Check Preview. Publish. Freshness and search catch what you missed.