Confluence Directory Structure !link!

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

For cross-functional initiatives with a specific end date (e.g., "2024 Product Launch"). confluence directory structure

: To keep information discoverable, most experts recommend keeping the nesting to 2–3 levels deep . | Aspect | Installation Directory | Home Directory

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 Using (like [Draft] , [Final] , or [SOP]

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

: Every piece of content lives within a Space , which acts as the top-level container (e.g., a "Product" space or a "Team" space).

This is where the application code lives. It is created when you unzip the Confluence installer.