Existing WordPress presentation
The current public site remains the source of truth while SCC captures server HTML, rendered DOM, assets, routes and dynamic components.
Open current websiteWebsite modernisation / in progress
CRS Rendering
A fidelity-first modernisation of the existing WordPress site. The objective is not to throw away what works, but to capture it accurately, verify it visually, remove fragile platform dependencies and then modernise from a trustworthy baseline.
Current statusBuild and visual QA in progress
Verified rebuild being prepared
The after image will be published here only when the current capture passes local and hosted visual QA. Hero slider, testimonials, route fidelity and mobile behaviour are explicit acceptance checks.
QA gated — not presented as completeWhat SCC is doing differently.
The migration engine keeps source HTML and browser-rendered DOM as separate artefacts, reconstructs assets locally and fails closed on unsafe runtime state rather than producing a visually convincing but broken clone.
Source + rendered DOM.
Both representations are retained so lazy resources can be discovered without blindly serialising mutated JavaScript state.
Component-level QA.
The CRS hero and testimonial carousel are checked at desktop and mobile viewports before a clone can be treated as acceptable.
Change after fidelity.
Once the baseline is portable and verified, design, performance, SEO and operational improvements can be introduced without guessing what the original site was doing.
Before and after evidence will be part of the case study.
The Website Modernisation pipeline already creates source/clone screenshots for critical components. Once the current CRS run completes, those QA captures can replace the temporary evidence panels above, giving visitors a genuine visual comparison rather than marketing mock-ups.