How to Create a Wiki in Confluence (2026 Guide)
Confluence is the most widely used wiki platform for engineering and product teams, especially those in the Atlassian ecosystem. Its space-based organization, page hierarchy, and deep Jira integration make it a natural choice for technical documentation.
This guide covers how to set up a well-organized Confluence wiki from scratch, including space structure, page templates, permissions, and the maintenance habits that keep a wiki useful.
Step-by-step guide
Step 1: Plan your space structure
Create separate Confluence spaces for different knowledge domains: Engineering, Product, Design, Operations, and Company-wide. Each space has its own permissions, page tree, and search scope. Avoid putting everything in one mega-space; it becomes unsearchable within months.
Step 2: Set up the page hierarchy
Within each space, create a top-level page tree. For a Product space: Home > Roadmap, PRDs, Meeting Notes, Processes, Templates. Use child pages for individual documents. Keep the hierarchy 3 levels deep maximum; deeper nesting makes content hard to find.
Step 3: Create page templates
Go to Space Settings > Content Tools > Templates. Create templates for your most common document types: PRD, Meeting Notes, Post-Mortem, RFC, Onboarding Guide. Each template should have pre-filled sections with placeholder text explaining what to write in each section.
Step 4: Configure permissions
Set space-level permissions in Space Settings > Permissions. Give the relevant group "View" access, and restrict "Edit" to the owning team. For sensitive spaces (HR, Security), restrict view access. Use page-level restrictions sparingly; they create confusion about who can see what.
Step 5: Add Jira macros and integrations
Use the Jira Issues macro to embed live Jira queries in wiki pages. For example, embed all open P0 bugs on the Engineering home page, or show the current sprint board on the team page. Use the Jira Roadmap macro to embed your roadmap timeline directly in the Product space.
Step 6: Set up a maintenance cadence
Assign wiki gardeners: one person per space responsible for monthly cleanup. Archive pages not updated in 6 months. Fix broken links. Update the page tree if new sections are needed. A wiki without maintenance becomes a graveyard.
Common mistakes
One giant space for everything
Putting all documentation in a single space makes permissions impossible to manage and search results noisy. Separate spaces by team or domain. Cross-link between spaces when needed.
No page templates
Without templates, every document has a different structure. This makes it harder to find information and harder for new team members to contribute. Templates enforce consistency without limiting creativity.
Deep nesting
Pages nested 5-6 levels deep are invisible. Users cannot navigate to them and search does not surface them well. Keep hierarchies shallow (3 levels max) and use labels for cross-cutting categorization.
No archival process
Old, outdated pages that rank alongside current documentation erode trust in the wiki. Establish a quarterly archival process: pages not updated in 6 months get reviewed and either updated or archived.
Tips
- Use Confluence labels to create cross-space topic views (e.g., all pages labeled "onboarding")
- Pin the most important pages to the space home page using the Content Report macro
- Use the Page Properties macro to create structured, queryable metadata on wiki pages
How Vantage helps
Vantage connects to Confluence as a context source. When you create a project, import existing Confluence pages as context for PRD generation. The AI grounds new specs in your team's existing documentation, ensuring consistency with established processes and decisions.