The `site:export` command should be able to export on top of another recipe
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3574664. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !828 !816 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The blank site template currently instructs people to export their recipe directly: <a href="https://git.drupalcode.org/project/drupal_cms_site_template_base/-/blob/1.x/GET-STARTED.md?ref_type=heads#publishing">https://git.drupalcode.org/project/drupal_cms_site_template_base/-/blob/1.x/GET-STARTED.md?ref_type=heads#publishing</a></p> <p>This will work, and it is the right thing to do, but it will also be missing all of the helpful scaffolding the blank site template includes, like CI configuration, license, README.md, recommended.yml and so forth. It would be best if you could copy that stuff into your exported recipe automatically too.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a <code>--base</code> option to <code>drush site:export</code>:</p> <pre>drush site:export --base=../recipes/drupal_cms_site_template_base</pre><p>This would mirror the base recipe into the destination directory, then export on top of that.</p> <p>Additionally, we should fix some bugs that plague people trying to build site templates (Andy from Dripyard reported these):</p> <ul> <li>The system.site config is exported as an action, but it's using the <em>system</em> path of the home page (e.g. <code>page.front: /page/6</code>, rather than <code>/home</code>). We should intercept this and transform it on export, at least until the relevant core problem (<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/1503146" title="Status: Closed (fixed)">#1503146: Aliased paths cannot be set as front page</a></span>) is released.</li> <li>Menu link parents are not exported as dependencies of menu link content entities. This, we can certainly shim around, and there is a core issue to fix it: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3562072" title="Status: Closed (fixed)">#3562072: Menu link content export with dependencies doesn't include parent menu link entity.</a></span></li> <li>System ships action entities on behalf of the Node module, which cause weird dependency problems. These should just be filtered out of the exported configuration entirely.</li> </ul> > Related issue: [Issue #3562072](https://www.drupal.org/node/3562072) > Related issue: [Issue #1503146](https://www.drupal.org/node/1503146)
issue