Problem/Motivation
CivicTheme has a set of steps required to install CivicTheme. We can automate the setting up of CivicTheme with recipes.
I can see the need for three recipes:
1. Drupal 11 (Core Drupal) - Fresh site install of CivicTheme
2. Drupal 11 (Core Drupal) - activation of CivicTheme
3. Drupal CMS activation of CivicTheme
Proposed resolution
We have a discovery for building the "Site install with CivicTheme" :
https://github.com/civictheme/monorepo-drupal/pull/1355
We have the "Drupal CMS activation" recipe:
https://github.com/civictheme/upgrade-tools/tree/main/drupal-cms-recipes
We do not have the "Activation of CivicTheme" recipe.
Remaining tasks
1. Create / modify the recipes needed
1. Test the recipes
D11 Site Install
Does the site install, install expected config to run Drupal site ie expected views, expected modules are setup - see standard profile installation with the CivicTheme modifications
Drupal CMS Recipes
Does the recipe activate and allow us to create pages in Drupal CMS without issue, does it break anything - we should also look to creating a Drupal CMS environment for CivicTheme testing
D11 Theme activation
Does it modify / create expected configuration
Further work
Since the items above have been done/are in progress, next things to consider:
We have the:
- site_builder recipe
- Drupal CMS recipe
- content Profile recipes
Currently, these are part of the CivicTheme monorepo and targeted at D11. The goal is to allow users to spin up a fully configured CivicTheme instance via a single command.
The key question: Should each of these recipes live in separate projects or branches, or remain within a single centralised repository?
An alternative being considered: Create a new branch for each recipe to isolate concerns and streamline development/testing.
We need a clear approach to ensure:
- Maintainability
- Ease of use for developers and end users
- Alignment with CivicTheme's architecture principles
Note: There is a lot changing with site templates, look into what we should do to make CT really easy to install and configure and develop plan.
Comments
Comment #4
fionamorrison23 commentedComment #5
fionamorrison23 commentedComment #6
fionamorrison23 commentedComment #7
joshua1234511@ivan-zugec
Ongoing work for Drupal 11 compatibility is progressing well under PR #1355. Key updates include:
The installation profile has been updated to reference the new Drupal 11-compatible recipe setup:
Installation profile reference: https://github.com/civictheme/monorepo-drupal/pull/1355/files#diff-e9cbb...
A single command now runs all relevant post-install steps, streamlining the process:
Command line update: https://github.com/civictheme/monorepo-drupal/pull/1355/files#diff-d15d5...
Provisioning of content has been incorporated as part of the automation:
Content provisioning logic: https://github.com/civictheme/monorepo-drupal/pull/1355/files#diff-bb6b0...
Comment #8
fionamorrison23 commentedComment #9
fionamorrison23 commentedComment #10
fionamorrison23 commentedComment #11
joshua1234511Comment #12
fionamorrison23 commented