Finalise the name for Drupal recipes

“Recipes” are the things Symfony Flex uses and overlap a little, conceptually. The similarity could be a good reason to use the same name.

Thanks for opening this issue, but moving ahead with better terminology than “starter kit”. As I wrote on one of the monster Slack threads on this topic:

1. Naming is hard. 😉
2. Blueprints are exact. There’s no flexibility, you have to build precisely what is drawn / written or you’re in trouble. And it’s usually a big effort to get 2 or more separate blueprints to play nicely together. You generally need 1 big blueprint for your whole project or you’ll regret it. Blueprints tend to be expensive and hard to get.
3. Most recipes give you tons of leeway to make substitutions and modifications. It’s normal to combine many dishes in the same meal. Generally much more flexible. Easy to find / share. Usually free.
4. Agree with a ton of what’s already been said I don’t want to repeat.
5. Given what we’re building, and the options / proposals so far, I think “recipe” most accurately maps to what we mean and invokes the right imagery.

The big drawback of “recipe”, as @mandclu points out, is that you generally have to follow them yourself and assemble the dish manually. These are magical, automated recipes. So in that sense, it’s more like ordering take out, or selecting toppings for a pizza or something. The site builder just wants to assemble the buffet for their users, they don’t want to have to do all the cooking themselves.

- -

I still think “recipe” is good, and we can make it clear these are recipes that come with a robot that can prepare them for you. 😉

"Drupal recipe" sounds good. We can bring the 'automatic' install vs 'manual instructions' aspect clear by making the command look automatic.

php core/scripts/drupal recipe PATH/TO/RECIPE

So instead of 'recipe' we can use something like 'install' or 'apply' or 'cook' maybe :)

php core/scripts/drupal cook PATH/TO/RECIPE

Or maybe

drush cook PATH/TO/RECIPE

Actually love the idea of recipe, and building on the ideas from anoopjohn, I love the marketability of "drush cook " - not to mention things have many layers of composability. Recipe -> Course -> Meal - Cook it all.

Based on the previous comments and research from other communities, I agree that "Drupal recipe" is a good name for this initiative.

On a lighter note, people who can cook recipes will be called "Drupal cooks" while those who can prepare recipes will be called "Drupal chefs" :)

"Drupal site recipe" sounds good for me.
Where I agree that "Drupal Recipe" looks fine and good for me from the previous comments and community members.

+1 for Drupal Recipes. We have used the world “template” a bunch of times and as someone who lives in twig why confuse things at all.

For beginners using common terms is a good idea. A recipe is a set of steps you do to build something and when cooking you can mix multiple recipes together to make a new recipe or use them together to make a meal.

Thank you to everyone working on this. IMHO this initiative has the potential to really increase Drupal adoption by letting islets install different recipes to give Drupal a try.

How about Experience Builder?

Hello Everyone,

I tried the recipe concept, but when I executed the below PHP command

"php core/scripts/drupal recipe recipes/contrib/[recipe-name]" in my inside of Drupal web/ directory using in CLI,

it showed the error such as " Command recipe is not defined."

anyone, please help us, why i am getting the "recipe is not defined"?

Does it need to add "recipe" keyword anywhere in the files?

Thank you in advance.