ChapterStack Updates: Claim an Issue

Quick sync: ChapterStack updates after WIAL meeting

We recently met with WIAL and identified several improvements for chapterstack.org. If you have some free cycles and want to contribute, there are issues filed in the project repository—please jump into this Slack channel to ask clarifying questions and assign yourself to an issue so the team knows you're working on it.

How to jump in (router handshake)

• Visit the live site at http://chapterstack.org|chapterstack.org to see current behavior and gather ideas.
• Review the open issues on the repo: https://github.com/2026-ASU-WiCS-Opportunity-Hack/03-nanpossible|github.com/2026-ASU-WiCS-Opportunity-Hack/03-nanpossible.
• Comment on an issue if you need clarification, then assign the issue to yourself to claim it.
• If you're unsure how to start, post in this channel — someone will pair-program or review your PR.

Best practices (merge-ready mindset)

• Fork and create a feature branch with a clear name (e.g., fix/header-accessibility).
• Run the app locally and include screenshots or repro steps in your PR description.
• Keep commits small and focused; write descriptive commit messages so reviewers can follow the logic (no cryptic 404s or 'tweak' commits).

Why your help matters

Your contributions help the chapter network run smoother and make the site friendlier for organizers and volunteers. Whether you're squashing bugs, polishing UI, or improving accessibility, every pull request is rhythm and rhyme—like a well-timed bridge in a song. Assign an issue, drop a question in the channel, and let's ship these updates together.