---
title: "How Buuk works"
url: "/help/buuk/how-buuk-works"
updated: "2026-11-13T16:22:26.094Z"
---
# How Buuk works

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.

![The Buuk dashboard home: published pages, drafts, views, missed searches, and recent activity.](/api/media/assets/a0c60e34-d018-4c8a-88e7-3cd25157873e)

## 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 [Help Centre → Manage tabs](./docs-collections).

| Collection | Editor home | Public tab |
| --- | --- | --- |
| Documentation | Help Centre → Help | Help |
| FAQ | FAQ | FAQ |
| Guides | Help Centre → Guides | Guides |
| API reference | Help Centre → API Reference | API Reference |
| Changelog | Help Centre → 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

1. Create or import an article. Save is automatic. Version history keeps earlier snapshots.
2. Check the public layout with Preview in help center. Preview does not make a draft public.
3. Publish when the copy is ready. The URL stays stable as long as the slug does not change.
4. Optional: schedule a publish time, or require editorial approval before anyone can ship.

> [!WARNING]
> Unpublished work is out of public search, the widget, and Ask AI for readers. Treat drafts as internal until you publish.

## 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 lists the articles readers voted unhelpful, and Freshness scores how current each page is, so you know what to rewrite next.

## A typical week

1. **Ship product**
   Your app changes. GitHub releases, tickets, and Slack questions show up as usual.

2. **Review suggestions**
   Open [**Suggestions**](./suggested-updates). Accept the ones that should become docs. Leave the rest.

3. **Edit and publish**
   Rewrite in the editor. Check Preview. Publish. Freshness and search catch what you missed.

> [!NOTE]
> You are looking at that loop running on Buuk itself. Open any article from Help Centre in the dashboard to edit this copy.