As a distribution builder or site builder, I want the recipes included in Drupal CMS to be available as standalone packages so that I can reuse them in my distribution or site without using Drupal CMS's scaffold project.

[balsama]

#70 implies that all of the recipes will be developed in a monolith repo (as it is currently). But we should have automation that splits the atomic Recipes into their own repos for distribution so that they can be reused outside of the scaffold project for both distribution builders and individual site builders.

[phenaproxima]

Yup, agreed on this. I'm not sure how to set up the subtree split, but at least there's prior art on that. This is most definitely blocked until Starshot finds its permanent home under DA control (most likely on GitLab...at least, that's what I hope for).

[phenaproxima]

Just for visibility - this is something I discussed with Alex Pott. The current plan is for all recipes (yes, all recipes, everywhere) to be their own tiny Composer packages -- this prevents ambiguity and package nesting, which is a pure Drupalism that needs to die.

Starshot would then be bifurcated into:

1. A metapackage that brings in all the component recipes but provides nothing of its own. This is the same thing drupal/core-recommended does.
2. A template project that sets up Starshot with quick installs, DDEV/Lando integration, etc.

[simesy]

Why wouldn't (in time) all the recipes used by starshot just be avaialble in the project browser, or whatever tool will be used for recipes in Extend.

[phenaproxima]

@simesy: I think that is, eventually, the exact aim. But there's a lot of infrastructure that needs to happen for that first, across several initiatives and at the DA's end.

[simesy]

Yes agreed, i see how it's a good thing at this point (and a good feature in general) to have default recipes in the same repo.