Quick challenge: What's the ONE macro you can't live without?

[#1]

Hey everyone! I'd like to know about your go-to macros. We all have that one macro we drag onto every page. Mine's the Info Panel for quick tips, warnings, and important notes. It's such a small thing, but it makes pages feel more organised and helps readers spot key information immediately. I've also started using it to highlight "pro tips" in our internal guides, and people actually read them now.

Your turn:

• What macro do you use most?
• Any clever ways you've customised it or combined it with other macros?

Drop your answers below, and let's build a community macro cheat sheet together. If you're new to Confluence, feel free to ask questions about macros you've seen but don't know how to use. This is a great place to learn from each other. 

[Neve Keable]

Got to be Content tree (page tree) for me. I find it's a really great way of making a group of Confluence pages more navigable . I've shown it to a few people who have been making lists of pages manually(!) and they're always pleased to adopt this macro so it stays up-to-date. 

I use it alongside other macros such as the Info Panel, Excerpt Include, image and Jira macros to create attractive landing pages for a group of work that clearly show what is contained. I like making pages like this to help break down a Confluence space into smaller groups. 

[zoltanersek _outpostlabs_dev_]

I use Page Index and the table of contents macro very often. 

[Anwesha Pan]

For me it’s its few macros that I cannot live without:

• Table of Contents 
• Info panel
• Button (to create Tabs)
• Advanced expand
• Page search
• excerpts

[Abi Brown- Kolekti]

I love the advanced expand - it makes my pages look so organised and colourful! Also prob most used is tables & table of content! 

[Barbara Szczesniak]

Well, some of those mentioned already sound like they come with 3rd-party apps. 

For myself:

• Anchor, so I can link to a heading or step on a(nother) page
• Expand for long pages of reference data
• Filter by label; I put a version number label on each page that I change for a release, and then I use this macro to get a list of all of the pages I've changed for the release to make sure I include them in my documentation release notes