Shane Bogue Projects

XRF Lead Services

Local search pages and checked regulatory figures for a lead-inspection company

The XRF Services logo: an X mark beside the words RF Services.
The logo rebuilt as a vector from the company's PDF artwork, on a branch not yet merged. Fig. 1 2026–present
  • Work
  • In progress
Year
2026–present
Role
Designer and developer
Org
XRF Lead Services, Inc.
Stack
Next.js 16, React 19, Tailwind CSS 4, TypeScript, Payload CMS (headless, via @cms/sdk) and 2 more

A site for an Arizona company that does XRF lead-paint inspections, soil sampling and dust-wipe clearance testing. It has service-area city pages, legal pages and a lead bar. I rebuilt it as a headless Next.js app whose page bodies, once hard-coded, are now CMS pages the company will be able to edit once it launches. It is not public yet.

Problem

The company's current site is on GoDaddy Website Builder. They needed pages that rank for the cities they serve, regulatory figures that are actually current, and a site they can edit themselves.

A simple placeholder icon.
Before: the placeholder icon used with a text name. Fig. 2

Approach

One cities.ts file drives the header dropdown, the service-areas grid, the city pages and the sitemap. Shared Terms and Privacy pages, mobile top bars, and lead-bar fields sent under the names the chosen form expects. I checked the dust-lead clearance levels and the federal civil penalty figure against eCFR, the Federal Register and EPA sources and flagged them for the owner and an inspector to review. In the v2 port, an importer turned the fork's code-defined content into 22 CMS pages. Real lead-safe work photos replaced stock where they existed; stock stayed only where the company had no photo of that subject. On a branch not yet merged, the logo is traced to a vector from the company's PDF artwork.

Process

5 dated steps, from the project’s history

  1. 01

    Client fork

    Set up the client preset and upstream remote on the platform template.

  2. 02

    City pages and legal pages

    Flat /{city}-lead-testing pages from one source file, shared legal text, a footer legal column, and a readable sitemap page. The SEO strip and quick-service links now show on phones, where they had been hidden.

  3. 03

    Checked against the sources

    Updated regulatory figures against eCFR, Federal Register and EPA sources, flagged for owner and inspector review, and set the tenant on anonymous lead submissions on the server.

  4. 04

    Headless port and import

    Scaffolded apps/xrf with hero variants, v2 blocks and forms, legal pages, sitemap, robots, security headers and an error page, then imported the fork's content as 22 CMS pages, 9 of them city pages.

  5. 05

    Real photos and a traced logo

    Real lead-safe work setups now illustrate the sections on banned methods, lead dust and lead effects. On a branch not yet merged, the logo is rebuilt as a vector and the admin uses black and the logo's orange.

Results

Runs locally against the CMS with 22 pages imported. It moves straight to the new platform at cutover.

Lesson

I checked the regulatory numbers against primary sources and flagged them for the owner and an inspector to sign off, instead of copying them from the old site.