drupal / mercury_editor_demo_recipe
Sets up the Mercury Editor demo content type, paragraph types, and content builder configuration.
Package info
git.drupalcode.org/project/mercury_editor_demo_recipe.git
Type:drupal-recipe
pkg:composer/drupal/mercury_editor_demo_recipe
Requires
- drupal/core: >=10.3
- drupal/heading: ^2
- drupal/mercury_editor: >=3.0.0-alpha19
- drupal/mercury_editor_demo_components: 3.0.x-dev
- drupal/mercury_layouts: >=2.0
- drupal/svg_image: ^3.0
- drupal/twig_field_value: ^2.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-10-20 15:15:08 UTC
README
A Drupal recipe that sets up a fully working Mercury Editor demo — content type, paragraph components, sample content, and Style Options — all in one command.
Requirements
- Drupal 10.3 or 11
- Composer
- Drush
Installation
1. Require the recipe via Composer (from your project root):
composer require atendesigngroup/mercury_editor_demo_recipe
2. Apply the recipe (from your Drupal docroot, e.g. web/):
drush recipe ../recipes/mercury_editor_demo_recipe
Troubleshooting an interrupted installation
If SVG demo media fails extension validation, update the recipe, rebuild caches, and apply it again. From a DDEV project root:
ddev drush cache:rebuild
ddev drush recipe ../recipes/mercury_editor_demo_recipe
The recipe updates image-field settings through the field entity API so that cached field definitions are refreshed before importing SVG media. Existing content is skipped when the recipe is reapplied.
Configuration synchronization is separate from applying a recipe. If a full
configuration import proposes deleting paragraph types or uninstalling Paragraphs,
the sync directory does not match the active site. Do not delete existing content
to resolve this. Review ddev drush config:status first. If the active site is the
configuration you intend to preserve, export it with ddev drush config:export
and review the resulting changes before committing or importing them elsewhere.
Usage
After applying the recipe:
- Go to Content and open "Drupal Like You've Never Seen It" — a sample page pre-loaded with demo components.
- Click Edit to explore Mercury Editor with all paragraph types loaded.
- Or go to Content → Add content → ME Test CT to build a new page from scratch.
What the recipe installs
- ME Test CT content type, pre-configured for Mercury Editor
- 8 paragraph types: Button, Card, Divider, Heading, Image, Section, Slideshow, Text
- Multi-column Section layouts: 1, 2, 2-bricks, 3 (25/50/25), and 3 (33/34/33) columns
- Style Options on Button, Card, and Divider components
- Sample page with 88+ demo paragraphs
- All required modules (see
composer.json)
Schema regression check
After installing the recipe, run from the project root:
ddev drush php:script /var/www/html/recipes/mercury_editor_demo_recipe/tests/check-config-schema.php
The check validates Mercury Editor defaults, the recipe's outline icons, and section behavior settings against Drupal's configuration schemas. It also verifies that populated menu groups remain valid YAML text and that the recipe does not bundle optional language configuration. It also checks that SVG extensions are enabled through the field entity action, which refreshes field definitions before content import.
The recipe does not install Language or Content Translation or enable translation for the demo bundles. Multilingual sites can configure translation separately.
Maintainers
Maintained by Aten Design Group.