madmasel.hu / 14 September 2026
Madmasel: we changed the platform before changing the site
For the Engine v4 migration of a live automotive site, the first requirement was a byte-preserving migration proof. The development system, CI/CD and rollback changed; the customer-facing artifact did not.
Situation
madmasel.hu was already live and receiving advertising traffic. In that situation, combining a platform migration with a redesign, tracking changes and a runtime replacement would have created unnecessary risk. The first step was to prove that the new build could reproduce the same public output.
Approach
We wrapped the site in a pinned KampányMűvek Engine v4 setup with a deterministic copy-build contract, PR quality gates, production deployment, live QA and rollback workflows. The migration proof compared the generated artifact with the starting state, allowing us to separate the platform change from the frontend modernization that followed later.
Outcome
The site gained a new release process without the migration itself altering public content. That made it much safer to tackle legacy frontend dependencies and PageSpeed issues afterwards, because stable CI/CD and a tested path back were already in place.