Part of the discussion in #3458653: Allow "subrecipes" in the same git repo → was a mention of using composer suggest as a way to present additional recipe options. For example, suppose an event recipe wanted to make registration an available feature but wasn't sure this capability would be needed by every site applying the main event recipe. The recipe author could develop a separate recipe to add the registration functionality, and add it to the "suggest" section of the event recipe's composer.json file. At the end of the process of applying the event recipe, a site builder would be present with an option to also apply the event registration recipe.
Extend the functionality of the recipes system to look in a recipe's composer.json file for a "suggest" section. If present, any listed projects would be presented to the site builder as options to be installed. They could apply all suggestions in a single click, skip all suggestions, or. (ideally) have an option to select specific suggestions to apply.
Active
11.0
Code
Implementation may be able to draw on the work intended for ✨ Make it possible for recipes to prompt for input values Fixed , with the critical difference being when in the process the work proposed here would fire.