User Guide
How to: Build a Tabbed Knowledge Base Page
A step-by-step workflow for building a tabbed hub page that organises content across multiple sections - the most common pattern for IT runbooks, product docs, and team wikis.
Design: Three-Layer Structure
A well-built tabbed page combines three macro layers:
| Layer | Macro | Purpose |
|---|---|---|
| Navigation | Tab Parent Content Mapper | Tabs across the top, each tab = one content section |
| Visibility | Conditional Show / Hide | Different content per audience within the same tab |
| Formatting | Alert, Background, Buttons, Cards | Visual richness and callouts within each section |
Step 1 - Prepare Your Child Pages (for Auto-Tab Approach)
- Create a parent page in Confluence (this will be your hub)
- Create child pages under it - one per tab section (e.g., Overview, Setup Guide, Troubleshooting, Reference)
- Name each child page clearly - the page title becomes the tab label
Step 2 - Insert Tab Parent Content Mapper
- Open the hub page in edit mode
- Type
/→ search Tab Parent Content Mapper → insert it directly on the page - In the config panel, confirm the parent page (defaults to current page)
- Set Sort Order to page tree order or Alphabetical
- Preview - each child page appears as a tab
Step 3 - Add Formatting Inside Tabs
Edit each child page and add rich formatting macros:
- Use Alert for warnings, notes, and important callouts
- Use Background to visually distinguish different sections within a tab
- Use Buttons to link to related Jira boards, external tools, or other pages
- Use Advanced Expand to collapse long reference tables or optional details
→ Alert Macro · Background Macro
Step 4 - Add Audience Visibility (Optional)
If different teams need to see different content within the same tab:
- On the child page (in edit mode), select the content meant for a specific group
- Type
/→ Conditional Show → insert it around the selected content - In the config panel, search for and select the specific users or groups who should see this content
- Test in View mode with a matching user and a non-matching user
→ How to: Create Role-Based Content Visibility
Step 5 - Publish and Verify
- Publish each child page
- Publish the hub page
- Verify tabs appear correctly in view mode
- Test tab navigation - each tab should load the corresponding child page content inline
Maintaining the Hub
- Add a new tab: Create a new child page under the parent
- Remove a tab: Delete or move the child page out of the parent
- Reorder tabs: Drag child pages in the Confluence page tree to reorder them