---
title: Craft CMS – The modern CMS for creative teams and serious developers
date: 2025-11-10T13:00:00+01:00
author: webworker
canonical_url: "https://craft-kit.dev/blog/craft-cms-built-for-teams-that-care-about-quality"
section: Blog
---
A good content platform should give editors a clear workflow, designers control over the result and developers a codebase they can still understand after handoff. That is why I build with Craft CMS, Twig and Datastar.

## Start with the content

Craft lets you model the actual work: pages, articles, locations and reusable components, with fields and relationships that match the project. Editors see the inputs they need, rather than a generic page builder with every option switched on.

In Craft Kit, Matrix composes page sections and CKEditor handles text with embedded components. Both use the same Twig component templates. Explore the [Builder demo](https://craft-kit.dev/builder) to see the distinction.

## Keep the interface close to the templates

Datastar adds reactivity without replacing Craft's rendering model. Twig still produces the markup. A filter change requests new results; an update returns HTML; signals keep the browser's transient state coordinated.

This is not reserved for the headline demos. Navigation dropdowns, the mobile menu and the search panel use Datastar too. There is no Alpine, React or Vue layer for everyday interface state.

## A shared foundation for the team

- **Editors** work with structured, reusable content rather than raw layout instructions.
- **Designers** get custom markup and styling instead of a theme's constraints.
- **Developers** can follow a feature from its HTML attributes to the Twig endpoint that renders the response.

Craft Kit includes Tailwind and Vite for styling and asset builds. Specialist libraries handle the map, slider and gallery; Datastar owns the ordinary reactive UI. The stack is deliberate, not dependency-free.

## Quality is implemented, not automatic

Accessibility, sensible query limits, eager loading, cache boundaries and server-side validation still need to be built. A smaller rendering architecture makes those decisions easier to see; it does not make them disappear.

## Try it before choosing it

Use the [blog filters](https://craft-kit.dev/blog), [interactive map](https://craft-kit.dev/map), [search](https://craft-kit.dev/search) and [Todo List](/hypermedia-todolist-craft-cms-datastar). Then look at how the templates implement them.

[Download Craft Kit on GitHub](https://github.com/handplant/craftcms-lazy-starter-kit). It is a starter kit for your own Craft and Datastar work, not a finished client website or a mandatory design system.
