Standardizing New Environment Setups

To ensure consistency across our development, staging, and production environments, the UI Suite DevOps team has created a standardized setup procedure for all new Drupal instances. This procedure, based on the official install.md documentation, codifies the specific steps required to get Display Builder running correctly and efficiently.

The first step in our automation script is to ensure all necessary dependencies are present, including handling any required patches for Drupal core using the cweagans/composer-patches plugin. This is critical, as Display Builder's advanced features sometimes rely on very recent changes to core. The script then uses Drush to set required configuration values, such as disabling JavaScript aggregation, which is crucial for ensuring the proper functioning of the builder's UI.

For our local development environments, we also have steps to pull down the necessary JavaScript libraries (like Shoelace and HTMX extensions) locally via npm, rather than relying on a CDN. By scripting this entire setup process, we eliminate manual errors and ensure that every developer at UI Suite is working with an identical, correctly configured foundation. This standardization is key to our operational efficiency and stability.