--- title: Why Craft Kit date: 2026-04-24T10:46:00+02:00 author: admin canonical_url: "https://craft-kit.dev/craft-cms-starter-kit-agencies" section: Pages --- WordPress is a plugin problem. TYPO3 is a configuration problem. Headless is a complexity problem. They're different symptoms of the same mistake: the wrong tool for the job. Every agency has the same story. Too many moving parts, too much time configuring, too little time building. The stack is different. The problem is the same. **Craft CMS is the answer most agencies haven't tried yet. Craft Kit is a production-ready Craft CMS starter kit that gives your team a clean foundation — without the overhead of a headless setup, a JavaScript framework, or a plugin ecosystem held together with hope.** > Craft Kit is a scaffold, not a theme. It gives you a structured starting point with established patterns and sane defaults — then gets out of the way. Every part of it is meant to be adapted, extended, or replaced to fit the project at hand. ## Less stack. More product. - 👥 ## Smaller teams, same output One developer can own the full stack. No separate frontend and backend specialists required. - 🚀 ## No DevOps overhead One stack, one deployment. No pipeline between your CMS, your API, and your frontend. - ⚡ ## Faster onboarding New developers are productive from day one. Twig is readable. The structure is obvious. No framework to learn first. - 🔧 ## Lower maintenance cost Fewer moving parts means fewer things to break, fewer dependencies to update, and fewer midnight alerts. - 🤝 ## One team, one codebase No frontend/backend split. No handoff friction. The whole project lives in one place, owned by one team. - 🛡️ ## A platform with a roadmap Craft 5 is LTS — five years of support after Craft 6 ships. Craft 6 brings Laravel under the hood. The platform is going somewhere. ## Why Craft CMS? Craft is one of the few CMS platforms that gets content modeling right. Fields, sections, entry types, Matrix blocks — the authoring experience is flexible enough for complex projects and simple enough that clients actually use it without training. It doesn't force a data structure on you. You build exactly what the project needs. For agencies coming from WordPress or TYPO3, Craft is the upgrade that doesn't feel like a compromise — cleaner content modeling, no plugin bloat, and a codebase you can actually own. And the platform is moving in the right direction. Craft 6, due in late 2026, is being built as a Laravel package — meaning it can be dropped into any existing Laravel application and treated as a first-class dependency. The full Laravel ecosystem becomes available: packages, middleware, tooling, and a talent pool that's orders of magnitude larger than any niche PHP framework. For agencies evaluating long-term platform risk, that matters. Craft 5 is now an LTS release, with five years of support guaranteed after Craft 6 ships. There is no pressure to migrate before you're ready. > The CMS your editors will actually use. > The platform your developers won't want to leave. ## Why not headless? Headless architecture makes sense for a specific set of problems: native mobile apps consuming the same API, highly distributed content teams, microsecond performance SLAs at massive scale. For most agency projects, it introduces complexity without solving anything the client actually asked for. The Hypermedia approach — server-rendered HTML, enriched where needed with lightweight interactivity — delivers the same results with a fraction of the moving parts. Craft CMS handles content modeling and rendering. Twig handles templating. Datastar handles the reactive bits. That's the whole stack. > Same UX. Faster development. Fewer dependencies. > Easier onboarding for the next developer on the project. ## **100 across the board** The demo site runs 100 across the board — not as a benchmark exercise, but as a direct consequence of the architecture. Server-rendered HTML is fast. Semantic markup is accessible. Clean output is indexable. > These scores hold without any special optimization pass. > They are the baseline, not the goal. ![Craft Kit demo site scoring 100 in Performance, Accessibility, Best Practices and SEO on Google Lighthouse.](https://craft-kit.dev/uploads/transforms/_768xAUTO_crop_center-center_85_none_ns/Bildschirmfoto-2026-04-24-um-12.25.01.png?v=1777035245) craft-kit.dev — 100/100 across all Lighthouse categories. No optimization pass required. ## The stack **Craft CMS 5, Twig, Datastar, Vite, Tailwind CSS, DDEV, SEOMate** **— and nothing else.** Every tool has a reason to be here. DDEV ensures every developer on the team gets the same local environment on day one. Vite handles asset bundling with instant HMR. SEOMate covers Open Graph, meta, and sitemaps without configuration overhead. Datastar replaces the need for a JavaScript framework wherever reactivity is required. What is not in the stack is just as deliberate: no React, no Vue, no Next.js, no GraphQL, no separate API layer. > Every tool chosen on merit. Every tool you can replace. > Nothing you can't explain to a client. ## Datastar demos — real-world patterns Craft Kit ships with working examples of the most common reactive UI patterns, built with Datastar and server-rendered Twig. No JavaScript build step. No component library. No state management library. These are demos, not finished components. The point is to show the pattern clearly so you can adapt it to what the project actually needs. ## Craft CMS live search with Datastar Instant filtering, server side [Search](https://craft-kit.dev/search) ## Craft CMS blog listing with Datastar paginated, filtered, reactive [Blog](https://craft-kit.dev/blog-hypermedia-datastar) ## Craft CMS. todo list with Datastar Full CRUD, no JS framework [Todos](https://craft-kit.dev/hypermedia-todolist-craft-cms-datastar) ## LLM-ready out of the box Craft Kit includes the LLM Ready Plugin. Append .md to any entry URL and the page renders as clean Markdown — structured, readable, and machine-consumable without additional templates or configuration. > AI crawlers index it cleanly. LLMs summarize it accurately. Your content is machine-readable by default — no extra tooling, no extra cost. ![LLM Ready Plugin showing Markdown output for a Craft CMS entry — appending .md to any URL returns clean, machine-readable content.](https://craft-kit.dev/uploads/transforms/_768xAUTO_crop_center-center_85_none_ns/Bildschirmfoto-2026-04-24-um-11.21.21.png?v=1777035245) LLMs love it. AI crawlers index it. Zero extra configuration. ## AI-assisted development setup Craft Kit ships with a complete Claude Code configuration so AI-assisted development works on day one. CLAUDE.md gives Claude the full project context — stack, architecture, conventions, folder structure. .claudeignore keeps it focused on relevant files. .mcp.json connects Claude Code to the Craft MCP Plugin for direct access to the running Craft installation. A Datastar skill set — attribute reference, SSE patterns, and philosophy docs — is included as a Claude skill folder. > A developer unfamiliar with Craft or Datastar can be productive from the first session. > The setup does the explaining. ## Ship on time Your next project starts in a few weeks. How many developers does it need? How long until the first deployment? If the answer is uncomfortable — it's time to look at the stack. Craft CMS doesn't just simplify the architecture. It puts deadlines back in reach and keeps maintenance predictable. Smaller teams, faster builds, less time firefighting. Ship on time. Stay on top of it. The web was Hypermedia before we called it that. A URL returns HTML. The browser renders it. That's still the fastest, most accessible, most maintainable architecture there is. We just forgot. > Every JavaScript framework was built to solve a problem that server-rendered HTML doesn't have. --- Craft Kit is available on [github](https://github.com/handplant/craftcms-lazy-starter-kit). If you are evaluating it for an agency project or want to talk through whether this architecture fits your stack, [get in touch](https://webworker.me/). Questions about the Hypermedia approach, Datastar integration, or how to migrate an existing Craft project — happy to discuss any of it.