Patients need simple answers and a clear route to booking; referring doctors need methodologies, technical materials, and a fast contact path to expert support.

A substantial body of clinical and operational information that had to be preserved but presented more cleanly and with sharper structure.

The new site had to be fast, modern, and content-evolvable, or the same problem would resurface within one or two years.

The operations team needed to publish articles, edit reference materials, and adjust services, prices, and locations without a developer in the loop.

In healthcare, ambiguity reads as risk. The pages had to close the user's open questions before the user left to look at a competing center.

We made the Doctors / Patients switch the central interaction point — switching it changes the navigation structure, content priorities, and the very wording of headings. The doctor-facing mode exposes short entry points into methodologies, technical materials, and support. The patient-facing mode leads with simple explanations, a step-by-step path to choosing an examination, and booking.

We built a shared component layer for both surfaces — typography, grid, cards, reference blocks — so both modes read as equally native parts of the same brand. A separate workstream targeted the small interface elements that build trust and a sense of control at every step (clear pricing, transparent prep instructions, named author bylines on doctor materials).

We modeled content types and their relationships in Directus so the same factual material could surface differently for the two audiences. For patients: explanatory blocks, indications and contraindications, preparation instructions, route guidance to the nearest center. For doctors: methodologies, clinical standards, technical materials, and a single entry point into consultation or expert support. The editorial process runs end-to-end without engineering support.

We designed the frontend as a set of stable templates covering the key pages in both modes, so content updates would not break layouts or demand manual fixes. Speed optimization was treated as part of the UX — fast transitions build trust and make the site feel current rather than legacy.

We separated the language and presentation for each audience while preserving brand coherence — one visual style, one set of layout principles, one consistent way of explaining complex topics. This avoids the failure mode where one mode looks like the main site and the other like an afterthought.

to publish or update a page or article — down from 2–3 days in the old WordPress-era workflow

of site content is now fully manageable by the client's team without engineering involvement — up from a previous baseline where almost every change required a developer ticket

improvement in key-page speed (Hero, Service, Location pages), measured on Lighthouse + real-user GA4 page-load timing

the Doctors / Patients switch removed the previous mixed-content confusion that was costing both groups time on every visit

block-based architecture, clean typography, and generous whitespace make complex medical content scannable without sacrificing depth

is now communicated clearly through the site — corporate values, clinical credentials, and equipment advantages have a dedicated surface rather than competing with patient flows