Opening an issue
- Use a clear, specific title (“Broken link on the Membership page” beats “website problem”).
- Include the page address, what you expected, and what you saw instead. Screenshots help a lot.
- For content corrections (dates, names, rules), include a source we can verify.
Submitting a pull request
- Keep each pull request focused on one change — small PRs get reviewed faster.
- Describe what you changed and why in the PR description.
- Match the existing style of the code and content around your change.
- Test locally first:
npm install && npm run dev, then check your change in the browser. - Never include passwords, API keys, or personal information in a contribution.
- Safety-related content (fire rules, water conditions, by-laws) must cite an official source.
How review works
A volunteer site manager reviews every suggestion, issue, and pull request — and we’re grateful for all of them. Please know that we may not accept a proposed change exactly as submitted: the board is responsible for what the association publishes, so we may ask you to revise it, or adapt your idea into a future update ourselves. Either way, your input shapes the site.
By contributing, you agree your contribution is licensed under the project’s MIT License, with no expectation of payment.