Drupal CMS and Varbase
How Varbase 11 relates to Drupal CMS 2, what it reuses, and the Drupal CMS changes that affect a Varbase site or a Vardot site template.
Varbase 11 and Drupal CMS 2 are both built on Drupal core 11.4 with recipes and Drupal Canvas. Varbase reuses some Drupal CMS recipes and modules, and the Vardot site templates install on both.
Checked on 1 November 2026, against Drupal CMS 2.2.7 and a Varbase 11.0.0 project.
How They Compare
Site templates offered
The curated list in site-templates.yml, which includes the four Vardot templates
Every recipe of type: Site in the project, Varbase Starter by default
Front-end theme
Mercury, in the Drupal CMS site templates
Vartheme BS5
Patches
None in the project template
vardot/varbase-patches and vardot/drupal-core-patches
Vardot Site Templates in the Drupal CMS Installer
The Drupal CMS installer lists its site templates from site-templates.yml in drupal_cms_installer. Four entries have Vardot as the creator:
Varbase
drupal/varbase_starter
The Rightup
drupal/rightup
Educare
drupal/educare
Horizon Aid
drupal/horizonaid
Each card links to Learn more, Demo and Documentation. The Documentation links point to the site template pages in this guide, so keep those paths stable.
Choosing a card makes the installer fetch the template with Composer. To install one without the browser, see the template's page.
Recipes Varbase Reuses From Drupal CMS
Varbase Starter 1.0.x applies these Drupal CMS recipes (recipe.yml):
drupal_cms_anti_spam,drupal_cms_authentication,drupal_cms_seo_basic,drupal_cms_seo_toolsdrupal_cms_forms,drupal_cms_accessibility_tools,drupal_cms_search
Varbase AI Base and Varbase AI Figma Base apply drupal_cms_ai. drupal_cms_google_analytics is downloaded with Varbase Starter and applied on demand.
Varbase also installs the Drupal CMS Helper module (through Varbase Media Base). See the telemetry section below.
What Changed in Drupal CMS 2.2
Drupal CMS 2.2.0 was released on 25 September 2026.
One base recipe. The core features of Drupal CMS moved into
drupal_cms_site_template_base(named Drupal CMS Basics). A site template applies it to get the recommended setup.Eight recipes marked unsupported. On Drupal.org, Admin UI, Anti-Spam, Authentication, Content Type Base, Media, Privacy Basic, SEO Basic and SEO Tools are now Unsupported and Obsolete. Their last releases are on the 2.1.x line.
Add-ons stay separate. AI, Forms, Search, Accessibility Tools and Google Analytics remain separate recipes.
A new multilingual recipe,
drupal_cms_multilingual. Varbase uses Varbase Internationalization Base instead.Canvas translation. Canvas pages are fully translatable with Canvas Translate. Varbase installs it with Varbase Internationalization Base.
What This Means for Varbase
Varbase Starter 1.0.x still applies four of the unsupported recipes: Anti-Spam, Authentication, SEO Basic and SEO Tools. Composer still resolves them (
~2), but they no longer get upstream fixes.Varbase does not apply Admin UI, Content Type Base, Media or Privacy Basic. Its own Admin, Content, Media and Security recipes cover them.
Varbase does not use
drupal_cms_site_template_base.
AI Stack
The Drupal CMS AI recipe installs the AI module, the AI dashboard, the amazee.ai, OpenAI and Anthropic providers, the admin chatbot, AI alt text, Drupal Canvas AI and Easy Encryption Admin for the provider keys. It asks for a provider and an API key when applied.
Varbase AI Base applies it and adds the Varbase AI recipes: editor assistant, image alt, taxonomy tagging, context, content review and safety. See Varbase AI Recipes.
Drupal Canvas
Drupal Canvas has been the default editing experience of Drupal CMS since Drupal CMS 2.0.0 (28 January 2026). Varbase 11.0.x uses the same module, Drupal Canvas 1.12, with the Vartheme BS5 components instead of Mercury. See Drupal Canvas.
Telemetry
Drupal CMS Helper sends anonymous usage data to the Drupal CMS team, through Amplitude in the European Union. It is on by default, and it is installed on every Varbase 11 site. On a Varbase 11.0.0 site, the telemetry status reads as enabled until someone opts out.
What it sends, from the Drupal CMS telemetry page: the site template used at install, modules installed and uninstalled later, recipes applied, visits to some admin pages, a weekly ping, and an environment flag. Varbase recipes and site templates (varbase_*, educare, horizonaid, rightup) are on its list of reported names. It does not send content, user data or custom module names, and it sends nothing from tests, CI or preview environments.
To opt out:
In the browser: clear Send anonymous usage data on Administration \ Configuration \ System \ Basic site settings (
/admin/config/system/site-information).Before installing: set the environment variable
DRUPAL_CMS_TELEMETRY=0.On an existing site:
ddev drush state:set drupal_cms_telemetry 0.In every environment, in
settings.php:
The browser and Drush choices are stored in the database, so a new copy of the site asks again. Use the settings.php line to opt out everywhere.
Related
Last updated