AURA Content Formatting Macros Tabs LaTeX HTML in Confluence

Custom icons and custom fonts let us match our exact brand guidelines, something our design team genuinely never believed was possible inside Confluence. We upload a handful of SVGs, and suddenly the Buttons, Cards, Dividers, and Panels all carry our own identity rather than generic defaults. It elevated the entire look of our documentation without a single external tool or clumsy workaround, and the whole thing was set up in an afternoon. Our brand finally feels consistent everywhere it appears.

The Buttons alone justify the price for us. Instead of links buried in paragraphs, every page now carries clear, branded calls to action that people actually click. Combined with the Tabs to organize the content behind each step, our processes finally make sense at a glance. It has quickly become one of the most useful additions to our whole setup.

Consistency was our biggest problem before Aura came along. Now, with the shared color palettes and macro templates our admins configured once, every Card, Button, Divider, and Panel across the entire instance matches our brand without anyone having to think about it or reference a style guide. Editors simply pick an approved template and start writing. The whole wiki looks like one company built it deliberately, instead of the patchwork of clashing styles we had before switching to Aura.

LaTeX support is what finally pulled our research team into Confluence. We write equations using the syntax we already know, and they render cleanly on the page in both light and dark mode. Referencing a formula elsewhere without copying it keeps everything consistent across our documentation. It made our technical pages far more precise.