| Criterion | Score (1=poor, 5=excellent) | Notes | |-----------|-----------------------------|-------| | Logical depth (≤5 levels) | | | | Consistent naming | | | | Easy to find key pages | | | | No orphan pages | | | | Archive of outdated content | | | | Permissions are clear & inherited | | | | Pages have review dates | | | | Macros enhance navigation | | |
: Act as the "chapters" or main sections of your project. confluence page tree
| Problem | Fix | |---------|-----| | Tree too deep | Collapse related subpages under a summary page | | Duplicate names | Rename: Budget Q1 → Finance – Budget Q1 | | No TOC on long parent | Insert Table of Contents macro | | Orphan page | Link it from at least one parent or index page | | Old decisions mixed with active docs | Move closed decisions to _Archive/Decisions/ | | Criterion | Score (1=poor, 5=excellent) | Notes
The is the backbone of information architecture within Atlassian's collaborative workspace. Unlike traditional folder-based systems, it provides a dynamic, hierarchical view of pages within a space, allowing teams to see how documents relate to one another at a glance. : The page tree is always visible in
: The page tree is always visible in the left-hand sidebar, highlighting your current location and allowing for quick navigation. How to Create and Manage Your Hierarchy
Ultimately, the Confluence Page Tree is a manifestation of a company’s collective mind. A chaotic, disorganized tree often reflects a chaotic, disorganized workflow, where roles are unclear and projects lack definition. A clean, logical tree reflects a team that values clarity, process, and accessibility. It bridges the gap between the isolated author and the collaborative whole.