Contrib.social

Applied vs. available recipes

Open on Drupal.org →
Created on 10 May 2024, 8 months ago
Updated 12 August 2024, 4 months ago

Problem/Motivation

A nice thing in the mockups for starshot is the idea of having recipes shipped that are not applied by default. Two examples were blogs and webforms.

We can assume that 100% of people installing starshot will want admin UI improvements like Gin, but even if 50% want a blog and 50% want webforms, that's 50% that don't. Or once people have a bit more experience, they might want alternative implementations to those shipped with starshot etc. Having shipped-but-not-applied recipes solves all of this very nicely.

By having them packaged but not applied, it makes it much more obvious that site features can be composed initially. Also if a site definitely doesn't want webforms, they'll never install webforms, then it won't be applied, won't add extra items to the admin interface, and won't need to be updated. In aggregate, this should reduce the maintenance burden for installs over time. There are also some performance/install UX considerations - i.e. Drupal can get to a working install much faster if it doesn't have to apply all the recipes at once along with default content etc. It also means we will need to make discoverability very easy/intuitive, which will help when people want to install remote things with project browser later, since they'll know where to go.

There could be some kind of 'apply everything' meta-recipe for people that really do want to switch on everything just to look around too.

Steps to reproduce

Proposed resolution

Apply admin UI tweaks recipe by default, but keep 'site features' shipped and not applied, at least for the most part.

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan
Status

Closed: works as designed

Component

Code

Created by

🇬🇧United Kingdom catch

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

Comments & Activities

  • Issue created by @catch
  • Comment 7 months ago →
    🇭🇺Hungary Gábor Hojtsy Hungary

    I believe this is something we will definitely want in Starshot. This was the only screen from the mockups that Dries showed in the Driesnote. I don't know what else to do with this issue :)

    I think there is an MVP goal of having hardcoded CMS recipes and hardcoded additional recipes separate which is what Dries stated .

    For a non-MVP I think there is an underlying task between recipes and project browser to identify the "CMS" level recipes from the "additional" recipes. And a stretch goal of somehow having a mapping of which additional recipes are suggested on top of which CMS recipes at least as "most suggested" or somesuch.

  • Comment 7 months ago →
    🇺🇸United States thejimbirch Cape Cod, Massachusetts

    Recipes are applied, not installed to Drupal. Updated the title and the issue summary.

  • Status changed to Closed: works as designed 4 months ago
  • Comment 4 months ago →
    🇦🇺Australia pameeela

    Closing this one since as Gabor said, this is definitely the plan!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024