Integration of Starshot Prototype with DXPR CMS

[Neslee]

Summary

Objective: Integrate the Starshot Prototype into the DXPR CMS to enhance its capabilities and features.

Scope: This issue focuses on the implementation of the Starshot Prototype within the DXPR CMS. This will involve referencing and integrating relevant pull requests and features from the Starshot Prototype repository.

References: Repository: Starshot Prototype

Tasks

1. Review Starshot Prototype Features: Go through the Starshot Prototype repository and identify key features and functionalities that can be integrated into DXPR CMS.

2. Pull Request Analysis: List and analyze relevant pull requests from the Starshot Prototype that contribute to the desired functionalities.

3. Integration Plan: Develop a detailed plan on how to integrate the identified features into the DXPR CMS. Ensure compatibility and smooth operation within the DXPR CMS environment.

4. Implementation: Code the integration following the developed plan. Make necessary adjustments to both Starshot Prototype and DXPR CMS codebases to facilitate integration.

5. Testing: Perform thorough testing to ensure the new features work seamlessly within DXPR CMS. Address any issues or bugs that arise during the testing phase.

Acceptance Criteria

• [x] Successful integration of Starshot Prototype setup into DXPR CMS
• [x] Definition of YAML File (YAML file for basic setup of DXPR CMS site using recipes structure is defined and initiated.)
• [x] Modules and Themes Setup (All required modules and themes are listed and configured in the YAML file)
• [x] Recipes for basic setup, blog, drag-and-drop content types, and associated settings (metatag, pathauto, etc.) are established and documented
• [x] DXPR Builder and Theme Recipes (Recipes for DXPR Builder features and DXPR theme are set up and functional.)
• [x] Multilingual Configurations (Recipes for multilingual support are created, Configurations for translations and permissions are set up and tested.)
• [ ] Managing Multilingual Content (Migrate all Spanish content when multilingual recipe is installed)
• [x] Performance Optimization (Performance recipes are implemented and tested to ensure optimal site speed and responsiveness.)
• [x] Media, Images, Taxonomy, and Views (Recipes for media management, images, taxonomy, and views are established and operational.)
• [x] Spanish Language Configuration (Recipes for Spanish language support are configured and functioning correctly.)
• [x] Permissions Management (Recipes for site-wide permissions are set up)
• [x] Full testing of permissions to ensure proper access control.
• [x] Installer Creation (An installer is created to run post-site install scripts seamlessly.)
• [x] Implement WebP image style overrides
• [x] Remove router_http_port from project .ddev/config.yaml - https://github.com/phenaproxima/starshot-prototype/pull/136
• [x] Remove DRUSH_OPTIONS_URI as unnecessary (DDEV provides it already) - https://github.com/phenaproxima/starshot-prototype/pull/139
• [x] Use recipes ability to borrow values from existing config to set up the Nominatim geocoder - https://github.com/phenaproxima/starshot-prototype/pull/143
• [x] Patch Automatic Updates with #3463662 - https://github.com/phenaproxima/starshot-prototype/pull/145
• [x] Enable Gin's high contrast mode to improve accessibility - https://github.com/phenaproxima/starshot-prototype/pull/147
• [x] Add infrastructure for automated tests - https://github.com/phenaproxima/starshot-prototype/pull/29
• [x] No critical bugs or issues post-integration

[jjroelofs]

Multilingual demo content is postponed, there is a roadmap for supporting this in the recipe infrastructure: https://www.drupal.org/project/drupal_cms/issues/3461541