Confluence Fundamentals: Spaces, Pages, and Team Documentation That Lasts

Good documentation is a product, not an afterthought

Confluence is Atlassian’s collaborative wiki. It pairs naturally with Jira: Jira tracks the work, Confluence captures the knowledge. This guide covers the fundamentals you need to organise documentation that survives team turnover.

Spaces: Your Top-Level Containers

A space is a self-contained area for a team, project, or topic. Common patterns:

  • Team spaces — one per squad (Platform, Design, Support)
  • Project spaces — one per initiative, archived when complete
  • Knowledge base spaces — customer- or company-facing how-to articles

Pages and the Page Tree

Pages live in a hierarchical page tree. A shallow, well-named tree beats a deep one nobody can navigate. Use the tree to express structure, not folders-within-folders.

A clear page tree turns scattered notes into a navigable knowledge base

Templates Save Everyone Time

Confluence ships with templates for meeting notes, decision records, and requirements. Create your own for anything you write more than twice:

Template Use it for
Meeting notes Recurring stand-ups and reviews
Decision record Capturing why a choice was made
How-to article Repeatable operational procedures

Habits That Keep Docs Alive

  1. Link from Jira issues to the relevant Confluence page so context travels with the work.
  2. Add a "last reviewed" date and owner to important pages.
  3. Archive aggressively — outdated docs are worse than no docs.

The best documentation answers the question someone is about to ask in chat.

What to Learn Next

  • Macros like Table of Contents, Jira Issues, and Excerpt
  • Page permissions and restrictions for sensitive content
  • Confluence + Jira reporting to surface requirements alongside delivery

Arivanandhan Chitheshwaran