Brothh docs are authored in the admin app and displayed in the git_book app at docs.brothh.com.

## Authoring

Use **Admin -> Docs** to create docs, categories, revisions, rollbacks, and legal-page overrides. The public reader only displays published docs.

Start with a workflow spec, not a blank page. Each article should explain the reader's task, name the source route, call out the app that owns the behavior, and include a screenshot or figure whenever the UI state could be misunderstood. Drafts are safe to save, but only published docs show on docs.brothh.com.

## Research inputs

Before writing docs, check:

- \`workflow/\` for page and product behavior specs.
- \`C:/Users/nmadd/Desktop/vs_code/er_documentation\` for ER domains and relationships.
- \`C:/Users/nmadd/Desktop/vs_code/my_brain\` for product preferences and integration context.
- The running app in browser for screenshots of each view and section.

## Screenshot convention

When documenting a UI state, upload the screenshot through the Admin article image flow, then include it near the relevant step:

\`\`\`md
{% figure src="https://example.invalid/admin-docs-editor.png" alt="Admin docs editor publish controls" caption="Publish controls in the Admin Docs editor." /%}
\`\`\`

{% figure src="/docs-images/gitbook-home.png" alt="Published Brothh Docs homepage" caption="Published GitBook homepage with product navigation, interactive playground preview, and browse-by-product sections." /%}

## Publishing checklist

- Confirm every linked route exists in GitBook or another Brothh app.
- Confirm legal and help links point to docs.brothh.com when the content is reader-facing.
- Use the slash menu for callouts, figures, tabs, steps, code groups, playgrounds, calculators, glossary terms, and viewer variables.
- Preview the article before publishing and check the public GitBook route after publishing.