Pediatric Dental Redesign — 3 Pages, Draft-First
A three-URL pediatric dental redesign — 43 hours, 87 days, draft-first Divi delivery. Shipped iteratively by 5 specialists for a Seguin, TX practice.
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): Guadalupe Kids Dental — pediatric dental practice, Seguin, TX
Engagement: White-label development for a US marketing agency
Delivered: February – May 2025 · ~87 days · ~43 hours · three Figma-driven page redesigns on a live site
The Craft of a Multi-Page Redesign
A live Divi site, three pages redrawn against a draft-first contract — and on the first homepage pass, a style change propagated into the shared global header, breaking every page on the live domain. The site rolled back to the previous day within a 15-minute window; every subsequent page ran from a cloned test environment. Draft-first was the agency requirement; test-environment-first became ours, enforced by what Divi’s global scope does on a live pediatric dental site.
Snapshot
| Field | Value |
|---|---|
| End-client industry | Healthcare — Pediatric Dentistry |
| End-client | Guadalupe Kids Dental (pediatric dental practice, Seguin, TX) |
| Engagement | White-label multi-page redesign for a US marketing agency specialising in local-business websites |
| Project Type | Figma-to-Divi multi-page redesign — built draft-first, published per page after agency review |
| Scope | 3 pages redesigned — Homepage, New Patients (/new-patients/), Special Needs (/special-kids/) |
| Timeline | ~87 days (February – May 2025) |
| Effort | ~43 hours across all pages and QA — design build · QA rounds · URL and metadata updates |
| Team | 5 specialists (dev · dev+QA · QA · PM) |
| Design handoff | Figma briefs per page (agency-owned; design URLs withheld) |
| Page builder | Divi (Elegant Themes) — existing site builder; no page-builder swap |
| Tech Stack | WordPress · Divi · Site Checker (xaverPRO QA plugin) |
| Build mode | Draft-first — each redesigned page built as WordPress draft, published to target URL after agency-side review |
| Delivered | Three pages live at target URLs — / (homepage), /new-patients/, /special-kids/ — agency review completed before each publish |
| Review rounds | ≈4 review rounds across the 87-day calendar window |
| Per-ticket effort | 7 internal Redmine tickets · median 4h / P75 12h per ticket |
The Brief
A US marketing agency retaining Guadalupe Kids Dental — a pediatric dental practice in Seguin, TX — brought us in to refresh three pages against Figma designs delivered iteratively. The practice’s site used Divi, and the agency was clear about building within it rather than introducing a new page-builder dependency. Pediatric dental patients are children; the parents booking those appointments have urgent, task-oriented interactions with the site — scheduling routine cleanings, researching sedation options, finding the Special Needs care page for a child with different needs. The pages being redesigned were primary entry points for each of those interactions.
The agency’s model on this engagement was iterative: homepage first, then New Patients, then Special Needs — each delivered in sequence, each against its own Figma frame, each approved independently before publish. Draft-first was the expected delivery model throughout. The site was live and booking appointments; no page was to go live mid-build, and no change was to touch shared global components — header, footer, or global theme styles — without explicit confirmation.
The ask on each page was the same: match the Figma in Divi, build in draft, run internal QA across desktop and mobile, submit for agency review, and publish only after approval. Remain outside the end-client-facing loop throughout.
Risk context. Divi is a global-scope page builder: its theme options and global module system mean that a style applied during page-level editing can silently inherit into the site’s header or footer — across every page on the live domain. Unlike Elementor’s widget-scoped architecture, Divi’s global containers are always adjacent to the page canvas. On the first homepage build pass, a style rule propagated unexpectedly into the shared header, producing layout breakage visible site-wide. The team caught it before agency handoff, rolled the site back to the previous day’s backup, and rebuilt the homepage on a cloned test environment. Every subsequent page redesign on this engagement ran from a test clone first, with the global scope validated before any change touched the live site. Divi’s flexibility is real; so is the surface area it exposes when the build discipline isn’t calibrated to it.
How We Did It
1. Homepage rebuild on a cloned test environment after a global-scope incident. The first build pass for the refreshed homepage ran on the live site’s Divi canvas. During that pass, a Divi module styling change propagated into the shared global header — affecting every page on the live domain, not just the homepage being redesigned. The site was rolled back to a confirmed-clean backup. From that point forward, the homepage build continued on a cloned test environment, with the live site left untouched until the redesign had been fully validated in isolation. The finished homepage draft was then migrated to the live site and published only after agency-side review confirmed it was clean.
This was not a minor process adjustment — it shaped how the remaining two pages were handled. Every redesign task on this engagement ran test-first, with Divi’s global scope treated as a constraint rather than an assumption.
2. New Patients page — draft build against Figma, responsive adaptation without mobile frames. The New Patients page (/new-patients/) was the second redesign task, with its own Figma brief. The brief had no mobile-specific design frames; responsive adaptation was handled according to Divi’s standard breakpoints and the agency’s standard for mobile layouts. The page was built as a WordPress draft and only surfaced to logged-in administrators during development. QA across desktop and tablet viewports identified several layout adjustments — heading scale, button sizing, and 1024 px breakpoint handling — before the page was submitted for agency review. The agency reviewed the draft and approved it for publish with minor final adjustments made before the go-live.
3. Special Needs page — iterative build with draft isolation and URL publishing discipline. The Special Needs page redesign carried a specific constraint: the practice already had a live page at a different slug (/special-needs-new/ during development, replacing a live /special-kids/). The development draft was kept at a separate slug throughout build and QA — an intentional draft-isolation pattern to ensure the redesigned page and the existing live page could co-exist without the live page being disrupted. Once the draft passed QA, the published task involved setting the new page’s URL to /special-kids/, moving the old page to draft status, and confirming that the Title, Description, and slug matched the spec. A Divi Builder update attempt during this task hit an Elegant Themes authentication gate — two-factor authentication for new devices blocked the update, requiring out-of-band resolution. The page was published after the URL and metadata were confirmed correct.
4. Coordinated QA across page-builder and mobile viewports. Each page carried a dedicated QA issue (separate from the build issue) assigned to Pavel Sazhin. QA covered desktop and mobile viewports, Divi module rendering at standard breakpoints, and form-element and downloadable-resource functionality — the Special Needs page carried downloadable forms, carried over from the previous version of the page. Mobile-first rendering received additional attention on each page given that parents scheduling pediatric dental appointments are heavily mobile. For each page, QA rounds ran before agency submission; post-agency-review fixes were tracked back through the build issue.
The homepage build on the live site caused the shared header to absorb styles from the new page canvas — every page on the domain broke. We had 15 minutes, rolled back to the previous day, and rebuilt on a cloned environment. The test-environment-first protocol that covered every subsequent page on this engagement came from that one incident.
Operational Integrity at handoff
The homepage build pass on this engagement surfaced a live-site regression before any page reached the agency — a Divi module styling change propagated into the shared global header, contaminating every page on the live domain; the site was rolled back to the previous day’s backup, and every subsequent build ran from a cloned test environment to contain Divi’s global scope from that point forward. 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 |
|---|---|
| Pages redesigned | 3 — Homepage, New Patients (/new-patients/), Special Needs (/special-kids/) |
| Build mode | Draft-first — each page built as WordPress draft, published only after agency-side review |
| Global-scope incident | Site-wide header breakage caught pre-handoff; site rolled back; subsequent work test-environment-first |
| URL publish discipline | /special-kids/ URL and metadata confirmed correct before publish; old page moved to draft status |
| QA coverage | Desktop + mobile viewports across all three pages; tablet (1024 px) breakpoint specifically addressed on New Patients |
| Timeline | ~87 days (February – May 2025) — iterative, page-by-page delivery cadence |
| Effort | ~43 hours across build, QA, and URL/metadata tasks |
| Team | 4 specialists — no dedicated strategist, no design lead (agency-owned) |
| Site status, verified 2026-04 | seguinkidsdental.com live, returning HTTP 200 |
Process
| Phase | Duration | Outcome |
|---|---|---|
| Homepage Figma brief + estimation | ~1 week (Feb 2025) | Design reviewed; Divi confirmed as existing builder; global-scope constraints noted |
| Homepage build — test-environment rebuild | ~2 weeks (Feb–Mar 2025) | Homepage built on test clone after global-scope incident; rolled out to live after rollback; agency review pending |
| New Patients page build + QA | ~2 weeks (Apr 2025) | New Patients built as draft, responsive QA completed, submitted to agency; minor revisions; published |
| Special Needs page build + QA | ~2 weeks (Apr–May 2025) | Special Needs built as draft on separate slug, QA completed; Divi auth issue resolved out-of-band |
| URL publish + final metadata | ~1 week (May 2025) | /special-kids/ URL assigned, old page drafted, Title/Description confirmed correct; engagement closed |
Phases are sequential on this engagement — each page was completed and approved before the next was started. Iterative cadence was the agency’s explicit preference for this client.
Team
Delivery team
- Nikita Tumasevic — homepage build (Divi, test-environment rebuild), New Patients page build, Special Needs page build
- Pavel Sazhin — QA across all three pages (desktop and mobile, Divi module rendering, form functionality)
- Anna Polunina — implementation support and QA
- Lyudmila Travkina — homepage redesign implementation (first pass and rebuild); New Patients responsive adaptation
- Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, Divi authentication coordination, final publish 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 — Figma frames, page content, downloadable resources on the Special Needs page — were the agency’s. We received the Figma brief, implemented it in Divi, and returned a draft for review.
For agencies commissioning iterative page redesigns on a retained client
If your agency has been burned by a dev partner who broke global site components — header, footer, shared styles — while working on a single page, this is the inverse. We run Divi page builds from a cloned test environment, validate global scope before anything touches the live site, and publish only after your review. Send a Figma and a note on the client’s page builder. We will return a fixed-hours estimate within 24 hours, no cost, no obligation.
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.