---
title: "Craft CMS & Hypermedia: How Agencies Build Less and Deliver More"
date: 2026-01-23T12:55:00+01:00
author: admin
canonical_url: "https://craft-kit.dev/blog/craft-cms-hypermedia-how-agencies-build-less-and-deliver-more"
section: Blog
---
Most web projects don't fail because of bad code. They fail because of accumulated complexity — a frontend that drifted away from the backend, an API that needs to stay in sync with templates, a framework that nobody on the team fully understands anymore.

Sound familiar?

This is the hidden cost of modern frontend stacks. And it's a cost that agencies carry for years after a project ships.

## The Problem With the Current Default

The industry default for interactive web projects has become: a headless CMS, a JavaScript framework, a separate API layer, and a build pipeline that ties it all together.

### This stack works. But it comes with a price.

Every new developer needs to learn two systems. Every content model change requires updates in multiple places. Every deployment has more moving parts. And every year that passes, the gap between what the framework expects and what the project actually needs grows a little wider.

For agencies, this means more time debugging architecture and less time building features. More onboarding costs. More maintenance contracts. More conversations with clients about why a "simple change" took three days.

## Hypermedia Is Not a Step Backward

Hypermedia is the architecture the web was built on — and it never stopped working.

In a hypermedia-driven system, the server returns structured HTML instead of raw JSON. The browser renders it. Interactions trigger server responses that update exactly what needs to change. State lives on the server, where it belongs.

This is not nostalgia. It is a deliberate choice to remove complexity that was never necessary in the first place.

For Craft CMS projects, hypermedia is the natural fit. Craft was designed to model content, render templates, and serve HTML. Hypermedia lets it do exactly that — without a parallel frontend application fighting it for control.

### What Datastar Adds

Datastar is a lightweight hypermedia framework that brings reactivity to server-rendered HTML. Live search, filtered listings, real-time updates, pagination — all driven by the server, delivered as HTML fragments over a persistent connection.

No virtual DOM. No client-side router. No hydration step. No separate state management layer.

The result is a Craft project that behaves like a modern web application — without the architectural overhead of one.

## What This Means for Your Agency

The business case for hypermedia is straightforward.

Faster delivery. Without a separate frontend application to configure and maintain, projects move faster from kickoff to launch. There are fewer decisions to make, fewer layers to debug, and fewer dependencies to manage.

Lower maintenance costs. A simpler stack means fewer things that can break. New developers can read and understand the codebase without a guided tour. Content model changes stay contained. Projects remain maintainable years after handoff.

No framework lock-in. Frameworks change. What is standard today may be legacy in three years. A hypermedia-driven project built on Craft and Twig has no framework expiry date. It stays relevant because it relies on the platform — not on a third-party library's release cycle.

Better collaboration. When backend logic and frontend presentation live in the same Twig templates, there is no coordination overhead between teams. Designers, developers, and editors work in the same system — not around each other.

### The Stack That Scales With Your Business

Agencies that have moved to a hypermedia-first approach with Craft CMS report the same thing: projects that were expected to be complex turned out to be straightforward. Projects that shipped fast stayed fast to maintain.

That is not a coincidence. It is what happens when the architecture matches the problem.

Craft CMS is a structured, expressive, server-driven platform. Datastar extends it without replacing it. Hypermedia keeps complexity where it belongs — low.

**For agencies building long-lived client projects, that is not a technical preference. It is a competitive advantage.**