Problem/Motivation

Archimedes has a dependency on drupal/cms. Technically speaking, that doesn't work, but it is in service of a clear intent -- Archimedes intends to build on top of Drupal CMS's foundational recipes and functionality, without incorporating all of it.

Proposed resolution

Archimedes should be applied on top of Drupal CMS, and then exported as a full-size site template using drush site:export. That's the best practice documented in Drupal CMS's official site template starter kit (see https://git.drupalcode.org/project/drupal_cms_site_template_base/-/blob/...).

This will have a two-pronged effect:

  • Archimedes will properly inherit all Drupal CMS functionality, without needing to screw around with dependencies.
  • All the configuration and content will be fully under Archimedes' control, so it can remove things it doesn't need (like the Utility page content type).

Issue fork archimedes-3577045

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

phenaproxima created an issue. See original summary.

phenaproxima opened merge request !1

nexusnovaz made their first commit to this issue’s fork.

nexusnovaz’s picture

nexusnovaz commented
Status: Active » Fixed

Thanks @phenaproxima, i've done some extra work on it and merged it in!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.