WK·003
Rhya
A live wellness site for a real business, built close enough to the stakeholder that vague feedback was never going to survive long.
102 commits · 11 active weeks
latest b613c3c · 12 Jun 2026
Overview
Rhya is a live site for my girlfriend's wellness business. It sits here because it is a useful counterweight to the agent and infrastructure work: a real service, real customers, and a product experience that has to earn trust before anyone books anything.
The work was not about showing off technical complexity. It was about clarity, structure, brand, conversion, and the operational details that make a small business feel coherent online.
The live site, captured
The actual site is one click away. While you are there, a Pilates event may make a stronger case than this caption.
Context
Most of the other projects began with a technical annoyance. Rhya began with a person and a business that needed the web presence to feel as considered as the service itself.
That changes the design pressure. You are not optimising for a clever demo. You are trying to help someone understand what is offered, decide whether it is for them, and take the next step without friction. The site started as Moon and Mornings and became Rhya as the brand sharpened.
What changed
A service site can be beautiful and still fail if the next action is unclear. Rhya had to explain the offer, support booking or registration, and still feel warm rather than transactional. That is a harder balance than it looks in a screenshot.
The temptation in brand work is to decorate until it feels premium. The better move is usually quieter: make the decision easier, make the language clearer, and let the design support that instead of competing with it.
The build
The archive shows Rhya through frozen frames from dated commits. You can see the product decisions arrive in order: service language becoming clearer, the coaching and Pilates paths becoming more concrete, the rename to Rhya, and the move from generic imagery toward real photographs of the coach and studio.
It is still active, and I will keep improving it. Partly because it matters. Partly because the stakeholder feedback loop is unusually close to home.
Notes from the archive
What held up is the operational test. Can someone understand the service, trust it, and know what to do next? If the answer is no, the page is not done, no matter how nice it looks.
This is the one I expect to keep changing. A live business does not freeze itself neatly for an archive. It keeps moving, which is inconvenient for a static showcase and much better for the actual business.
Evidence
| repo | github.com/Bhatte/Rhya | repo-reviewed |
| external-link | therhya.com | deployed |
| commit | Latest reviewed main-branch commit · 1366f9b | 2026-05-20 |
| screenshot | Journey captures from dated commits, 18 Feb to 15 May 2026 | source repo |
Technical detail
Other exhibits
| WK·001 | Alph | An open source CLI for MCP setup, built because editing the same JSON in five different places is a poor use of anyone's evening. | Terminal |
| WK·002 | AskHuman | A hosted MCP loop for agents that need a human decision instead of another confident guess. | Decision loop |
| WK·004 | Gradience | An assisted grading workflow that was probably right about the direction, but early for the market and the models. | Timeline |
| WK·005 | WatstheStory | A personalised audio briefing system for WhatsApp, built because a short spoken update sounded better than opening ten feeds before breakfast. | Live |