Confluence Directory Structure !!hot!! (Ultimate)

Using (like [Draft] , [Final] , or [SOP] ) helps users identify the status of a document instantly from the sidebar. 4. Leveraging the "Page Tree" and Labels

Would you like a visual diagram (ASCII or Mermaid) of this structure or a checklist for migrating these directories?

For administrators, always ensure the Installation Directory and Home Directory are kept separate. Backing up the Home Directory backs up your data. Backing up the Installation Directory only backs up the software version. This separation allows for easier upgrades (overwrite Install, keep Home). confluence directory structure

Here is a detailed breakdown of both aspects.

In Confluence, the is your highest level of organization. Think of Spaces as separate buildings in a complex. Using (like [Draft] , [Final] , or [SOP]

This is the for data persistence. It contains all user-generated content, attachments, indexes, plugins, and configuration overrides. Backups must include this entire directory.

Are you looking to , or are you setting up a new documentation structure from scratch? webapp | Data

If you are setting up Confluence for the first time, follow these structural guidelines:

| 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 |

Don't rely on Spaces for deep organization. Use the Parent/Child page structure within a Space to organize documents.