Droost CMS

What it is

Droost CMS is a Drupal recipe that turns a stock Drupal CMS install into an AI-agent-ready build platform in a single apply. It composes three projects that are better together: Droost (the toolkit an agent drives), Droost Theme (the theme it styles through), and UI Patterns 2 with Canvas for structured, component-driven pages.

It is the reference install: the configuration the Droost project builds and tests against, and what droost.org itself runs on.

Use this if you are using Droost

Droost CMS exists to stand up a Droost site quickly. It is not a general-purpose distribution, and there is little reason to apply it unless you are adopting Droost. If you are, it saves you wiring Droost, the theme, UI Patterns and Canvas together by hand, and it hands you a working example to copy. If you are not, install Droost on the site you already have instead.

What one apply gives you

• Everything in drupal_cms_starter: Canvas page building, media, SEO, and the admin UI.
• Droost with its brain, lexical and semantic code search, examples corpus, SDC display composer and Canvas tree tooling enabled.
• UI Patterns 2 as the Single Directory Component display substrate for structured entities.
• A shipped design pattern: an event content type whose display is composed entirely from SDCs, authored deterministically by droost_display_compose and exported here, so a fresh site demonstrates the entity fields to SDC props and slots to render pattern out of the box.
• Droost Theme as the site default: Tailwind v4 and daisyUI, design tokens in one editable CSS file, a Canvas-clean SDC library, and a compiled production stylesheet so the site needs no Node to install.
• The methodology and "use all of it" guidance, served through droost_guidelines and written into the AGENTS.md block your agent reads.

Canvas and UI Patterns, together

Drupal CMS ships Canvas; this recipe adds UI Patterns, and the two once fought over the SDC plugin manager (canvas#3561618). As of Droost 2.x no root patch is needed: droost_canvas bridges the conflict from its own service provider while it is enabled, and stands down once Canvas ships the fix. drush droost:doctor reports the pair's live state either way.

Install

On a fresh Drupal CMS project (composer create-project drupal/cms <dir>):

composer require --dev 'drupal/mcp_server:^2.0@alpha' 'drupal/droost:^2.0@alpha' \
  'drupal/droost_theme:^1.0@alpha' 'drupal/droost_cms:^1.0@alpha'
drush recipe recipes/droost_cms
drush droost:install          # the toolset path: editor wiring, the knowledge layer
drush droost:workflow:install # the pipeline path: levers, gates, the pack, the wall

A recipe cannot run Drush, so the two droost:*install commands are the part it hands back to you: they build the brain and the search index and materialize the workflow. scripts/assert-recipe-applied.sh <site-dir> checks every promise this recipe makes against a running site and refuses to say OK otherwise.

⚠️ Local development shape

Droost is a local-only toolkit, in the same class as devel. This recipe is for local and AI-assisted builds; do not deploy the result to production with Droost enabled.

Requirements

Drupal CMS (Drupal 11.1+ / PHP 8.3+), drupal/mcp_server, and the 2.x-era releases of Droost and Droost Theme. Semantic search additionally wants a local embedding backend (Ollama, or any OpenAI-compatible endpoint).

The ecosystem

• Droost is the brain and the tools: introspection that answers from the real site, code and semantic search, the build surfaces, and the plan, code, test, complete workflow.
• Droost Theme is the theme layer an agent restyles through tokens, daisyUI and SDCs.
• Droost CMS (this project) composes the two onto Drupal CMS as one recipe.