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 27 September 2026 by Viv Web Solutions

Decision 1: Is the twelve-area tree the one hierarchy? settled 23 Sep

Yes: the draft site's twelve-area tree is the hierarchy, for now.

Decision 3: Where do editors connect a page to its subject? settled 23 Sep

Option A: the link lives on the tree node ("this subject's page is …").

Decision 4: Keep the existing page addresses, or tidy them? settled 23 Sep

Keep the existing page addresses for now.

Decision 5: Cleaning up the topic tag names direction given, wording still needed

Do not rename any term yet.

Decision 6: The "All topics" page provisional, review pending

Option A: rebuild the page from the tree, on the existing work branch, with the current grid kept so it can be put back in one step.

Decision 7: Hand-picked lists, everything, or both? settled 23 Sep

Option A: a curated list per group with an "All N resources tagged …" link at the bottom.

Decision 8: What does a topic overview page look like? settled 23 Sep

Option A: the draft site's hub page is the design for a topic overview page.

Decision 9: Five small oddities in the tree settled 23 Sep

Yes to four of five: delete the two empty nodes; move the Public Safety tag to a child node; rename the Public Works child to "Infrastructure & Utilities"; collapse Technology to one node.

Decision 10: Federal Funding has three landing pages settled 23 Sep

Option A: the Municipal Operations Support page is the landing page for Federal & ARPA funding; the placeholder redirects to it; the ARPA page becomes a listed child and keeps its address.

Decision 11: Seven small placement questions approved 23 Sep, one follow-up

All seven approved for now.

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.