Dental Website Redesign
A full dental practice website redesign from Figma to Elementor Pro — 10 templates applied across ~102 pages, 68 hours of work, 54-day delivery.
Screenshots captured by automated tooling — some elements may not have loaded fully or may layer on top of each other. For the most accurate view, visit the live site →
Redesign multiple pages against the agency Figma. Draft-first delivery; principal post-review round; launch only after sign-off.
Client (end user): DG Dental (Dr. Dory Green) — general dental practice, Fort Lauderdale, FL area
Engagement: White-label development for a US marketing agency
Delivered: March – May 2025 · 54 days · ~68 hours · on schedule, no overrun
The Craft of a Homepage Redesign
Ten Figma page templates applied across 102 pages of a Fort Lauderdale dental practice site — plus a site-wide sanitization pass to remove every reference to the practice’s prior “Boutique & Spa” positioning before delivery. The pages were already on a staging server; the brief was to apply the design and flag any content gaps, not to build from blank. Our role was template-by-template Figma fidelity and a complete legacy-brand sweep before the agency took it live.
Snapshot
| Field | Value |
|---|---|
| End-client industry | Healthcare — General Dentistry |
| End-client | DG Dental (Dr. Dory Green, Fort Lauderdale FL area) |
| Engagement | White-label dental website redesign for a US marketing agency specialising in local-business websites |
| Project Type | Full-site Figma-to-Elementor Pro redesign — applied across all page templates |
| Scope | ~102 pages — homepage, About, Services (lander + individual service pages), Blog (lander + posts), Contact, Financing/Insurance, Doctor bio, Results gallery |
| Timeline | 54 days (28 Mar – 21 May 2025), on schedule |
| Effort | ~68 hours — development across 10 page template types, content integration, QA rounds, post-delivery edits |
| Team | 4 specialists (lead developer + QA lead + project lead) |
| Design handoff | Figma design (agency-owned; Figma URLs withheld — agency design IP) — 10 page layouts + homepage |
| Tech Stack | WordPress · Elementor Pro · agency WordPress hosting · Site Checker (xaverPRO QA plugin) |
| Build mode | Figma-faithful — each template type built from the Figma reference; per-page content supplied by the agency |
| Delivered | Full dental practice site redesigned to Figma spec — 10 templates, ~102 pages, staged on agency server, delivered for launch |
| Review rounds | ≈4 review rounds across the 54-day calendar window |
| Per-ticket effort | 10 internal Redmine tickets · median 2.2h / P75 10h per ticket |
The Brief
A US marketing agency managing a dental client — Dr. Dory Green’s practice in the Fort Lauderdale area — needed the existing WordPress site redesigned to match a new Figma brief. The brief covered the full site: homepage, all service pages, About Us with a doctor bio sub-page, blog lander and post template, a financing and insurance page, and a patient-results gallery. In all, 10 distinct page layout types, applied across roughly 100 pages.
The agency had already migrated the existing content to a staging environment on their server. Our job was to apply the Figma design to every page — verify the content was there, apply the design, and flag any gaps. The brief also required removing prior branding that was no longer relevant: the practice was shedding its previous association with “Boutique & Spa” positioning, and any residual references to that identity needed to be cleared across the site before delivery.
The ask was concise: match the Figma across every page type, integrate the supplied content per the agency’s Google Docs, confirm all pages are present and correctly designed, and deliver to the agency for launch. Stay outside the end-client-facing loop. Remain the invisible implementation layer.
Risk Context. A full-site dental redesign on a retained client’s live staging environment carries a different risk profile than a fresh build. The pages already exist; the content is already there. The failure mode is not a missing page — it is a misapplied design element that propagates silently across 40 service pages before anyone catches it, or a legacy brand reference that survives the redesign and shows up under a patient’s name search. The agency’s protection against this is implementation discipline: every template checked, every content page verified, every legacy brand mention found and removed before handoff.
How We Did It
1. Figma-to-Elementor Pro, template by template. The homepage and each of the 10 page template types were built in Elementor Pro against the approved Figma frames. Nikita Tumasevic led the build, working through each template type in sequence — services layout, blog layout, doctor bio, results gallery, contact, and financing pages — before moving to the per-page content application pass.
Because Elementor Pro was already installed on the staging site, the build slotted into the existing site infrastructure without introducing new dependencies. The Figma brief was the single reference for visual decisions; no scope interpretation was required.
2. Content integration per agency-supplied Google Docs. The agency provided per-page content in Google Docs — one document per template type, detailing the copy, headings, and CTA structure for each page. Content was applied to the correct Elementor blocks per the design. The service pages required more judgment than most — the original site had structured service pages as long-form articles, while the Figma introduced distinct content sections (“About the service”, “How it works”, “Benefits”). Content was distributed across those sections by the team, with any ambiguities flagged back before shipping.
3. Legacy brand sanitization. The practice was in the process of rebranding away from its prior “Boutique & Spa” positioning. This required a site-wide pass to remove references to that earlier identity — in page copy, blog post references, and any other visible surface where the old brand might persist. This was tracked in the agency’s QA spreadsheet and completed before the final delivery pass.
4. QA rounds before agency handoff. Internal QA ran with Pavel Sazhin — reviewing every template type against the Figma and confirming the content-per-page assignments were correctly applied. The QA tab in the agency’s Google Sheets workbook tracked open items by priority. Only high-priority items were resolved inside the main engagement; lower-priority refinements continued in follow-on issues after the initial handoff.
Redistributing 40+ service pages from long-form articles into Figma’s three-section layout — About the service, How it works, Benefits — was the task that required the most judgment on this engagement. The template was straightforward to apply; getting the content into the right blocks, without either discarding text or overstuffing sections, was what the build hours actually went into.
Operational Integrity at handoff
On this engagement the QA load fell on URL structure and legacy-brand sanitization: pre-handoff QA caught that all 102 pages were reachable with and without a trailing slash — site-wide redirects enforced before delivery — plus a cyclic redirect on the homepage logo link; a content pass cleared every “Boutique & Spa” reference from pages, posts, and menus per the agency’s QA checklist. 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.
Results
| Metric | Outcome |
|---|---|
| Site redesign | Shipped — Figma applied in Elementor Pro across all ~102 pages and 10 template types |
| Build mode | Figma-faithful — no visual decisions made outside the brief; deviations flagged to agency before implementation |
| Templates | 10 template types — homepage, About, Services lander, Service page, Blog lander, Blog post, Contact, Financing/Insurance, Doctor bio, Results gallery |
| Legacy brand sanitization | All “Boutique & Spa” references removed site-wide per agency QA checklist |
| QA rounds | Internal QA by Pavel Sazhin — all high-priority items resolved before handoff |
| Timeline | 54 days (28 Mar – 21 May 2025), on schedule |
| Effort | ~68 hours — distributed across design implementation, content integration, QA, and post-delivery refinements |
| Team | 3 specialists — no dedicated strategist, no design lead (agency-owned), no SEO lead (no migration scope) |
| Delivery | Staged on agency server, delivered for agency-controlled launch |
The outcome, restated plainly: the agency’s Figma was applied to every page type on a dental practice site, the prior brand positioning was cleared, all high-priority QA items were resolved, and the site was delivered staged and ready for the agency’s own launch process.
Process
| Phase | Duration | Outcome |
|---|---|---|
| Brief & estimation | ~3 days | Figma reviewed, page inventory confirmed (102 URLs), Elementor Pro confirmed |
| Design implementation | ~2 weeks | All 10 template types built against Figma; per-page content applied from agency Google Docs |
| Internal QA round | ~1 week | Pavel Sazhin against all template types; high-priority issues logged and resolved |
| Legacy brand sanitization + content edits | ~1 week | Boutique & Spa references removed; agency-requested content edits applied |
| Post-delivery follow-on | ~3 weeks | Additional edits per agency QA spreadsheet — low-priority items and content refinements |
Phases overlap — QA ran alongside late-stage content integration, and post-delivery follow-on issues were handled in parallel with agency-side review. The 54-day calendar reflects the full engagement from issue open to final issue close.
Team
Delivery team
- Nikita Tumasevic — lead developer (full site design implementation, template system, Figma-to-Elementor build)
- Pavel Sazhin — QA and project coordination (internal QA rounds, agency communication, issue tracking)
- Anna Polunina — implementation support and QA
- Anton Hersun, xaverPRO — project lead (estimation, agency-side sign-off)
Agency-side project management, design, and client communication remained with the partner agency throughout. Our team was invisible to the end client. All design decisions were owned by the agency; our role was Figma fidelity across every page and template type.
For agencies commissioning a full-site redesign on a retained client
This pattern fits agencies managing a retained local-business client with a full WordPress site — an existing Figma brief covering every page type, agency-supplied content in Google Docs, and a staging environment already in place. If that matches your setup, send the Figma and a URL inventory. We will scope the template types, identify any content-restructuring work (service pages in particular tend to carry this), and return a fixed-hours estimate within 24 hours — no cost, no obligation to proceed.
Don't have a spec yet? Send a one-paragraph description — we'll come back with the questions worth asking. Send a description →
draft page
This case is multi-page. The same discipline applies to single-page.
Homepage Redesign and Multi-Page Redesign share the same core methodology — Figma-led, tool-ecosystem-matched, draft-first. Scale differs; discipline does not.