Hack4Impact BU
Infrastructure Team
Every content change needed a developer. Rebuilt the chapter site so the e-board could run it themselves, then shipped the rebuild as a template other chapters can reuse.
- Content moved to CMS
- 85%
- Application engagement
- +100 clicks
- Reusable by
- Other chapters
- Live
- bu.hack4impact.org
Problem
Hack4Impact BU's site was developer-dependent by construction. The e-board could not update content, student applicants found applying difficult, and clients had no coherent path through the site. Every copy change, every new event, and every application cycle went through an engineer.
There was no scalable CMS workflow and no role-based access, so the bottleneck was structural rather than a matter of effort.
Approach
Rebuild the frontend in React with responsive design and reworked navigation, and move the content out from under the developers entirely, into a Strapi CMS with an admin panel and role-based access control mapped to the actual e-board roles.
Outcome
85% of site content moved into Strapi, cutting developer maintenance to the cases that genuinely need code.
Application engagement rose by over 100 clicks after the navigation and responsive rework.
New features shipped alongside the rebuild: an event gallery, Coffee Chat scheduling, application management, and CMS-editable sections throughout.
Handoff
The work was delivered with full documentation, SEO optimisation, and a handoff template built so other university Hack4Impact chapters can adopt the same setup rather than solving the problem again.
That template is the part worth pointing at. The site was the deliverable, but the reusable pattern is the contribution.
Built with
- React
- · Strapi CMS
- · RBAC
- · SEO