Problem/Motivation
Drupal recipes allow the automation of Drupal module install and configuration via the user interface and via the Drupal recipe composer plugin.
A Drupal recipe is a tool for Site Builders and Developers to add functionality to a Drupal site. It is like a recipe that provides a series of steps to add functionality. These steps could be taken manually to arrive at the same point. For example, I might want to provide a blog recipe that configures modules to provide a great blogging experience and creates a few sample posts. Or it can include a number of other starter templates and modules to build a full site experience. Ideally Drupal recipes would not configure an entire site themselves but would break out their functionality into smaller starter templates that can be reused by other Drupal recipes.
Drupal recipes are:
- Applied to Drupal sites, they are not installed.
- Easy to share
- Do not lock sites in
- Composible from other Drupal recipes
Proposed resolution
Maybe "Drupal recipe" is not the best name. In Dries's recent keynote they were called Starter templates. Starter template as a name has been dropped because It potentially clashes with starterkit themes. To some people "starter" suggests something that can only be used during install. Template is a word that clashes with HTML and twig templates.
Drupal recipe has some current usages: Lando, DrupalRecipes project (the Fox Valley Drupal group has no issues with core's usage).
Other potential suggestions have been:
- Starter template
- Feature template or Feature builder
- Component template or Component builder
- Drupal build recipe
- Site Recipes
- Feature starter templates