Sangha usually means community, but in Buddhist history it has a more specific weight: the gathered community of practice, and in many contexts the monastic community that preserves and embodies the path. In a modern yoga studio, the word has to be used carefully. It should point to responsibility, not just warmth.
For this product, Sangha means that community is not decorative. It is an operating reality. People have relationships to one another and to the studio: student, teacher, facilitator, staff member, work-study participant, volunteer, founder, visitor, donor, neighbor. Those relationships shape access, communication, accountability, and care.
That is why the app is one responsive PWA rather than separate fragments for public pages, member actions, teacher workflows, and admin context. A community-centered studio needs public offerings, schedule, pricing, member access, social context, and studio identity to feel connected without collapsing every role into one generic user experience.
Sangha also requires honest exchange. Work-study should be visible as service, not hidden as a fake membership. Complimentary access should be granted through role or policy, not disguised as a sale. Dana should be recorded as contribution, not forced into a coupon model. Community becomes healthier when its exchanges are named clearly.
The aim is a practical one: help studios make belonging legible. Software cannot create community by itself, but it can reduce the confusion that weakens community. When roles, access, communication, and contribution are clearer, the studio has more capacity to be a real gathering place.
