>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3545451. --> Reported by: [thejimbirch](https://www.drupal.org/user/2507260) Related to !660 !655 !657 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As Drupal CMS evolves into a foundation for site templates, and recipe/site template authors will use and extend the individual recipes, we should add descriptions about what each recipe does to the project page.</p> <p>Currently if you go to any of the recipe project pages, you only get a developer focused bug and feedback message.</p> <blockquote><p>This project is part of Drupal CMS. All bug reports and feedback should be filed in the Drupal CMS issue queue.</p> <p>If you're not using Drupal CMS, you can still use this recipe in your own project. Add it with the following Composer command:</p></blockquote> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>For an MVP, we can at least add the descriptions from the composer.json/recipe.yml and a list of modules the recipes installs and/or configures. That will give end users visibility into the functionality the recipe offers without having to look at the code.</p> <p>I could manage that if @pameeela approves. </p>