Studio deliveryHealth and wellness platform · 2025 · Senior full-stack engineerdrjeromepuryear.com
Puryear
Headless-CMS health platform on Storyblok, with a scoped AI assistant answering from the client’s own published material.
Puryear is a studio-delivered headless-CMS health and wellness platform on Storyblok, with a scoped AI assistant that answers only from the client's own published content and hands anything else to a human. Delivered inside a previous studio, not a client contract with The SyncFlow.
- Studio
- Attribution
- Full build
- Scope
- Live
- Status
Delivered inside a previous studio. Contract terms belonged to that studio, so none are published here.
The problem
The client published constantly and could not touch the site without a developer. Every content change became a ticket, which meant content stopped changing.
At the same time, the same handful of wellness questions arrived over and over, each one consuming time that should have gone to patients.
Constraints
The conditions the solution had to survive, not a wish list.
- Non-technical publisher
- Content editing had to be genuinely self-service, not a CMS that still needed a developer.
- Accessibility
- A health audience makes WCAG conformance a requirement rather than a nice-to-have.
- Answer quality
- Health-adjacent guidance has to be bounded and traceable to the client’s own published material.
The approach
In plain English, before the architecture.
Content moved to Storyblok so the client publishes directly, with components designed around how they actually write rather than around the database.
The assistant answers from the client’s own published content, which keeps responses on-message and gives every answer a source, and routes anything outside that scope to a human.
Architecture
The decisions that mattered, and why they were made that way.
- 01
Storyblok headless CMS
Editable components mapped to real page patterns, so the client publishes new content with no developer involvement.
- 02
Scoped AI assistant
Guidance answered from the client’s published material, with out-of-scope questions handed to a human rather than guessed at.
- 03
Progress tracking
Chart-based tracking of user progress over time, built on the same data model that drives the dashboard.
- 04
Accessibility and motion
WCAG standards applied across the interface, with GSAP motion used sparingly and gated behind reduced-motion preferences.
Outcome
The client publishes directly through Storyblok now, with no developer involved in ordinary content changes.
The AI assistant answers only from the client’s own published material and hands anything outside that scope to a human, keeping guidance traceable rather than guessed at.
Stack
- React
- Next.js
- Node.js
- Express
- MongoDB
- Storyblok
- GSAP
Tell us what you can’t staff.
Twenty minutes. No deck, no discovery sequence. If we are the wrong fit we will say so on the call and point you somewhere better.