Institut Ophelia

Context

Institut Ophelia serves dentists seeking continuing clinical education in Morocco. Its offer includes structured cycles, masterclasses, bootcamps, webinars, and editorial resources. Each format asks for different details before a visitor can decide whether it fits.

Problem

A programme catalogue alone does not explain what a course covers, where it takes place, or how to act on it. The site has to separate programme discovery from editorial content while keeping registration and contact routes close to the relevant course.

Existing architecture

The website and the institute's operational system are distinct codebases. The public frontend reads programme and editorial data from backend services; the operational repository documents the institute's internal workflows.

Solution architecture

The frontend groups training by format and gives individual programmes their own pages with practical details. Editorial routes, including Ophelia Radar, sit alongside the training catalogue rather than being mixed into it.

Programme and contact forms use backend endpoints. This lets the public site present the offer while the institute's systems handle the records behind it.

Implementation

The public site is built with Next.js. Its pages cover training listings, individual programmes, events, a professional community, articles, and contact. The repository also contains route redirects and structured metadata for programme pages.

A separate Ophelia OS codebase is documented for institute operations. The case does not treat that system as proof of a completed integration with every public website route.

Validation

The live site and source repositories confirm the available page families and programme journeys. No enrolment uplift, conversion rate, or training outcome has been supplied for publication.

Technical stack

Next.js
Ophelia OS