■FIG. A.6 · Club project · community product · Mar 2026
Hindi Sahitya Sabha Website
A campus literary society’s website is a small product with real users, real editors, and no budget — which makes it a perfect test of product discipline. This one was discovered before it was designed, designed before it was built, and shipped with the same security posture a larger site would need. Launched at hindisahityasabha.in in March 2026.
THE PRODUCT TIMELINE
01
DISCOVERY
Ask the community first
A 50-plus-response community survey covering design ratings, feature wishlists and content habits set the agenda — the roadmap was a ranked list of asks, not a preference.
02
DESIGN
Roadmap in Figma, then code
The ranked roadmap was designed in Figma before implementation. What shipped is what members asked for: the Saarthi hub (submissions, resources, games), the Smritikosh archive, and genre feeds.
03
SYSTEMS
Git-as-CMS publishing
Editors publish by committing content through an admin UI backed by Git. A prebuild pipeline compiles Markdown into sanitized JSON bundles, with sharp generating the image variants — no database to maintain, every change reviewable.
04
HARDENING
Defense in depth, quietly
Layered XSS defense: HTML sanitized at build time, rendered tokenized server-side, Content-Security-Policy enforced via edge headers. A contract test pins client and build-time loaders together so hydrated UI can never drift from prerendered HTML; vitest suites run throughout.
WHAT THIS SHOWS
The site is the proof that product instinct and engineering rigor aren’t separate roles: the survey decided what to build, the contract test and CSP decide whether it may ship. It also runs the same way the society works — content flows in as commits, reviewed like any other contribution.
Prev: FIG. A.5 · Language-Based Audio RetrievalCross over to Door B · Markets & Risk →