Skip to content

Headless CMS

A headless front end, and the AI in front of it.

I’m a tech lead and senior front end developer, and a forward deployed AI engineer. A headless CMS gives you content through APIs. I build what sits in front of them.

Why headless

Content through an API. Presentation kept separate.

A headless CMS serves content to whatever needs it. That separation is what makes multi-platform delivery practical, and it leaves the front end free to be fast.

Clients hire me as a freelance headless front end developer for that seam: the API, the interface, and a project led with the people who have to run both.

Next.js and Astro

The framework follows the site.

I’m a freelance Next.js developer for application work. Astro is the better tool when the site is content and the browser should do less.

  • Next.js

    Server-side rendering and static generation, built to be fast and kind to search. I use Next.js when there is a session, an integration, or an assistant behind the page.

  • Astro

    Astro’s component model ships less client-side JavaScript. I use it for content-led sites. I don’t use it for a workflow that needs a server and a signed-in user.

Accessible, then intelligent

The front end has to work for people. AI is the extra.

WCAG 2.2 applies to every interface, including ones fed by an API. I led frontend engineering to that standard at Dotcentric, and I bring it here.

Where an assistant helps, I add retrieval over the content the CMS already serves, with permissions and evals, from a prototype to a system your team can run.

One headless CMS I know from the inside

The same pattern on Umbraco.

I was on the Umbraco Headless Community Team from 2022 to April 2024, and advised on APIs, content structures and developer experience for modern JavaScript frameworks. Other headless APIs are the same shape of work.

Freelance Umbraco work

A few useful details

Before we talk.

Next.js or Astro?

Next.js when the site is an application: server rendering, static generation, a session, or an integration. Astro when the site is content-led and should ship very little client-side JavaScript. I will say which one fits.

Does the CMS get replaced?

No. A headless CMS keeps the content and serves it through APIs. I build the front end, and an assistant only when that content should answer questions as well as fill pages.

Can you lead the front end, not only the AI?

Yes. Tech lead and senior front end work is the core of this. I’m a freelance headless front end developer first. AI is added when it is the useful part.

Is the front end accessible?

Yes. WCAG 2.2 applies whether the page is rendered by Next.js, Astro or the CMS. Accessibility is part of the build, not a later audit.

Let’s put AI to work

What would you like to make happen?

Tell me what your business needs, the systems involved and where you’re getting stuck. We’ll work out whether I’m the right person to help.