AWENE — Bilingual Coaching Platform & Content Infrastructure
AWENE is a perimenopause and menopause coaching platform founded by Dr. Amira Medimagh, a physician and certified integrative health coach with over 20 years of experience in international public health. The platform accompanies women through hormonal transitions across Tunisia, Morocco, Algeria, the broader MENA region, and the French-speaking diaspora in Europe — combining scientific rigour with structured, human-centred support. Before OJC Labs, AWENE had no dedicated digital infrastructure: no CMS, no event or formation registration system, no automated contact or email flows.
Systems built.
What we built.
Headless Next.js platform — bilingual FR/EN
Built the full public site on Next.js with strict bilingual routing under /fr and /en. Every page, article, event, and formation has its own locale-specific route. Each language version owns its content independently — no shared re-exports between locales, no content bleeding across language boundaries. Multilingual SEO, per-locale canonical tags, and hreflang are handled at the framework level.
Headless WordPress CMS with custom plugin
Deployed a headless WordPress CMS as the content backend — the public site fetches content via REST API and renders it on Next.js. Extended WordPress with a custom plugin providing dedicated endpoints for events, formations, registrations, event recaps (PV), and satisfaction forms. All CMS data is normalized through a typed adapter layer before reaching the frontend — the site never exposes raw CMS internals to the public layer.
Event and formation lifecycle system
Built a full event lifecycle system: upcoming events display registration CTAs and available capacity; past events surface recap content and satisfaction form results. Formations follow the same pattern — a formation sales page and a formation recap page are distinct content models with distinct purposes, not the same page in two states. All registration submissions route through controlled API proxy endpoints rather than posting directly to the CMS, centralizing validation and keeping the public URL stable.
API proxy layer and Brevo email automation
Every form submission on the site — contact, newsletter, event registration, formation registration, satisfaction — routes through a Next.js API layer before reaching the CMS. This isolates the public frontend from CMS internals, centralizes validation, and injects Brevo email automation where needed: registration confirmations, bilingual welcome emails, and event notifications are all triggered automatically without manual intervention.
Technical SEO and performance infrastructure
Implemented full technical SEO infrastructure: per-locale canonical tags, hreflang (FR/EN), Open Graph and Twitter card metadata on every page type (articles, events, formations, recaps), structured data, and automated sitemap generation. Images are served via next/image from the configured CMS hostname. The CMS environment resolves from environment variables — no hardcoded domains, no silent fallbacks. Read more in our post on headless CMS architecture and SEO.
Technology stack.
Stack used.
Related reading.