46-Page Dental Template Customisation in Las Vegas

Client (end user): Haven Dental (Dr. Thomas Hsieh) — a dental practice in Las Vegas, NV
Engagement: White-label template customisation for a US marketing agency
Delivered: November 2025 · 83 days · 43 hours · 46 active URLs · on schedule

The Craft of Template Customisation

46 pages of a Luminous dental template customised to a Figma spec for a Las Vegas general dentistry practice — 10 templates, 43 hours, 83 calendar days. The distinguishing constraint was parallel management: 37 additional pages provisioned in staging throughout the build had to stay in a non-indexable state while active delivery continued, and a recurring spa-like copy residue from the shared template base required four dedicated remediation rounds after initial handoff.

The value is speed with consistency — but only if the customisation is disciplined. A dev team that “interprets” the Figma, skips QA rounds, or deviates from the template’s design system is worse than starting from scratch.

This case study is a record of a template customisation executed to the agency’s Figma, with a QA profile that shows the discipline it takes.

Snapshot

The Brief

A US marketing agency brought us in to customise their Luminous dental template for Haven Dental, a practice at 9375 S. Rainbow Blvd. in Las Vegas, NV, led by Dr. Thomas Hsieh. The agency held the upstream work: the Figma design, the Kinsta hosting environment, content coordination with the practice, and the staged deployment structure. Our role was development-and-QA execution only.

The scope was among the larger Templated engagements in our portfolio. The site’s service architecture spanned five dental care categories — cosmetic dentistry, emergency dentistry, preventive dental, restorative dentistry, and oral surgery — each with its own lander page and multiple sub-pages. Thirty-two of the active 46 URLs were service pages sharing the same Service Page template, each customised to per-practice content and imagery. An additional 37 pages were provisioned in staging but held hidden pending post-launch content delivery; these required careful management to avoid premature indexing.

The discipline requirement at this scale is not about volume — it is about template copy residue. A large-scale Templated build assembled from a shared base has predictable failure modes: copy-pasted placeholder text surviving into live pages, template-origin tone inconsistencies, contact details or service language that echoes the wrong practice. On Haven Dental, the agency’s issue backlog tracked a recurring class of exactly these findings across multiple rounds — content errors that were invisible to the dev pass but surfaced under editorial review. The QA loop existed precisely to surface and close those items before sign-off, and the 272+ tracked issue-backlog rows show the volume that discipline requires. One recurring category — spa-like register phrasing inherited from the template’s prior-industry copy — required four dedicated post-launch fix rounds to remediate, a limitation specific to large-scale template customisation where page copy originates outside the dev team.

How We Did It

1. Figma-as-contract, template-as-canvas. The Figma file was the design spec. The Luminous branded template was the underlying page structure. Our job was to reconcile the two page by page — where the template’s default layout matched the Figma, we kept it; where the Figma required a deviation, we customised. No design decisions originated on our side. We chose per-client overrides over modifying the shared Luminous template because a direct edit would have cascaded to every other agency client site built on the same base.

2. Managing hidden-page provisioning alongside active delivery. Haven Dental’s sitemap contained 83 rows total: 46 active URLs for launch and 37 flagged as hidden (“Page Hidden”), pending the practice’s content delivery. Managing both sets in the same Kinsta environment required keeping the hidden pages in a clean, non-indexable state throughout development — provisioned but suppressed — so that the launch of active pages was not contaminated by stub content from held pages. The agency flagged several hidden-page-related errors in the SEO backlog during QA, confirming that a passive approach to hidden pages (simply not publishing them) was insufficient; active status management was required through the life of the project.

3. QA cycle at template-customisation scale. A clean template customisation is not “build once, review once”. It is “build, QA, adjust, QA, adjust”. The agency’s backlog tracked 145 SEO issues and 127 CX issues — 272 rows across the two backlogs — across a 40-item launch checklist. The issues spanned the full editorial surface: missing or placeholder contact details (email, social links, hero text), service taxonomy mismatches from the template, copy that carried a spa-like tone rather than a dental-practice register, and placeholder testimonial text that survived into live pages. Each category required targeted correction without inadvertently cascading a fix into pages where the original text was correct.

The principle is unchanged: on a templated build, the QA loop is where the value is delivered. A shorter loop means a weaker match to the Figma and a higher probability of template residue surviving into live pages.

4. Customisation without drift. Each change to the Luminous template was confined to per-client overrides. The shared template structure was not modified. The Haven Dental customisation did not change the template’s behaviour on any other Kinsta site that uses the Luminous base.

5. Cross-device verification. Customisations were QA’d across Chrome, Firefox, Safari, and Edge on desktop, tablet, and mobile viewports. Each QA round targeted the pages affected by that round’s delta set rather than the full 83-URL sitemap — coverage without redundant review cycles.

Working under 37 non-indexable stub pages alongside the 46-page active delivery meant the sequencing had to be deliberate: suppress-and-verify for hidden pages before go-live, spa-like copy remediation addressed across four discrete rounds rather than one terminal pass. The order was the discipline — the active set launched clean because the hidden set stayed controlled.

Operational Integrity at handoff

The dominant QA load on this engagement was spa-like copy residue from the shared template base — the agency raised dedicated fix tasks “Replace SPA-LIKE Copy” (3 rows, Redmine #1097) and “Final Spa Removal” (#1206) across multiple rounds, and a separate pre-launch task flagged empty hidden pages that «will be indexed soon after we make website live» (#1197) — all resolved before go-live. 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.

Results

The outcome, restated plainly: the agency’s Figma was implemented against their Luminous branded template across 46 active pages and 10 templates, with 37 additional pages held in managed hidden state for post-launch delivery, over 83 calendar days.

Process

Development and QA ran concurrently throughout. Post-launch rounds addressed content residue items that surface only under full editorial review of a live site — a normal cadence on a large Templated engagement where 37 hidden pages are pending content and the live set covers 32 service pages.

Team

Delivery team

• Natalia Bogatel — lead developer (template customisation, Figma-to-layout mapping, post-launch fix coordination)
• Pavel Sazhin — QA (issue-backlog review, design-fidelity verification, fix rounds)
• Timur Arbaev — QA support (additional QA rounds, credentials and image updates)
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off, xaver-tier QA)

The agency managed design, content, client communication, and hosting entirely upstream of our work. Our team was not visible to the practice. Work orders came in through the agency’s shared issue backlog; no task was marked done without agency-side reviewer sign-off on each item.

For agencies with a branded template system