Faster browsing
Games has a smaller first load, while Seeing, Listening, and Activities now arrive 30 ideas at a time.
Loading…
The overhaul is complete. What remains is a smaller, more honest map: choices that need product direction, engineering follow-ups with a known path, and ideas worth saving until real usage calls for them.
Release foundation complete
Games has a smaller first load, while Seeing, Listening, and Activities now arrive 30 ideas at a time.
Every Together section has its own title and description, and bucket lists can show a useful preview image.
Detail windows, icons, controls, cards, colors, and admin tools now follow the same visual foundation.
Needs Scott's direction
These should wait for a clear product opinion because each choice changes what people experience, not just how the code works.
Why it remains
A name or identity change would touch navigation, sharing, search appearance, writing, and future marketing.
Best next move
Keep Adventures Together as-is unless a stronger name and positioning are worth a coordinated change.
Why it remains
A dark theme is a full visual system decision, especially for warm editorial surfaces, imagery, maps, and accessibility.
Best next move
Compare a true evening theme with a softer low-light theme before choosing whether to build either one.
Why it remains
Several home concepts exist, but the next version should be judged using real lists and real activity rather than placeholder layouts.
Best next move
Review the strongest real-data home variants and choose one leading direction before redesign work begins.
Why it remains
The clearly dead placeholder addresses are now permanent redirects, but a few working pages — the map, the projects workspace, and the Explore list index — still have no link pointing at them from anywhere on the site.
Best next move
Decide, page by page, whether each one earns a place in navigation or should be retired.
Ready for a future work pass
These have a sound technical direction. They remain because this release protected exact behavior and deployment safety instead of forcing a larger rewrite.
Why it remains
The unused older reads are gone and the rest now stop at a fixed size, but exact search, uncommon sorting, partner filters, and bucket-list views still rely on those compatibility paths.
Best next move
Move those exact behaviors into paginated server queries, prove parity, then remove the older reads.
Why it remains
Explore distance filtering needs a deliberate location-query design to stay fast as the place catalog grows.
Best next move
Write and review the geographic-index design before changing the Explore filter architecture.
Why it remains
Automated and guest checks are strong, but some admin screens and signed-in variations still rely on focused static coverage.
Best next move
Add repeatable signed-in browser scenarios for the highest-value admin and partnership paths.
Why it remains
The production board covers the main journeys, while a few useful route-specific checks still live outside that suite.
Best next move
Add Seeing pagination and release-page checks to the normal live smoke board when that test surface is next touched.
Intentionally not scheduled
These may be worthwhile, but they should follow real usage or a clearer product need rather than becoming cleanup for its own sake.
Why it remains
The foundation is now consistent, but converting every older component would create a wide change without equal user value.
Best next move
Move older controls onto shared primitives when their pages receive meaningful product work.
Why it remains
Section metadata is now server-rendered, while each interactive catalog still owns its live client experience.
Best next move
Use measured route performance to choose which section, if any, deserves server preloading next.