Our website revamped in twelve days with ArteZya: what we did, what we’ve learnt from it

On 12 October 2026, at 8.48 am, our old website was replaced by the new one. Twelve days earlier, on 30 September, we had begun work on the project with an archive of the old site built on MODX 2. In between: a new design, rewritten content, 225 redirects and a site checked page by page. Here’s how we did it, and what we’ve learnt that will benefit your projects.

What we revamped

• The foundation: ArteZya, our headless, no-code CMS, running on MODX 3 and the latest version of PHP. Each page is a collection of blocks, which we can edit without touching the code.
• The design, based on our 2026 brand guidelines, created by Valérie, our graphic designer: new logos, a new colour palette, and a dark mode that adapts to your device’s settings.
• The content: our thirteen services have been rewritten, with four removed as they overlapped; twenty-seven blog posts have been proofread, updated and checked, whilst twenty-two have been removed as they were out of date or no longer relevant.
• URLs: every old URL now leads to its new page via a permanent redirect, so that Google and your bookmarks keep up. 225 rules, checked one by one.
• Images: 686, optimised for every screen size and in WebP format, with useful filenames and alt text.
• What you can’t see: the structured data that describes each page to search engines, and a lighter page, designed to use fewer resources.

How we did it in twelve days

Everything can be replicated. The site wasn’t entered manually: scripts retrieve the old content, apply the revised text and set up the redirects. The entire site is rebuilt from scratch in under ten minutes, allowing us to correct a detail and check everything again, as many times as necessary.

Everything is checked. Each rebuild ends with automatic checks: the 225 redirects, the 686 images, and the editor for each block. The go-live process was rehearsed the day before on a test domain. On the day of the launch, our checks identified two issues, which were rectified that same day.

A team of three, including an artificial intelligence system. An AI agent, enhanced by our own developments, carried out much of the technical work: the scripts, the design porting, and the checks. Philippe, a senior consultant, led the project. Matthieu, a software engineer and framework designer, designed ArteZya alongside Philippe and is responsible for its development; he continued to refine it throughout the project. Every piece of text was proofread, every decision made by a human: the AI drafted proposals, the human made the final call. This is what made the twelve-day timeline possible, and it is also why automated checks are so important: they catch errors, wherever they may come from.

The result, measured

• We put the old site back online for a few hours, on the same server, to measure it under the same conditions as the new one (PageSpeed Insights, three measurements each, 14 October 2026). On mobile, the largest element on the homepage loads in 2.3 seconds instead of 6.2, and the first content appears in 0.9 seconds instead of 2.4. On a computer: 0.4 seconds instead of 1.0. And the page no longer flickers whilst loading.
• No URLs from the old site result in an error.
• Search engine optimisation: we’ll know in a few weeks’ time. A migration always causes rankings to fluctuate; we’ll update this post with figures from Search Console.

What this means for your project

Twelve days is not a guaranteed timeframe. We knew our content inside out, and we made decisions independently as we went along. For your website, timelines depend as much on your approvals as on our work. What this project demonstrates is that with a platform like ArteZya, tools that replicate and monitor everything, and swift decision-making, a redesign no longer needs to take months.