Eagle Eye Centre

The Challenge

A specialist medical practice publishes a lot of interlinked content: treatments, conditions, screening packages, individual surgeons, clinic locations, equipment and ongoing news. A prospective patient arrives worried about a symptom, not knowing the name of the procedure they need. The site has to route them from a concern to the right treatment and the right specialist, while the clinic keeps everything current without a developer in the loop.

The Solution

Next.js on the front end with Sanity as the content platform, queried with GROQ. Images are served from the Sanity CDN, and the whole content model is editable by the clinic's own team.

Modelling content the way patients think

The hard part of a medical site isn't the pages, it's the relationships between them. Treatments connect to the surgeons who perform them, to the locations offering them, and to the screenings that lead to them. Getting those references right in the schema is what lets a visitor start at "what are your concerns?" and arrive somewhere useful, instead of being handed a list of clinical terms.

Handing the site back to the clinic

A clinic runs promotions, adds specialists and posts events on its own schedule. Anything that needs a developer to change is something that quietly stops being updated. The content model is built so the team can publish all of that themselves, which is also the ongoing part of this engagement: I maintain the schema and the Studio as their needs change.

Key Features

• ▸Treatment and eye-screening content organised so patients can start from a concern instead of a procedure name
• ▸Surgeon profiles linked to the treatments they perform
• ▸Multi-location clinic pages with direct call and booking routes
• ▸Appointment listing and enquiry flows
• ▸News and events section the clinic updates itself
• ▸Equipment and technology pages supporting clinical credibility
• ▸Everything editable in Sanity Studio, no deploy required