Review and customize the outline

The documentation outline is the map of the Space you are about to create. Review it for reader usefulness before starting page generation.

Check the structure

Begin with orientation and the first successful task. Group related workflows, then add deeper reference material. A reader should be able to tell what a page will answer from its title.

For each section, ask:

• Does this topic exist in the project and matter to this audience?
• Is another page already covering the same task?
• Is the title specific enough to guide a reader?
• Are prerequisite topics earlier in the structure?

Refine the proposal

Use the outline controls to add sections or subsections, rename entries and reorder them. Provide page context where the editor offers it. For example, “Explain how a failed payment is retried, including the states visible to an operator” is more useful than “Add more detail.”

Use Ask for modifications when you want the proposed structure revised with a specific instruction. Wait for that revision to finish, then review the resulting outline again before accepting it.

Accept and generate

On the dedicated Full Tree generator, continue after you have reviewed the outline and start generation from the final step. Acceptance selects the structure for the build; later editing a completed Space is a separate activity.

If you already have a useful documentation set, use Update Documentation Gaps to propose additions and targeted changes instead of rebuilding everything.

Avoid an oversized outline made of repetitive pages. Completeness means the reader's relevant questions are answered with source-supported content, not the largest possible page count.