Context
Hackathon PR #72 explored a /members page with a Leaflet map and localized page wrapper. The PR should be treated as prototype/reference work rather than merged directly.
Goal
Decide whether the site should have a members page, then rebuild or clean up the prototype into a privacy-safe, maintainable feature.
Prototype references
Known concerns from the hackathon audit
- Contains fake/sample member data.
- Adds Leaflet dependencies.
- Modifies generated
src/data/composite-feed.json.
- Fetches Meetup data during build for hosted-events stats.
- Has known navigation/localization bugs.
Acceptance criteria
- Replace or remove sample member data before merge.
- Define the source of truth for real member/profile data and any privacy rules.
- Keep generated files generated; do not hand-edit
src/data/composite-feed.json.
- Fix localized routes/navigation for English and Japanese pages.
- Avoid build-time external fetches unless intentionally accepted and documented.
- Add appropriate tests or documented manual verification for the page.
- Run full project checks before opening the final PR.
Notes
This should be handled as a fresh feature branch or a heavily cleaned PR, not a direct merge of the prototype.
Context
Hackathon PR #72 explored a
/memberspage with a Leaflet map and localized page wrapper. The PR should be treated as prototype/reference work rather than merged directly.Goal
Decide whether the site should have a members page, then rebuild or clean up the prototype into a privacy-safe, maintainable feature.
Prototype references
Known concerns from the hackathon audit
src/data/composite-feed.json.Acceptance criteria
src/data/composite-feed.json.Notes
This should be handled as a fresh feature branch or a heavily cleaned PR, not a direct merge of the prototype.