Tl;dr
Pages are the foundation of pretty much every Confluence space and the stereotypical content type that most people think of when they think of Confluence. To me this makes sense - we’re all used to looking at some form of word-based document.
Features
Pages support a wide range of features that let you craft content. If you’re used to any word processor many of them will feel familiar - although there are some differences! For example, you cannot change font size - instead you can change text into a header. This will both change the font size, but (and more importantly I’d argue) it makes that text a link. This lets you instantly link someone to a specific part of a page - and also works with macros (like Table of Contents) to do some magic.
There’s the regular host of formatting - including things like italics, bolding and underlining. Sections let you make columns on the page to break up content, while font colors and highlighting let you add some color to things.
Pages, however, also have a great feature called “elements” or “macros” that move them far beyond word docs. Macros are essentially small programs that run on a page and do a wide range of things. I won’t detail them all (check out this list for some), but some examples include:
Marcos are where the magic happens, so it’s definitely worth your time to look into them. You should also note that many marketplace apps will add extra macros to your instance - so it’s possible you have more (or less!) than other folks.
In additional, pages support templates - pre-formatted structures. This makes it incredibly easy to spin up content (and saves you a LOT of effort copying/pasting). Templates are unique to the space they’re in, and you can even make your own templates (or edit existing ones). Talk to your space admin to edit or create templates.
Use Cases
Generally unless I know I need a visual space (a whiteboard) or structured data (a database) I use a page. This means I’m mainly using pages to communicate information to my team, including things like:
Other REALLY Similar Content
There are two other content types that are similar to, but substantially different than, pages. I’ll have another “Know Your Content” type post about these, but just be aware they exist!
Live docs might LOOK like a page but they behave slightly differently. They contain all the same editing, permission and collaboration tools, however, instead of requiring you to publish the initial draft (or any updates) a live doc is instantly published. This means teammates don’t have to wait to see whatever the update this.
Blogs also look and feel a LOT like pages, but they fit a different use case. Blogs are intended more for point-in-time updates (think weekly updates, project updates and anything else that once it happens it won’t change). Like pages (and live docs!) they support robust editing options, however, they have one major difference - they’re outside the content hierarchy. Unlike pages, whiteboards, smart links, databases and live docs, blogs appear in a separate section under the content hierarchy. This allows them to be displayed chronologically.
Best Practices
Here’s a few tips and tricks I’ve learned over the years around Pages. By no means exhaustive, but they’ve helped me make engaging, useful content:
Additional Info
Below are some additional resources to help you better use pages. Please drop your comments, questions and other info down below!
Robert Hean
Systems Manager & Trainer
Hean
2 accepted answers
0 comments