Get in touch

Godmorgen

Benjamin Dorey, Astro and Next.js frontend developer in Grenoble, France.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 headless WordPress websites with Astro, and web applications with 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 want sites that still hold up years later, and that clients can use without having to think about the tech behind them.

Selected work

58 production websites, newest first.

2018

2017

  • Sintégrafor pro(GSite replacedGulp · SASS · WordPress
  • Sasicfor pro(GSite replacedGulp · SASS · WordPress

2016

2013

  • Première Avenuefor Première AvenueSite replacedPHP · CSS
  • LM Parfumsfor Première AvenueSite replacedPHP · CSS

2011

  • PharmOfficefor Plasma'comOfflinePHP · CSS

Case studies

Performance.Maintainability.Craftsmanship.

I’m involved in every stage of a project’s lifecycle, from content architecture and frontend development to deployment, maintenance and continuous improvement.

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 security, performance, updates, deployments and infrastructure, so the site keeps 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.jsViteGitVercelCI/CDSentry
AI tools
CursorCodexClaudeMCPV0
Design
AdobeFigmaZeplin

FAQ

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.

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 keep Next.js for web applications. The choice follows the job, not the other way around.

What does a headless 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 looking after the site: security, performance, infrastructure, editorial workflow and improvements over time.

Can editors preview their changes before publishing?

Yes. I build a custom preview that shows unpublished content on the real frontend, right inside the WordPress back office. Editors see exactly what will be published, without leaving the tool they know.

Is headless good for SEO?

Yes, when it’s done right. Pages are generated as static HTML, so they’re fast and easy for search engines to read. URLs, metadata and redirects are handled on the frontend, and on a rebuild I keep existing URLs so rankings aren’t lost.

Does AI write your code?

Partly. It handles the repetitive work: content structures, boilerplate files, types, validation. Architecture, implementation and code quality are still my job, and I review everything it produces before it goes in.