Release notes
What changed on Lamppost, newest first.
August 24, 2026 — the Atlas
The new site
- A complete redesign across every page — homepage, explore, record pages, civic pages, and account screens. Old links all land where they should.
- Navigation rebuilt around your questions: Near me, The city, Coming up — with My streets one click away when signed in.
Explore
- A split view: the record list always visible beside a map that fills your screen. The default window is now 7 days.
- Three tabs — Records, Insights, Nearby — with live counts. Nearby shows records just beyond your configured radius, and says exactly how far that is.
- The map and list talk to each other: pick a pin and the list finds the record; pick a record and the pin lights up. Every record links to its full detail page.
- Signed in, the map opens on your watched areas, with everything outside them gently dimmed.
- A My streets drawer: manage watched locations without leaving the map.
Your streets
- The dashboard moved to My streets, and everything came along: who represents you, public meetings near your areas, cases you follow.
- Editing watched areas is back — a radius slider with sensible stops (200 m to 8 km, shown in meters and miles), polygon redraw, address change, add and delete.
- Neighborhood analytics for your watched areas — all of them together, or one at a time.
- The amenity completeness score now explains how it is counted, and lists which kinds of everyday places are — and are not — within a 20-minute walk.
The city & Coming up
- The city is a stats dashboard: counts, per-day rates, week-over-week changes, busiest ZIP codes, with a 7/30/90-day selector.
- Coming up carries a three-month calendar — days with meetings are highlighted and clickable — above the full agenda, absorbing the old Meetings, Council, Committees and People pages.
Insights on the map
- Corridor detections draw as bands along the actual street; “first of its kind within a 20-minute walk” callouts mark amenity gaps.
Fixes
- A launch-day map that refused to render, a refetch loop that asked the server the same question once a second, an insight-card label overlap, footers floating mid-screen, and a dozen accessibility defects caught by new automated checks.