Skip to content

Track content freshness

Topicary flags stale content so you can prioritize updates before documentation drifts out of date.

Staleness indicators

On the Topics listing page, each topic shows a freshness indicator based on its last update:

Time since last update

Indicator

What it means

Under 30 days

None (content is fresh)

Recently reviewed or updated

30-89 days

Amber indicator

Content may be drifting — worth a review

90+ days

Red indicator

High risk of outdated content — prioritize review

The 30-day and 90-day staleness thresholds are system defaults and cannot be customized per project. They are calibrated to typical software documentation cadences where products ship updates monthly or quarterly. A topic flagged as stale is not necessarily wrong — it is a signal to verify, not an error.

Filter for stale content

  1. Go to Topics.

  2. Open the filter options.

  3. Select the Stale filter to show only topics that haven't been updated in 30+ days.

Review and refresh

Open each stale topic and assess whether the content is still accurate:

  • If it's still correct, make a small edit (even a whitespace change) and save to reset the staleness timer.

  • If it needs updates, revise the content and save.

Combine freshness filters with tag filters to create targeted review queues. For example, filter for stale topics tagged "Authentication" to review all authentication content before a security-related release. This is more efficient than reviewing every stale topic across the entire project.

Additional content health checks

Beyond staleness, the Topics page can filter for:

  • Empty — topics with no content

  • Orphaned — topics not included in any map

  • Broken references — topics referencing deleted components

  • Undefined variables — topics using variable tokens that don't exist in any set

Use these filters during regular content audits to maintain documentation quality.


See also

Was this page helpful?