: To avoid the rigid limits of a single directory, many teams use Confluence's tagging/labeling system to group related content that might live in different parts of the hierarchy. Best Practices for Organization
: Every piece of content lives within a Space , which acts as the top-level container (e.g., a "Product" space or a "Team" space).
| Aspect | Installation Directory | Home Directory | |--------|------------------------|----------------| | Content | Binaries, libraries, webapp | Data, attachments, config, logs, indexes | | Change frequency | Rare (upgrades only) | Constant (user actions, uploads) | | Backup required? | No (can be re-downloaded) | Yes (must be backed up regularly) | | Cluster share | Not shared | Shared home must be on NAS/SAN for Data Center | confluence directory structure
This is the for data persistence. It contains all user-generated content, attachments, indexes, plugins, and configuration overrides. Backups must include this entire directory.
A great follows the path of least resistance. By using clear Spaces, a disciplined three-tier hierarchy, and consistent naming, you turn Confluence from a cluttered storage bin into a high-speed knowledge engine. : To avoid the rigid limits of a
Ensure that the directory structure isn't hiding important info behind accidental "restricted" locks.
Mastering Your Confluence Directory Structure: A Guide to Organized Collaboration | No (can be re-downloaded) | Yes (must
| Directory | Content Description | |-----------|----------------------| | /attachments | Versioned file attachments (stored by numeric ID; the database maps IDs to page names). | | /backups | Automated site backups (XML format) and support zip files. | | /bundled-plugins | Pre-packaged plugins shipped with Confluence. | | /data | Internal H2 database (if not using external DB) and Lucene search index. | | /index | Search index fragments for faster lookups. | | /logos | Site, space, and profile logos. | | /plugins-cache | Cached plugin descriptors and web resources. | | /plugins-osgi-cache | OSGi bundle caches for plugin management. | | /restore | Temporary location during space or site restores. | | /shared-home | Clustering directory (Data Center only) for shared resources across nodes. | | /temp | Temporary working files (e.g., export temp, thumbnail generation). | | /thumbnails | Cached image thumbnails (scaled versions of attachments). | | /viewfile | Temporary cache for file downloads before streaming. |
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