Confluence Directory Structure |verified| (2027)

Within each Space, aim for a "shallow and wide" tree rather than a "deep and narrow" one. Ideally, a user should reach any document in . Tier 1: The Landing Page (Dashboard) Every space needs a homepage. Use this to highlight: The space mission statement. Key stakeholders and "who to ask" for help. Links to the most frequently accessed Tier 2 pages. Tier 2: Category Folders (Parent Pages) These act as containers. Common Tier 2 folders include: Resources: Templates, brand assets, or tool links. Meeting Notes: Organized by month or workstream. Processes/SOPs: The "How-to" guides for the team. Archives: For outdated material (don't delete, just move). Tier 3: Content Pages (Child Pages)

Page Hierarchy (Parent and Child pages). This allows teams to create "folders" by nesting sub-pages under a main landing page. 4. Attachments and Blog Posts Attachments: Files (PDFs, images, spreadsheets) are not stored in a separate directory; they are attached directly to specific pages. Blog Posts: These provide a chronological stream of updates. Unlike pages, they are organized by date rather than hierarchy, making them ideal for announcements. 5. Labels (The Connective Tissue) Because the hierarchy is relatively flat, Confluence uses confluence directory structure

If you’ve ever felt like you’re wandering through a digital labyrinth trying to find a single project spec, you aren’t alone. Without a deliberate , a workspace quickly devolves into a "document graveyard." Within each Space, aim for a "shallow and

: To keep information discoverable, most experts recommend keeping the nesting to 2–3 levels deep . Use this to highlight: The space mission statement