Delivered outcome · production evidence

A fragmented wellness library turned into a connected subscription knowledge platform

Essential-oil guidance was spread across interconnected oils, ailments, body systems, properties, emotions, recipes, application methods, and safety considerations that were difficult to discover and maintain as ordinary pages.

Delivered outcomeCreated one connected discovery experience across oils, ailments, recipes, body systems, emotions, profile context, and safety information while giving the editorial team a structured CMS workflow.

What Zenveus built

The work behind the result.

A responsive Next.js knowledge platform backed by Strapi, GraphQL, and relational content modeling, with search, filters, body-map discovery, multilingual publishing, profiles, inventory and wishlist features, backend-controlled premium content, Stripe subscriptions, and containerized AWS deployment.

WORKSTREAM / 01

Relational knowledge architecture

Modeled oils, ailments, body systems, properties, emotions, recipes, application methods, and safety guidance as connected content in Strapi and GraphQL.

WORKSTREAM / 02

Guided discovery experience

Built responsive search, filters, body-map exploration, multilingual publishing, and contextual paths across a complex wellness library.

WORKSTREAM / 03

Subscription product operations

Added profiles, inventory and wishlist features, backend-controlled premium access, Stripe subscriptions, and containerized AWS deployment.

Implementation stackCapabilities used in delivery
Next.jsReactTypeScriptStrapiGraphQLApollo ClientMySQL/MariaDBStripe subscriptionsbackend access controli18nDockerAWS ECSAmazon ECRAWS CodeBuildAmazon S3Mailchimp Transactional

Engineering takeaway

A content-rich wellness product becomes useful when its relationships, discovery paths, access rules, and editorial operations are designed as a knowledge system rather than a collection of pages.

Bring us the constraint

Build the evidence your product needs next.

We can audit, harden, take over, or build the system — with a defined outcome and a production handoff.

Scroll to Top