Handover pack

Decisions we need from VLCT on topics

Each decision is its own page with the background, the options, our recommendation and what happens next. Forward any one of them on its own. Every page ends with the exact answer we need.

Prepared 17 September 2026 by Viv Web Solutions

Decision 1: Is the twelve-area tree the one hierarchy? needs VLCT

Decision 1 of 8 · Structure

Decision 3: Where do editors connect a page to its subject? needs VLCT

Decision 3 of 8 · Editing

Decision 4: Keep the existing page addresses, or tidy them? needs VLCT

Decision 4 of 8 · URLs

Decision 5: Cleaning up the topic tag names needs VLCT

Decision 5 of 8 · Wording

Decision 6: The "All topics" page needs VLCT

Decision 6 of 8 · Navigation

Decision 7: Hand-picked lists, everything, or both? needs VLCT

Decision 7 of 8 · Sidebars

Decision 8: What does a topic overview page look like? needs VLCT

Decision 8 of 8 · Design

Decision 9: Five small oddities in the tree needs VLCT

Follow-up · Structure (issue #82)

Decision 10: Federal Funding has three landing pages needs VLCT

Follow-up · Content (issue #89)

Decision 11: Seven small placement questions needs VLCT

Follow-up · Structure (issue #32)

Decision 2: Where does an overview page live? settled 11 September

Overview pages stay as pages, keep their addresses, and appear in the Resource Library as a pinned "Topic overview" card.

How to answer

Reply to Kalman by email with the decision number and the option letter, or comment on the GitHub issue linked at the bottom of each page. If we hear nothing before the next build, we apply the recommendation; every one is reversible, and each page says how.