Use a template system to refresh an existing site by preserving useful content and URLs while rebuilding layout, design tokens, components, CMS, and responsive behavior deliberately.

A template can accelerate a redesign without forcing the business to discard everything that already works. The key is to separate valuable content and URLs from the visual system that needs replacing.
List important pages, high-performing landing pages, forms, integrations, CMS content, analytics, and URLs. A redesign should not accidentally erase useful search equity or business workflows.
Compare the required page types and content model with the template. A close structural match saves more time than a visually exciting homepage that needs to be rebuilt.
Keep useful service explanations, case studies, proof, and search-performing content. Rewrite outdated or weak sections rather than treating every old paragraph as sacred.
Map typography, colors, spacing, buttons, cards, containers, and imagery into the new system before customizing page by page.
Use the redesign to simplify fields, remove demo content, and align Collections with how the team actually publishes.
Keep valuable slugs where practical. When a URL must change, map it to the closest relevant replacement and verify internal links after launch.
Responsive behavior, performance, and interactions should be checked after real copy, images, forms, analytics, and scripts are installed.
A template-led refresh works best when the old site provides the content and business knowledge while the template provides a better production system.