35-Page Oral Surgery Template Customisation

Client (end user): Greenwich Oral & Maxillofacial Surgery — Greenwich, CT
Engagement: White-label development for a US marketing agency
Delivered: October 2025 – January 2026 · 63 days · ~26 hours

The Craft of Template Customisation

Homepage to Figma spec, all 34 remaining template pages colour-adjusted — and then handed to the content team. The agency’s brief for Greenwich Oral & Maxillofacial Surgery scoped the work in two explicit tiers: one page built to the full monochromatic Figma design (#000000 and #ffffff, textures stripped from the dental-template10 base), the rest of the 35-page site colour-adjusted and structurally ready so the content team could populate URLs without waiting on us.

Snapshot

The Brief

A US marketing agency, retained by Greenwich Oral & Maxillofacial Surgery — a multi-surgeon oral and maxillofacial surgery group operating from a Greenwich, CT location — handed us access to the agency’s dental template 10 system running on Kinsta, plus a Figma design file for the homepage. The build environment was the agency’s own Kinsta staging domain; the page builder was pure Elementor (no ACF field references — all service and doctor pages built directly in the block editor).

The ask had two distinct parts. First: build the homepage exactly as specified in the Figma design, including a monochromatic colour scheme (black and white with accent accents from the practice brand), sticky header behaviour, and hover-effect animations. Second: apply the brand colours and typography from the Figma to all existing template pages on the site — service pages, doctor pages, contact and referral pages — and populate each with placeholder content or the practice’s live content as available. The content team would take over URL content after we delivered the template-ready pages. This scope split — homepage to Figma plus colour pass on the template library, with content population deferred — was a deliberate sequencing choice: it kept the customisation phase bounded and let the content team work pages independently once the structural and visual foundation was in place.

How We Did It

1. Figma-as-contract, template-as-canvas. The agency’s Figma file for the homepage governed every structural decision: the hero layout, the section sequence, the monochromatic colour application, the typography. We did not improvise on the design or substitute agency-default elements. Where the Figma was silent (the sticky-header gap over the hero, for instance), we resolved the ambiguity through direct chat with the QA lead and documented the decision before moving forward.

The template-10 system was the canvas. Before beginning the Figma pass, we restored the homepage from the template-10 default (prior client-side content had been pasted directly into the staging site, corrupting the template structure). The clean base allowed the Figma implementation to be systematic rather than remedial.

2. Colour and typography pass across all template pages. The agency’s instruction was clear: apply the brand palette to all template pages and make them available on the site so the content team could begin populating URLs. The dental-template10 defaults used background textures that conflicted with Greenwich’s monochromatic direction; we removed the textures and substituted the slate hero image from the homepage where decorative backgrounds were required. Typography was updated to match the Figma across all page types.

3. Surgical-specialty service taxonomy, correctly scoped. The practice’s service structure reflects oral and maxillofacial surgery’s specific scope: dental implants (including full-arch variants), oral surgery procedures, orthognathic surgery and TMJ treatment, emergencies, oral pathology, and referral pathways for doctors. Four URL changes and 19 redirects in the agency’s sitemap — moving legacy short URLs like /wisdom-teeth/ to nested paths like /oral-maxillofacial-surgery/wisdom-tooth-removal/ — were resolved against the sitemap before handoff. The doctor-page section presented four active surgeons plus a Partner Emeritus designation for a retiring surgeon, all populated with the practice’s publicly available biographical information.

4. QA cycle at template-customisation scale. The agency’s AutoQA and dual-backlog system tracked 471 issues across the SEO backlog (234 rows) and CX backlog (235 rows). Post-handoff, a series of targeted fix rounds addressed layout corrections, a contact-form addition, and icon replacement requests surfaced by the agency’s review team. Each fix round was assigned, QA’d, and closed before the next was opened. The 85-item launch checklist closed before the production site received its final content-team handoff. Among the corrections the post-handoff rounds exposed were template-residue issues the initial colour pass had not caught — a footer link still carrying a previous client’s placeholder data, and shared-template elements that required per-client overrides beyond the Figma-specified palette changes.

The template had been corrupted by prior client-side content pasted directly into the staging site — restoring it from dental-template10 defaults was the prerequisite that made the Figma pass systematic rather than remedial. Once the clean base was in place, the monochromatic palette, texture replacements, and URL structure could each be applied without undoing the one before.

Results

The outcome, restated plainly: the agency received a 35-page oral surgery site with the homepage built to Figma spec, all template pages colour-adjusted and texture-cleaned per the practice brand, and the doctor and service pages populated — ready for the content team without structural corrections pending.

Operational Integrity at handoff

Pre-handoff QA caught a texture-bleed from the base template — the agency’s dental-template10 defaults carried beige background textures that conflicted with the monochromatic brief; each was removed and, where a decorated background was needed, replaced with the slate hero image per the QA note (chat #1353, Timur, 2025-11-04). Pre-handoff QA ran through Site Checker — see our QA discipline for the categories and the fail-zero gate. The agency’s own QA layer — their tools, their process — ran post-handoff and surfaced issues into the shared backlog for our fix loop until they signed off.

Customisations stayed in the per-client overrides; the agency’s shared template components were not modified.

Process

QA and development ran concurrently — the agency’s post-handoff backlog opened while post-launch fix requests were still being scoped, which is why the calendar spans 63 days rather than the sum of individual phases.

Team

Delivery team

• Natalia Bogatel — lead developer, Figma implementation and template colour pass
• Timur Arbaev — QA lead and developer support across QA rounds and fix iterations
• Pavel Sazhin — developer support and QA, initial template review pass
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)

Agency-side project management and client-facing communication remained with the partner agency throughout. Our team was invisible to the end client.

For agencies with a branded template system