Introduction Unlike traditional file systems (Windows, macOS) that use nested folders, Atlassian Confluence employs a unique architecture based on Spaces , Pages , and Parent-Child relationships . Understanding this paradigm is critical for creating a scalable, searchable, and maintainable knowledge base. This paper outlines best practices for structuring content to improve findability, governance, and collaboration. 1. Core Components (The "Folders" Analogy) | Traditional Term | Confluence Equivalent | Function | |----------------|----------------------|----------| | Root Directory | Space | High-level container for a team, project, or department. | | Subfolder | Parent Page | A top-level page that serves as a table of contents or category. | | File | Child Page | A page nested under a parent; inherits permissions and styling. | | Path | Breadcrumbs & Page Tree | Visual navigation showing hierarchy. |
Introduction Unlike traditional file systems (Windows, macOS) that use nested folders, Atlassian Confluence employs a unique architecture based on Spaces , Pages , and Parent-Child relationships . Understanding this paradigm is critical for creating a scalable, searchable, and maintainable knowledge base. This paper outlines best practices for structuring content to improve findability, governance, and collaboration. 1. Core Components (The "Folders" Analogy) | Traditional Term | Confluence Equivalent | Function | |----------------|----------------------|----------| | Root Directory | Space | High-level container for a team, project, or department. | | Subfolder | Parent Page | A top-level page that serves as a table of contents or category. | | File | Child Page | A page nested under a parent; inherits permissions and styling. | | Path | Breadcrumbs & Page Tree | Visual navigation showing hierarchy. |