Dr Hassan El-Hefnawy — Cardiology
The same clinic platform, rebuilt around a different doctor with a different identity — proving the product adapts rather than repeats.
- Platform
- Web
- Year
- 2026
- Role
- Full-stack developer
The challenge
One clinic site is a project. Two is a question: is the second one a copy with the colours swapped, or does the thing underneath actually generalise? A template would have forced this doctor into the first clinic's layout and typography.
The approach
The engine is shared — booking, dashboard, permissions, RTL, dark mode, SEO — while the identity is not. This one runs its own eight-section layout on IBM Plex Sans Arabic with a teal and sand palette, independent of the other clinic in look and in content.
The result
A second clinic went live without inheriting the first one's design decisions, which is the only real test of whether a platform is a platform.
Highlights
- Cardiology services in detail — Consultation, echocardiography, stress ECG, 24-hour Holter, routine follow-up and pre-operative assessment.
- Managing the bookings — Tracking, filtering, status changes and internal notes, plus adding a booking by hand for whoever called in.
- A patient record that builds itself — Assembled automatically from bookings with the phone number as the identifier — no double entry, no file created by hand.
- A wholly independent identity — IBM Plex Sans Arabic, a teal-and-sand palette and its own eight-section homepage — sharing neither look nor content with the other clinic.
- Light and dark — The site follows the visitor’s preference, and both modes are designed rather than derived by inverting colours.
- Separate database, separate deploy — Its own codebase, its own database and its own deployment — neither clinic can take the other down.
Built with
- Next.js
- TypeScript
- Prisma
- PostgreSQL
Next project
The Copywriter Camp