Making headless invisible for editors.
An internal WordPress plugin I progressively built to simplify preview, deployment and day-to-day workflows for editors working with headless websites.
- Project
- Internal WordPress plugin
- Year
- 2023
Good Evening
with them.Currently building and maintaining production websites at pro(G.
View selected workOver the past ten years, I’ve worked on dozens of production websites. Today, I help them evolve. Tomorrow, AI will continue to change how I work, not why I build.
I'm a frontend developer based in Grenoble, France. At pro(G I build production websites, mostly headless WordPress with Astro or Next.js.
I've been doing this since 2011. Since 2017 I've been the agency's only developer, which means I own the work from content architecture to deployment.
I care about sites that still make sense a few years later, and about editors who don't have to understand the stack to use them.
50 production websites, newest first.
An internal WordPress plugin I progressively built to simplify preview, deployment and day-to-day workflows for editors working with headless websites.
How I use Cursor, custom skills and automation to remove repetitive work while keeping the parts that matter firmly in my hands.
A private web platform connecting members through content, profiles, companies and events, with a Next.js frontend powered by the existing WordPress back office.
A production website built with Astro and WordPress, designed for performance, SEO and an efficient editorial workflow.
Migrating a legacy WordPress theme to a modern Astro architecture while preserving editorial workflows, SEO and long-term maintainability.
As the sole developer, I’m involved in every stage of a project’s lifecycle from content architecture and frontend development to deployment, maintenance and continuous improvements.
From content architecture to frontend implementation, I build websites designed to evolve. Every project starts with a solid foundation that stays easy to maintain as it grows.
A project doesn’t stop at launch. I look after performance, deployments, infrastructure and everything required to keep production running smoothly over time.
I automate repetitive work so I can spend more time building the parts that matter. AI, automation and custom tooling help me move faster, while implementation, code quality and technical decisions remain mine.
I build withAstro
Because the frontend can be fast and maintainable without taking WordPress away from the people who write. Editors keep the back office they know. I take care of preview, deployment, and everything that would otherwise leak into their day.
Astro ships as little JavaScript as it can. For a content site that has to last, that's usually the right default. I use Next.js when the product needs it, like a private members platform. The choice follows the job, not the other way around.
Keep the CMS. Replace the frontend. Preserve the editorial workflow, the URLs, the SEO. That's the work I did on pro(G: a legacy theme to Astro, without asking editors to change how they publish.
I keep the site. Performance, infrastructure, editorial workflow, the slow improvements. Shipping is the start.
Cette page existe aussi en français.
Lire en français