- Issue created by @mandclu
- π¨π¦Canada mandclu
Note that there was some spirited discussed about this concept on Drupal slack as part of the Recipes Initiative Meeting: https://drupal.slack.com/archives/C2THUBAVA/p1719959181462799
- π¨π¦Canada mandclu
(pasting in part of a comment from #3458653: Allow "subrecipes" in the same git repo β since it's also relevant here)
As part of the slack discussion linked above @thejimbirch mentionedcomposer suggest
as an existing technical element that is relevant, but in practice not really used by anyone. In theory, Project Browser could have support for composer suggest, and interactively present any listed projects as options to download and apply after the main recipe is applied. This could be path for making it easier to find and apply available extras for a recipe, but on its own it wouldn't allow for any distinction between "recommended" and "available" elements. - ππΊHungary GΓ‘bor Hojtsy Hungary
For the first pass of project browser recipe support, we planned to include basic input for recipes, eg. a contact form recipe would need your email address. A recipe working with a 3rd party service would need an API key. Configurability of recipe combinations beyond that (eg. this recipe suggests these other 3 recipes to install, you can choose) is a step beyond that but I think is somewhat of a continuation potentially in terms of interaction.