The 70-node tree works, but five spots do not follow their own rules. Each is a one-node edit in the admin screen, fully reversible, and none blocks anything else. We would rather fix them once, with VLCT's nod, than debate them later.
| Oddity | Where | Recommendation |
|---|---|---|
| Two nodes gather no tags at all, so they show a count of 0 | "Executive session" under Open Meeting Law; "Elections & Voting" under Elections & Town Meeting | Delete them. Re-create if VLCT starts tagging content that way. |
| One top-level area is also a tag | "Public Safety & Emergency" carries the Public Safety tag (162 items) directly; every other area is a pure grouping | Move the tag to a child node "Public Safety (general)" so the area behaves like the others. |
| "Infrastructure" appears twice | "Public Works & Highways › Infrastructure" and the area "Housing & Infrastructure" | Rename the Public Works child to "Infrastructure & Utilities". The Housing area's word refers to the CHIP programme, which is a different thing. |
| One area has a single child with the same page | "Technology & Cybersecurity › Technology & Info Security" | Collapse to one node. No client input needed unless you object. |
| A child points at its own area's page | "Insurance & Risk (PACIF) › Risk Management" → the Risk Management Services page, same as the area | Ask RMS: fold into "Coverage & Insurance", or keep as the department's catch-all. |
If we hear nothing before the next build, we go with the recommendation: the four recommendations are applied and Risk Management is left as is. Reply to Kalman by email, or comment on the linked issue.
Related: #82. Undo: every edit is a node that can be renamed, moved back or restored from Trash; the pre-change tree is saved in the repository.
← 8 · Overview page design · All decisions · 10 · Federal Funding →