Build polished pages, portals, and navigation in Confluence

The approach that works

Building a polished Confluence hub is a layered process: plan the structure, assemble it with layout macros, impose navigation, and lock the design into reusable templates. Each layer solves a different failure mode — confusion, flat pages, dead-end reading, and inconsistency — and together they turn Confluence into a real intranet or portal builder. The steps below walk through each layer and the decisions it involves.

1. 1

   Plan the page structure first

   Before touching the editor, sketch the sections the page needs: a hero that states the purpose, a card grid for the main topics, tabs or accordions for detail, and a clear call to action at the foot. Planning on paper (or a whiteboard) is faster than re-arranging macros later, and it forces you to decide what the page is for before you start decorating it.

2. 2

   Assemble with layout macros

   Use page-builder macros — hero, cards, tabs, pricing, buttons, galleries, call-outs — to build the page visually, the way you would in a landing-page tool. Drop a hero at the top to anchor the page, lay the main content into cards so each tile is a single idea, and push dense or optional detail into tabs so the overview stays readable.

3. 3

   Number headings for stable references

   Apply auto-numbered headings so the outline reads like a real document — 1, 1.1, 1.2, 2 — and so cross-references like "see section 3.2" actually resolve. Choose a numbering style (decimal, Roman, legal) that matches the document type, and let the macro renumber automatically as you add, remove, or reorder sections, so the numbers are never wrong by hand.

4. 4

   Add Previous/Next navigation for page series

   For a runbook, onboarding flow, or multi-page guide, add Previous/Next buttons so a reader can move through the sequence in order without hunting for the next page in the sidebar. Use this whenever a set of pages is meant to be read linearly; for reference pages that are landed on independently, a table of contents and clear headings matter more than pagination.

5. 5

   Apply a consistent theme

   Use a global theme editor to set the colour palette, button styles, and spacing once, so every hero, card, and call-out across the space matches. Consistency comes from defining the look in one place and reusing it, not from re-styling every macro by hand — and a single theme is what lets you re-skin the whole intranet in minutes when the brand changes.

6. 6

   Save and reuse templates

   Once a layout works, save it as a master template and reuse it across hubs so every portal in the space shares the same structure and look. Pair the template with a short author guide — what goes in the hero, how many cards, where the call to action lives — so contributors fill the structure rather than reinventing it, and the space stays coherent as it grows.

This solution is for you if…

• ✓Internal comms and HR teams building intranet hubs, onboarding flows, and people portals
• ✓Product and marketing teams creating landing-style pages for internal launches
• ✓Knowledge managers organizing long, multi-page documentation and runbooks
• ✓IT and operations teams publishing status dashboards and service catalogs
• ✓Anyone who wants a Confluence page that looks intentional rather than like a draft

Read the guides

• → Build Modern Confluence Pages Hero Articles Qr Forms
• → Auto Number Headings Confluence
• → How To Use Numbered Headings Confluence
• → Faq Confluence Page Navigation Apps
• → Confluence Numbered Headings Comparison