>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3593994. --> Reported by: [tim bozeman](https://www.drupal.org/user/2241356) Related to !3 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Today <code>drupal/plus_suite</code> ships as a single monolithic recipe. Applying it installs the whole suite plus a <code>landing_page</code> content type, <code>image</code> and <code>layout_block</code> block types, the optional editorial block types, the non-Layout-Builder inline editing extra, and demo content.</p> <p>That is ideal for a greenfield site, but wrong for an existing site that already has (say) a landing page type, or that wants the page builder experience without these block and content types. There is currently no way to take only the pieces you want.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Split the single recipe into composable component recipes, kept inside one composer package so installation stays a single <code>composer require drupal/plus_suite</code>. An existing site applies only the components it wants; a new site applies the umbrella and gets everything, exactly as before.</p> <p>Structure (all under the one package):</p> <pre><pre>recipes/plus_suite/<br>&#9500;&#9472;&#9472; composer.json&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (unchanged require list: all suite modules)<br>&#9500;&#9472;&#9472; recipe.yml&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (thin alias to the nested umbrella, kept for CI detection)<br>&#9492;&#9472;&#9472; recipes/<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; umbrella: composes every component below + demo content<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_base&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; module installs, config import, config actions<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_layout_block<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_image_block<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_heading_block<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_cta_block<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_teaser_block<br>&nbsp;&nbsp;&nbsp; &#9500;&#9472;&#9472; plus_suite_non_lb_node<br>&nbsp;&nbsp;&nbsp; &#9492;&#9472;&#9472; plus_suite_landing_page</pre></pre><p>Key points:</p> <ul> <li><strong>One composer package, components nested inside it.</strong> No separate drupal.org projects or Packagist packages. The package <code>require</code> list (navigation_plus, lb_plus, edit_plus, and the rest) guarantees every module is present for every component.</li> <li><strong>A <code>plus_suite_base</code> engine recipe</strong> does the shared work: module installs, config import, and the config actions. Every other component lists <code>recipes: [plus_suite_base]</code>, so applying any component pulls in base automatically.</li> <li><strong>The umbrella sits as a sibling of the components and composes them by bare name.</strong> Core resolves a bare recipe include relative to the applied recipe's own directory, so it works from any apply path. A docroot-relative slash include would break under the test harness and CI, which apply recipes by absolute path. The cost is one extra path segment on the "apply everything" command.</li> </ul> <p>Apply commands:</p> <pre><pre>drush recipe ../recipes/plus_suite/recipes/plus_suite&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (everything)<br>drush recipe ../recipes/plus_suite/recipes/plus_suite_landing_page&nbsp; (just one component)</pre></pre>