Acquia BLT, available on GitHub, generates new Drupal projects using a standardized template that is based on Acquia Professional Services' best practices.
To improve efficiency and collaboration across Drupal projects, Acquia BLT provides both a common set of tools and standardized structure, hopefully helping developers reduce incidents of duplicated work, speed up project set up time, and get new developers onboarded more quickly.
Using Acquia BLT for your Drupal projects will help you meet the following goals during your development cycles:
- Provide a standard project template for Drupal based projects
- Provide tools that automate much of the setup and maintenance work for projects
- Document and enforce Drupal standards and best practices through default configuration, automated testing, and continuous integration
Acquia BLT offers the following features for your organization's use:
- Local Git hooks - Validate formatting, syntax, and compliance with Drupal coding standards
- Testing frameworks - Provides default configurations for Behat and PHPUnit
- Project automation tasks - Includes commands for syncing environments, compiling front-end assets, and executing tests
- Deployment artifact generation - Includes building production-only dependencies and sanitizing production-environment code
- Continuous integration and deployment tools - Supports both the Acquia Cloud pipelines feature and TravisCI
Use the following steps to help you get started using Acquia BLT:
- Review the minimum skillset for using Acquia BLT to determine if Acquia BLT is a good fit for your organization.
- Review the Acquia BLT documentation to determine which version of Acquia BLT to install.
- Review the system requirements, and then perform the installation steps appropriate for your operating system.
- Review the repository architecture to familiarize yourself with code organization practices in Acquia BLT
Developing with Acquia BLT
Acquia BLT offers commands that can simplify many of the everyday tasks required in development, including the following:
- Configure continuous integration (CI) - Using Acquia Cloud pipelines or TravisCI
- Generate build artifacts - As a part of the release process
- Deploy code to Acquia Cloud - Using Acquia Cloud pipelines or TravisCI
Acquia BLT and Remote Administration
Acquia BLT is compatible with Acquia's Remote Administration service only if all vendor and Drupal code is committed to the main development or build branch. Although the Remote Administration service cannot update Acquia BLT itself, Drupal core and contributed modules can be updated.
If your website's deployment process builds your production codebase using continuous integration and your
composer.lock files are committed to the codebase, Remote Administration cannot perform updates on your website.
For more information about Acquia BLT, including installation instructions and how to use its available hooks,
see the Acquia BLT documentation.