05
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.
- Year
- 2023
- Technologies
- WordPressVercel
Godmorgen
I don’t just ship projects.I stay with them.
Currently building and maintaining production websites at pro(G.
Over 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.
About
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.
Selected work
Nouvelles Résidences
pro(G
2026
AstroReactCSS+1
Nouvelles Résidences
pro(G
AstroReactCSSGSAP
2026
Coqys
pro(G
2026
AstroReactCSS+1
Coqys
pro(G
AstroReactCSSGSAP
2026
Alpexpo
pro(G
2026
AstroReactCSS+1
Alpexpo
pro(G
AstroReactCSSGSAP
2026
Quobly
pro(G
2026
AstroReactCSS+1
Quobly
pro(G
AstroReactCSSGSAP
2026
Unis
pro(G
2026
AstroReactCSS+1
Unis
pro(G
AstroReactCSSGSAP
2026
Workflow
Performance.Maintainability.Craftsmanship.
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.
Build
01Operate
02Improve
03Modern Tech Stack
Frameworks{Astro·React·Next.js·Alpine.js}—Styling{CSS·SASS·Tailwind·Bootstrap}—Animation Libraries{GSAP·Motion·Jquery}—CMS{WordPress·Shopify·Strapi·Drupal·Sanity}—WordPress Boilerplates{Bedrock·Sage}—Development Tools{Typescript·Docker·Lando·Node.js·Git·Vercel·CI/CD·Sentry}—AI tools{Cursor·Codex·MCP·V0·Lovable}—Design{Adobe·Figma·Zeplin}
Case Studies
04
Building a development workflow around AI.
How I use Cursor, custom skills and automation to remove repetitive work while keeping the parts that matter firmly in my hands.
- Year
- 2026
- Technologies
- CursorMCP
03
Building a private platform for MyCluster Montagne.
A private web platform connecting members through content, profiles, companies and events, with a Next.js frontend powered by the existing WordPress back office.
- Year
- 2025
- Technologies
- Next.jsTypeScriptTailwind CSSWordPressWPGraphQLVercelGitHub
02
Building Bonjour Edgar with a modern Astro workflow.
A production website built with Astro and WordPress, designed for performance, SEO and an efficient editorial workflow.
- Year
- 2025
- Technologies
- AstroTypeScriptCSSWordPressHeadless WordpressWPGraphQLCloudflareVercelGitHubCursor
01
Rebuilding pro(G frontend for long-term evolution.
Migrating a legacy WordPress theme to a modern Astro architecture while preserving editorial workflows, SEO and long-term maintainability.
- Year
- 2023
- Technologies
- AstroTypeScriptTailwind CSSWordPressHeadless WordPressWPGraphQLCloudflareVercelGitHubCursor
Questions I get asked
Why headless, if editors still work in WordPress?
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.
Why Astro, not Next.js, for a WordPress site?
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.
What does a WordPress rebuild actually involve?
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.
What happens after launch?
I keep the site. Performance, infrastructure, editorial workflow, the slow improvements. Shipping is the start.