Wiki Structure

Wiki Structure

The Acepe wiki should be a portal, not a second competing architecture authority.

Recommended structure

Page	Job
Home	Top-level portal and fastest entrypoint
Architecture-Concepts	Reading order into the core architecture docs
Wiki-Structure	Explain how the wiki and repo docs relate

Source-of-truth rule

%%{init: {'theme':'base','flowchart': {'curve': 'basis', 'nodeSpacing': 28, 'rankSpacing': 34}, 'themeVariables': {'fontFamily': 'Inter, ui-sans-serif, system-ui', 'primaryTextColor': '#1f2937', 'primaryBorderColor': '#9ca3af', 'lineColor': '#6b7280', 'tertiaryColor': '#ffffff', 'background': '#ffffff'}}}%%
flowchart LR
    n_wiki("Wiki portal") --> n_repo("Versioned repo docs")
    n_repo --> n_code("Code changes / PRs")

    classDef green fill:#B4E6C8,stroke:#8FB9A2,color:#1f2937,stroke-width:1px;
    classDef yellow fill:#FFEBB4,stroke:#D8C58E,color:#1f2937,stroke-width:1px;
    classDef purple fill:#D2BEF0,stroke:#A999C4,color:#1f2937,stroke-width:1px;

    class n_wiki yellow;
    class n_repo purple;
    class n_code green;

Loading

What belongs where

Belongs in wiki	Belongs in repo docs
Navigation	Canonical architecture intent
Reading guides	Ownership rules and invariants
Entry pages and doc map	Domain model definitions
Pointers to deeper docs	Versioned examples tied to code

Rule of thumb

If a statement should be updated in the same pull request as a code change, it probably belongs in docs/concepts/ inside the repo, not only in the wiki.