Iterant is in early access. These docs describe the product as it works today.
Iterant Docs

Themes

How Iterant groups related page opportunities into themes, and how to work a whole theme at once.

A theme is a named cluster of related page opportunities: "observability for Kubernetes", "migration guides", "pricing comparisons". Themes let you read a scattered queue as one body of work and schedule it as a unit.

The discovery agent coins themes as it works. They are read-only in the dashboard: you cannot add, rename, or delete one. When a later run coins a name close to an existing theme, Iterant matches it back to that theme rather than creating a near-duplicate, so a theme grows across runs instead of fragmenting.

Opening a theme

There is no themes index. You reach a theme from an opportunity: open its detail drawer and click the Theme: link under the title. Every opportunity belongs to at most one theme, and some belong to none.

What the theme page shows

The header carries the theme's icon, its name, a progress reading, and its description:

  • 4/17 shipped: how many of this theme's opportunities have produced a published page, out of the active total. Shipped counts the page rather than the opportunity, so it moves only once the page is live.
  • ETA pending: a delivery estimate needs your publishing capacity configured. Until you set that, the estimate stays pending instead of guessing.

Below that, four filter chips with counts:

ChipWhat it counts
AllEvery active opportunity in the theme: ready, scheduled, in review, or approved.
ReadyWorked up and schedulable, with no date yet.
In progressScheduled, in review, or approved.
ShippedHas a published page.

Dismissed and superseded opportunities are not counted here. A theme's numbers describe live work only.

Working a theme in bulk

Use a theme page rather than picking opportunities off Home one at a time.

  1. Filter to Ready.
  2. Select rows one by one, or use Select all Ready, which takes the ready opportunities currently loaded, capped at 100. When the theme holds more than that, the button's tooltip tells you how many it will take.
  3. Use the action bar at the bottom:
    • Schedule opens the scheduling proposal: dates grouped by week, each with the reason it landed there. Accept them, or send them to your calendar as proposals to fine-tune. Pillars are ordered ahead of the spokes that depend on them.
    • Dismiss dismisses the whole selection with one reason. Up to 100 at a time; the result tells you what was dismissed and what could not be, so a stale selection never drops rows without telling you.
    • Clear drops the selection.

A failed bulk dismiss keeps your selection intact so you can retry without re-picking checkboxes.

Pillars and spokes

Opportunities carry a role that matters inside a theme:

  • Pillar: the anchor page for the theme. Other pages point at it.
  • Spoke: a supporting page that depends on its pillar existing first.
  • Standalone: no dependency either way.

Scheduling respects this: a spoke is never planned before the pillar it depends on. Dismissing a pillar that still has dependent spokes prompts you first, and lets you choose between dropping the pillar alone or cascading to its spokes.

Themes on the coverage map

The coverage map is organised by buyer stage, so themes are not an axis on it. Theme names appear there as the topic labels on the demand band, so an opening reading "migration guides" names the theme the gap belongs to. Follow it back to the theme page to get from an open topic to the queue of pages that would close it.

Troubleshooting

Last updated on

On this page