Website modernisation / in progress
An established WordPress presence is being reconstructed from verified evidence before modernisation. The aim is to preserve valuable work, reputation and routes while replacing fragile platform dependency with a portable, testable foundation.
The live site remains the source of truth while SCC captures routes, rendered behaviour, assets and critical components.
Open current websiteThe replacement is not being marketed as finished. Hero behaviour, testimonials, route fidelity, mobile rendering and hosted visual QA are explicit acceptance checks.
QA gated — not presented as completeCurrent public source captured into the SCC release, not loaded from the client site at runtime.
Routes and useful source behaviour are preserved before design changes are accepted.
The replacement remains explicitly in progress until its hosted visual QA clears review.
The migration engine keeps source HTML and browser-rendered DOM as separate artefacts, reconstructs assets locally and refuses unsafe runtime state rather than producing a visually plausible but unreliable clone.
Both representations are retained so lazy resources can be discovered without blindly serialising mutated JavaScript state.
The hero and testimonial carousel are checked at desktop and mobile viewports before the clone can be treated as acceptable.
Once portable and verified, design, performance, SEO and operational improvements can be introduced without guessing what the original was doing.
The source capture is now visible here. The matching SCC replacement capture will be added when the current build clears review, creating a genuine source-versus-rebuild comparison instead of a marketing mock-up.