Working with other capabilities

Most of what makes Quality worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.

Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.


#Every connection

Connects to

What you get

Capable content indexing

Everything except the byline lozenge depends on it. Quality tags are written to the page's shared Capable index property, and every tag-based count, badge, list and chart requires the page to have been indexed. Not-yet-indexed pages are invisible to Quality.

Capable Search

Provides the Quality column, the Quality and Domains filters, the Quality side panel and the search views behind every per-rule list. In the standalone app the search side panel is the only way to review and fix issues on a specific page.

Capable Links

Populates the indexed list of outbound link domains. Without it the "Disallowed domain links" rule and the search "Domains" filter always return zero, with no error.

Capable Metrics

Provides page word counts. The weekly sweep probes once per run whether word counts are available and silently omits the word-count buckets if not. (Those buckets are collected but not shown anywhere. See notShipped.).

Capable migration catalogue

Supplies the macro keys behind the "Third-party macros" rule. In the standalone Capable Quality app the migration tooling itself is not available, so the rule can find migration opportunities that cannot be acted on there.

Confluence CQL index

Every count, badge and chart is a Confluence search. There is a lag between a page edit and the numbers changing, on top of Capable's own indexing lag.

Forge scheduled triggers and queue

The weekly aggregation is queued onto the app's single shared background queue (900-second consumer), the same one that handles content indexing. Aggregation and indexing compete for it.


#The pages


#A few things worth knowing

  • A connection needs both halves installed. In a standalone app most of these do not exist.

  • Anything that depends on search only reflects pages that have been indexed.

  • Published sites render Capable macros properly, which is where several of these pay off.



Better with company.