Ascension Roofing
Real Colorado roofing work, a clear estimate journey, and a carefully managed move from WordPress to Next.js.
- The work
- Client website
- My role
- Strategy, design, copy, engineering and launch
- Year
- 2026
A complete rebuild for an owner-led Colorado roofing business, from positioning and project storytelling through engineering and launch. The site pairs a distinctive high-desert identity with evidence that helps homeowners understand the work and request an estimate.
The challenge.
A roofing website has to establish trust before someone can inspect the craftsmanship themselves. This rebuild also had to carry an existing WordPress site into a new platform while preserving useful URLs, estimate delivery, and the company’s email service.
Decisions that
shaped the work.
Show the reasoning behind the roof
I developed the Roof Record around four steps: observed, recommended, built, and final check. The Crestone project explains why bathroom exhaust routing was corrected before the standing-seam roof went on. Real photographs, phase labels, and specific captions connect the recommendation to visible work.
Give every page a useful next step
Service pages explain the situation a homeowner might recognize, then connect to relevant work and an estimate request. The form carries the selected service forward and allows a preferred contact method, keeping the inquiry tied to the visitor’s original need.
Treat migration as part of the design
The launch plan accounted for protected URLs, redirects, canonical pages, consent-based measurement, and recovery backups. Estimate delivery was checked through the client-owned email service, and existing business email continuity was verified during the domain cutover.
A closer look.
Real project photography and concrete details establish the context before the story unfolds.
The Roof Record connects the finished roof to the decisions that came before it.
A launched site with an operating plan
The Next.js rebuild launched in August 2026 with the approved local Roof Record, responsive service pages, working estimate delivery, and documented hosting and recovery procedures. The content model supports later project additions without making an external CMS a requirement for the launch.
What I take forward.
The Roof Record gave the visual identity a practical purpose: make the contractor’s judgment legible, then make the next conversation straightforward.
