Keeping Confluence pages clean when your team relies on metadata

[#1]

Full disclosure: I work at Seibert, the partner of Junovi - the team behind the Properties (and Blueprint Creator) apps for Confluence. This article is about a redesign we recently shipped, but the problem it solves is one almost every Confluence team runs into, so I hope it's useful for all Confluence users.

If your team stores any kind of structured information on Confluence pages: owners, due dates, status, project phase, related pages, etc., you know the quiet tension that comes with it. You want that metadata to be there, consistent and easy to report on. But you also want a page that people actually enjoy reading, not one buried under tables of fields before the first line of real content.

Native Confluence gives you a few ways to handle this (labels, the page properties macro, front-matter tables), but each one asks you to trade something: either the data is hard to structure and report on, or it clutters the top of every page. For a long time, "structured metadata" and "clean pages" felt like a choice you had to make.

That trade-off is exactly what we set out to remove in the latest version of Properties. Here's what changed.

First, what is Properties?

Properties is a Confluence Cloud app for adding and managing metadata on your pages. Instead of typing information into free-form tables, you define reusable property groups (sets of fields like team, user, date, status, or a link to another page) and attach them to pages and templates. From there you can filter, sort, and pull everything into a report that turns your scattered page data into something closer to a live database. Teams use it for things like project tracking, employee onboarding, asset registers, quality management, and documentation that has to stay structured.

Properties is a Cloud successor to the Data Center-only Blueprint Creator.

The biggest change: a cleaner page by default

The most visible difference in the new version is this: your property groups no longer sit on the page by default, but none of your data has gone anywhere.

Nothing is deleted, moved, or lost. Instead, your metadata now lives one click away, behind the byline item at the top of the page (the same area that shows who created and last updated the page). Select it, and all your properties open in a tidy modal. The result is a page that reads cleanly, with the structured data still right there the moment you need it.

This is the part I find genuinely interesting as a design decision, and it's worth a moment even if you use a different tool: where should metadata live on a page? Always visible means clutter. Always hidden means people forget it exists. Putting it behind the byline, a spot people already associate with information about this page, is our attempt at a middle path: clean by default, discoverable by habit.

And if you're in the camp that wants metadata visible on the page, you still can. The new Property Group Display macro lets you surface a property group's data directly on the page. It's read-only (to edit, you open the group from the byline button), so it's ideal for pages where the metadata is part of what readers should see. In other words: hidden by default, visible when you choose.

One thing to flag if you're already a Properties user: the behind-the-byline flow applies to property groups created in the new UI. Groups you built before the update won't move behind the byline automatically - you can bring them onto the page with the new Property Group Display macro whenever you're ready.

A redesigned Property Group Portal

The Property Group Portal, the place where you build and manage your property groups and their fields, has been fully redesigned. It's not only a more modern look; it also adds structure to the management side. You now get categories and a visual hierarchy, so if you're running dozens of property groups, you can organize them into sensible sections instead of scrolling a long flat list to find the one you need. 

A polished Property Group Report

The Property Group Report keeps everything it did before and gains a cleaner interface with more flexibility in how you display your data. At its core it does the same powerful thing: it collects property values from across your pages and presents them in one place (a single page or many) so your metadata becomes something you can actually read, sort, and act on, rather than data locked away on individual pages.

A quick note for existing users

If you already have Properties installed and don't see the new interface, the app most likely just needs to be updated from the Manage Apps section of the Confluence admin panel. A Confluence admin can do this in a moment.

Wrapping up

The look is cleaner, a few things have moved to smarter homes, but the foundation is the same: your structured data is still yours, still exactly where you put it, now with the option to keep it out of the way until you want it.

If this sounds like a problem your team has, you can find Properties on the Atlassian Marketplace and try it free. And I'd genuinely like to hear how other teams handle the clean-page-vs-structured-metadata question: Do you keep metadata visible, tuck it away, or something else? Let me know in the comments.