How this roadmap works

This page is generated automatically from a GitHub Project board — it is not hand-edited. The board is the single source of truth; this site is just an attractive, public snapshot of it.

The flow

1. The team plans work on a GitHub Project board (issues from viv-chatbot, viv-typesense, and mma).
2. A small generator called Viv Product Roadmaps reads the board through the GitHub API.
3. It maps each item's fields and labels to a column, tags, and badges (see below).
4. It renders this static page and publishes it to GitHub Pages.

Because it is config-driven, the same engine can publish a roadmap for any product — each one just needs its own config file.

How items are placed

• Now / Next / Later columns come from the board's Horizon field. If an item has no Horizon set, the engine falls back to the issue's track label: Track 1: Demo Spine → Now, Track 2: Production → Next, Post Launch → Later.
• The Product tag (and its colour) comes from the Product field, falling back to the item's repository.
• The Theme tag comes from the Theme field — e.g. Indexing & Search, Citations, Guardrails.
• The coloured bar on the left edge reflects the issue's priority label (Top / High / Medium).
• The status pill reflects the board's Status (or whether the issue is open/closed).
• The Shipped column collects everything that's done. An item lands there in any of three ways: its Status is set to Done, its Horizon is set to Shipped, or the GitHub issue is closed.

Want to change what's shown?

Edit the GitHub Project board — move an item's Horizon, change its Product or Theme, open or close the issue. The next build (on a schedule, or triggered manually) regenerates this page. You never edit the HTML by hand.

Source

The generator is open within Viv: viv-product-roadmaps. This page links back to the underlying GitHub Project at the top — note that the Project itself is team-access only.