Skip to content

Prioritize what to write next

The Demand page answers a single question: what should I work on next? It aggregates every governance signal Topicary already collects into one prioritized worklist, so you never have to check five different places to decide what to do.

Demand sits right under Dashboard in the sidebar and is available on every plan, including Free.

Open the Demand page

Go to Demand in the sidebar.

Use Refresh worklist to re-run gap detection and the lifecycle scan so the list reflects the latest activity. The header shows when the signals were last scanned.

Where demand comes from

Each item carries a muted source tag showing which signal produced it:

  • Reader gap: a question readers searched for but your docs could not answer. From Triage content gaps.

  • Health scan: a per-topic recommendation from the nightly Automated lifecycle recommendations.

  • Code change: a merged pull request in a watched repository that may have made a topic inaccurate. From code watch.

  • Docs test: a failing docs-as-tests check ingested from your CI (Doc Detective).

  • Quality check: a passive finding, such as a duplicate or a missing cross-reference.

The worklist

Every item carries a colored action label so you can see at a glance what it asks for:

  • Create: write a new topic. These are reader gaps.

  • Update, Expand, Verify, Merge, Split, Archive: improve an existing topic.

Each item is ranked by a priority score (0 to 100) shown on the left. Higher means more urgent: the score blends how confident the signal is, how much evidence backs it, and, for existing topics, the topic's content debt. When you sort by priority, the list is grouped into urgency bands (Do now, Up next, Later) without reordering.

Above the list:

  • Filter chips switch between All, To create, and To improve.

  • A search box filters by title or reason.

  • A sort control switches between Priority and Newest.

The line under each title explains why the item is here, for example how many readers searched for a missing answer, or what the lifecycle scan detected.

Act on an item

The primary action depends on the source:

  • For a Reader gap, choose Create draft to start a new topic seeded from the gap and open it in the editor.

  • For a Code change, choose Draft update to stage the suggested edits and open the topic, or Open to check for a verify item.

  • For a Docs test or a lifecycle recommendation, choose the action that opens the topic so you can fix it.

  • Use the check mark to mark a recommendation done, and the X to dismiss any item you do not intend to act on.

Items disappear from the list as you act on them. Opening a topic from Demand carries the context with you: the editor opens with a banner and the relevant panel (findings or suggestions) already open.

See also

Was this page helpful?