Contrib.social

Allow for selection of elements (subrecipes) when applying a meta-recipe

Open on Drupal.org →
Created on 3 July 2024, 2 months ago
Updated 4 July 2024, 2 months ago

Problem/Motivation

The proposed recipes for Starshot sound ambitious, in terms of the amount of functionality they are intended to provide. For example, consider the proposed Events recipe → .

To be competitive with plugins available for Wordpress, a Drupal Events recipe might contain a variety of functionality, including:

  • Core event handling (content type and view)
  • Interactive calendar display
  • Locations and mapping
  • Registration
  • Notifications and reminders

Not every site will need all of these features. So, applying a meta recipe will could end up provide functionality not needed by some sites (potentially adding work to the ongoing upkeep of the site). Alternatively, the recipe could leave some pieces to be in separate recipes, but then the site builder would need to find and apply the correct, associated recipes.

Proposed resolution

It would be ideal if there was a way, in such a scenario, for the site builder to choose what elements they want to include when applying such a recipe. Any options skipped when applying the recipe could be added later, also through the project browser. Perhaps the Project Browser UI could visually indicate (and also provide an accessible cue) which recipes had only been partially applied.

There is a separate discussion in #3458653: Allow "subrecipes" in the same git repo → about how subrecipes could be stored an associated with the metarecipe, but I believe there should also be some way for a recipe creator to designate which available subrecipes would be "recommended" (installed by default) vs. "available" (only installed if the site builder explicitly chooses to add them).

✨ Feature request
Status

Active

Version

2.0

Component

User experience

Created by

🇨🇦Canada mandclu

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mandclu
  • Comment 2 months ago →
    🇨🇦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

  • Comment 2 months ago →
    🇨🇦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 mentioned composer 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.

  • Comment 2 months ago →
    🇭🇺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.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024