FRGet in touch

Good Evening

I don’t just ship projects.I stayBenjamin Doreywith them.

Currently building and maintaining production websites at pro(G.

View selected work

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.

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

50 production websites, newest first.

Case studies

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

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.

Operate

A project doesn’t stop at launch. I look after performance, deployments, infrastructure and everything required to keep production running smoothly over time.

Improve

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.

Modern Tech Stack

I build withAstro

Tools

Frameworks
AstroReactNext.jsAlpine.js
Styling
CSSSASSTailwindBootstrap
Animation Libraries
GSAPMotionJquery
CMS
WordPressShopifyStrapiDrupalSanity
WordPress Boilerplates
BedrockSage
Development Tools
TypescriptDockerLandoNode.jsGitVercelCI/CDSentry
AI tools
CursorCodexClaudeMCPV0
Design
AdobeFigmaZeplin

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.