Quality for Confluence

Capable Quality checks Confluence pages and blog posts against 13 content-quality rules covering page structure, accessibility, language and organisational compliance, and reports what it finds in four places: a "Quality" item on the page byline, a Quality column, filter and side panel in Capable Search, a per-rule list for every enabled rule in the Capable Quality navigation, and a Dashboard of charts and trends.

Eight of the rules are worked out when Capable indexes a page and stored as tags on that page, so they can be counted and searched.

The other five (disallowed domain links, disallowed macros, third-party macros, stale content, disallowed labels) are worked out live from lists a Confluence administrator supplies, and are never stored. Rules are configured once for the whole site on the Rules page; each rule has a single Priority / Warning / Info / Off control that both turns the

The Quality summary showing 1,021 total issues made up of 30 priority, 93 warning and 898 info, above a card for each rule with its count, including Disallowed macros 25, Image alt text 83, Empty page — The summary counts every finding across the site and breaks it down by rule under Priority, Warning and Info.

#Start here

Get started

What people actually do.

How it works

The behaviour worth understanding.

#Everything else

OverviewWhat it is, how the two products differ, and what it costs you.Get startedThe 18 things people actually do with Quality, and the route to each.How it worksHow Quality behaves: 11 behaviours worth understanding before you rely on them.AdministrationEvery setting, where it lives, and who is allowed to change it.IntegrationsHow Quality connects to the rest of Capable, and where it deliberately does not.ReferenceLimits, and the things that look like settings but are not available.Troubleshooting27 symptoms, grouped by where they bite.

Written against the app as it behaves today.