Add a recipe to deploy a Decoupled/Headless CMS

@garphy a decouple recipe would be awesome! But not something we will ship with Drupal CMS anytime soon. We don't want to be seen as gatekeepers of recipes, which can be contributed just like modules. We don't want to try to make Drupal CMS everything for everyone because it's not scalable, so we want to encourage the community to build the recipes that make sense for them.

I agree with Pam -- I think a decoupled recipe would be very cool and useful, but it's not something we need to maintain or gatekeep. If we wanted to ship it as a core part of Drupal CMS, we could always require it as a third-party dependency (something we already do with Easy Email Express → ).

The one thing I would humbly request is that, if you create and publish a decoupled recipe (and I hope you do!), you don't publish it under the name drupal_cms_WHATEVER</em>, as that can potentially cause housekeeping headaches for us later on. It's something that other recipe authors have done without consulting us, and although it's not the end of the world, I'd prefer to keep the <code>drupal_cms_ prefix reserved for packages that are actually part of our subtree split. :)

I'm happy to follow your guidance here. Agreed that it does not have to live within Drupal CMS itself.

What's the best way to handle it then? Create a separate d.o project? Fork Drupal CMS altogether?

Don't fork anything! :)

Just create a new general project → -- and it must be a general project, not a module or theme -- and start creating a recipe in it. You can use any of Drupal CMS's individual recipes as an example to follow, if you want. (Example: https://www.drupal.org/project/drupal_cms_content_type_base → )

Some more docs: https://www.drupal.org/docs/extending-drupal/drupal-recipes →

Closing this as Won't do.

But please share your recipe when you create it.

https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →

FYI, I spun off this to its own project at https://www.drupal.org/project/headless_drupal → .
Thanks for the support and information :)

Nice! Thanks for linking back to it.