Problem/Motivation

Create an outline for Recipe Maintainer documentation.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork distributions_recipes-3381259

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

bsnodgrass created an issue. See original summary.

thejimbirch’s picture

thejimbirch commented
Version: 10.0.x-dev » 1.0.x-dev
sgroundwater’s picture

sgroundwater commented

I added a menu stub pointing to this issue.
(This page can change or be deleted as needed.)

https://www.drupal.org/docs/extending-drupal/contributed-modules/contributed-module-documentation/distributions-and-recipes-initiative/recipe-maintainer-documentation

sgroundwater’s picture

sgroundwater commented

I backed out of this recent www menu/page until we can confirm the proper plan.
We want to be pointing people to the git repo docs.

thejimbirch’s picture

thejimbirch commented

We have a pretty good guide here:

Does it need updating?

https://git.drupalcode.org/issue/distributions_recipes-3381259/-/blob/33...

nicxvan’s picture

nicxvan commented

From my testing it seems these are minimums for how developers will likely use recipes. (Using drush to apply and composer to install)

Drupal 10.3
Drush 13
composer/installers 2.3
Add to installer-paths in composer.json

"recipes/{$name}": [
"type:drupal-recipe"
]