Repositories, Spaces, pages and generations
DocuWriter separates source code from the documentation you maintain. Understanding these objects helps you choose the correct action.
| Concept | What it represents |
|---|---|
| Provider connection | Authorization to access a GitHub, GitLab, Bitbucket or Azure DevOps account. |
| Imported repository | Code from a particular repository and branch, available to source-backed workflows. |
| Space | A documentation collection with pages, folders, sharing settings and optional repository links. |
| Page | Editable content inside a Space. A folder organizes pages; an external link points elsewhere. |
| Generation | A saved AI output, with its own generation history and actions. A generation can be added to a Space. |
| Autopilot repository link | Settings that connect a Space to a repository's events for ongoing documentation suggestions. |
Connections do different jobs
Authorizing a provider does not by itself generate documentation. Importing a repository does not automatically publish a Space. Linking a repository for Autopilot determines which source changes should be considered for that Space.
One Space can bring together documentation for multiple repositories through its content and repository links. A Full Tree run starts from the source selected for that run; review the resulting scope before treating it as documentation for an entire multi-repository system.
Choose the output shape
Use Full Tree Documentation for a task- or topic-organized set of pages. Use Codebase Documentation when you specifically want one document per selected source file. Use Custom prompts for a focused answer using selected repository files.
Manual edits and a new AI generation are different actions. Generation can consume credits; reading and organizing existing pages does not create new generated content. See Credits and usage.
Updated