Install Droost CMS

Droost CMS is a Drupal recipe that extends Drupal CMS into an agent-ready development platform. Pick it when you are starting a site rather than adding Droost to one you have.

What the recipe installs

Everything in drupal_cms_starter: Canvas page building, media, SEO, the admin UI.
Droost with its brain, code and semantic search, the examples corpus, the SDC display composer and the Canvas tree tooling enabled.
Droost Workflow via the droost_workflow submodule.
UI Patterns 2 and its field formatters as the SDC display substrate for structured entities.
Droost Theme as the site default. Mercury stays installed but is no longer default.
mcp_server configured for the stack: pagination raised to 200 so every tool registers on one page, the server named "Droost CMS", and server instructions that mention the workflow.
A shipped design pattern: an event content type whose default display is composed entirely from single-directory components, so a fresh site demonstrates the entity fields → component props and slots → render pattern out of the box.

Install

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

bash

composer require --dev 'drupal/mcp_server:^2.0@alpha' 'drupal/droost:^2.0@alpha' \
  'drupal/droost_theme:1.0.x-dev' 'drupal/droost_cms:1.0.x-dev'
drush site:install minimal -y          # or pick "Droost CMS" in the Drupal CMS installer
drush recipe recipes/droost_cms
drush droost:install                   # the toolset path: editor wiring, 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. Applying the recipe on an already-installed Drupal CMS site is supported, and re-applying it is idempotent: if an apply is interrupted partway, running the same command again completes it.

Root-require with explicit constraints

Droost, Droost Theme and the recipe must be required at the project root with explicit dev or alpha constraints until they have stable releases. Composer ignores stability flags in non-root packages, so the recipe's own requirements cannot widen stability for you.

No root patch

Drupal CMS ships Canvas and this recipe adds UI Patterns, and the two 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 canvas + ui_patterns coexisting — bridged by droost_canvas on a healthy site, and says so if uninstalling droost_canvas re-breaks the pair.

Verify the install

The recipe repository ships scripts/assert-recipe-applied.sh <site-dir>, which checks every promise the recipe makes against a ddev site and refuses to say OK otherwise: the module roster, the default theme, the MCP settings, the front page rendering through Droost Theme.

One nuance worth knowing

The recipe's config/ ships node.type.event, an unprefixed machine name in the same namespace Drupal CMS uses for its own content types. As of Drupal CMS 2.1.3 nothing there defines event, so this is a forward risk, not a present conflict. Before installing an events recipe alongside this one, check whether it defines node.type.event.