Confluence Page Structure ^new^ Official

Use page layouts to create columns. A 2-column layout (content on the left, metadata/links on the right) is a classic documentation standard.

Structure is only maintained if users follow the process. The workflow for creating a page should be: confluence page structure

Use the Expand macro to hide secondary details like raw data or long code blocks, keeping the main narrative clean. Summary Checklist for Page Structure: Is the page nested correctly? (No more than 3 levels deep). Does it have a Table of Contents? Are Heading tags (H1, H2, H3) used correctly? Are there clear Action Items? (Use the /action command). Is it labeled? Use page layouts to create columns

The "Drawers." These are high-level containers for teams (e.g., Marketing, Engineering) or projects. The workflow for creating a page should be:

By enforcing a rigorous , you reduce "search fatigue" and ensure that your team spends more time doing the work and less time looking for the instructions.