CMS Sites
Tidewater Health
Multi-location clinic site
Eleven clinics, forty-odd practitioners and a services list that changes monthly, all driven from three collections instead of eleven hand-built pages.
- Client
- Tidewater Health
- Industry
- Healthcare
- Category
- CMS Sites
- Year
- 2024
- Eleven location pages from one template
- Opening hours corrected in one place, not eleven
- Practitioner and service pages cross-linked automatically
01Client goal
What they came to us with
Every Tidewater clinic page had been built by hand, so a change to opening hours meant eleven separate edits and at least one page always got missed. Patients were calling clinics that had already closed for the day. The site needed to be driven by structured data, and it needed to make finding the nearest clinic offering a specific service a two-click job.
02Scope
What we agreed to build
- 01Content model covering locations, practitioners and services
- 02Location, practitioner and service templates
- 03Clinic finder filtered by service and area
- 04Accessibility pass to WCAG AA on the patient-facing routes
03Delivery
What maztech delivered
One template, eleven clinics
Location pages are generated from a single template. Address, hours, parking notes, accessibility information, the practitioners based there and the services offered all come from collection fields, so a change is made once and appears everywhere it is referenced.
Cross-links that maintain themselves
Services reference locations and practitioners reference both. A service page therefore lists every clinic offering it and every practitioner delivering it, and a practitioner page lists their clinics, without any of those lists being written by a person.
A finder built for the actual question
Patients arrive asking for a service near them, so the finder filters on service first, then area, and shows the clinic with its next opening time and phone number in the result itself rather than one click further in.
Accessibility taken seriously
Contrast checked against AA across the patient-facing routes, forms fully labelled with errors announced, the finder operable from the keyboard alone, and every clinic photograph given alt text that describes the entrance a patient is looking for.
04CMS setup
How the content model was built
Three collections and the references between them replaced every hand-maintained list on the site. Reception staff update hours from the editor, and it changes everywhere at once.
Locations
Collection- Fields
- Name, slug, address, coordinates, phone, opening hours, parking and access notes, photograph, services multi-reference
- Why
- Drives the location page, the finder result and the footer clinic list from one record.
Practitioners
Collection- Fields
- Name, slug, title, registration number, biography, portrait, languages, locations multi-reference, services multi-reference
- Why
- Appears automatically on the pages of every clinic and service they are referenced from.
Services
Collection- Fields
- Name, slug, summary, description, referral requirement, locations multi-reference
- Why
- Generates the service page and populates the first filter in the clinic finder.
05Components
Components used
- Location card with next opening time
- Opening hours table
- Clinic finder with service and area filters
- Practitioner card with languages spoken
- Service summary block with referral note
- Accessible appointment enquiry form
- Emergency information banner
Each one is a named, reusable component in the project, not a one-off section. That is what lets the team add pages later without the design drifting.
06Performance
Performance notes
Map loaded on demand
The interactive map is not loaded until a visitor asks for it. Until then the location page shows a static image and the address in text, which is what most patients read anyway, and the heaviest asset on the page never loads for them.
Structured data per clinic
Each location page carries local business schema generated from its own fields, including address, telephone and opening hours, so search results show correct hours for the specific clinic rather than head office.
Tested on the devices patients use
QA ran on mid-range Android hardware on a throttled connection rather than a desktop cable, because that is what most of the traffic is.
07Gallery
Screens from the build
Next step
Want a build like this one?
Tell us about the project and we will come back with a scope, a timeline and a price, plus an honest note on anything we think should change.
Or reach us directly
Studio hours are 9am to 6pm across US and EU time zones, Monday to Friday.
