Case study
Aestiva Dental
Staff updates, patient video, and a CMS the clinic could finally run without calling a developer.
Visit the project ↗
- Client
- Dragana
- Services
- CMS · Website development
01 / Challenge
Aestiva Dental needed outdated staff photos gone and new team members up. In theory the CMS should have handled it. In practice the code would not let the clinic touch what they needed to touch.
Aestiva Dental starting frame
The first screen that had to carry the business case.
02 / Insight
The work starts by deciding what the visitor needs to understand first. For Aestiva Dental, that meant translating the brief into a system people could scan, trust, and act on.
Clinic identityCurrent teamPatient videoProcess reconstruction
Staff is the product
Patients judge a clinic by the faces on the site. Outdated portraits were the actual brief, not a new homepage.
- Team
- Bios
- Video
03 / System
We opened the site so staff could update it, swapped employee profiles, added a patient-video plugin, and wrote a short CMS manual for the people who would actually use it.
Dragana
Hygienist
New hire
Process reconstruction
Clinic CMS
Profiles, media, and a short manual so the front desk could publish without calling a developer.
- Staff profiles
- CMS access
- Patient video
04 / Execution
We opened the site so staff could update it, swapped employee profiles, added a patient-video plugin, and wrote a short CMS manual for the people who would actually use it.
Aestiva Dental live experience
The shipped interface, used as the execution artifact.
05 / Outcome
The site matches the current team. Videos help patients see the practice. Staff can publish changes themselves — which was the point of a CMS in the first place.
Aestiva Dental after launch
The finished system, held together as one experience.