If you experience issues with a local BLT build, try using Dr. BLT to diagnose your problem:

blt doctor

If that isn't helpful, please post an issue on the GitHub issue queue including the following information:

  • Your version of BLT, composer info acquia/blt
  • Your operating system
  • The full log output of your BLT command, wrapped in a codeblock.

In seeking help, please keep the following points in mind:

  • BLT is distributed under the GPLv2 license; WITHOUT ANY WARRANTY.
  • The project maintainers are under no obligation to respond to support requests, feature requests, or pull requests.
  • All contributions to BLT will be reviewed for compliance with Drupal Coding Standards and best practices as defined by the project maintainer.

Contributing to BLT

BLT work is currently being tracked in the BLT GitHub issue queue and organized via a Kanban Board.

Developing BLT locally

If you'd like to contribute by actively developing BLT, we suggest that you clone BLT and also created a BLT-ed project for testing your changes.

Use the following commands to create a testable BLT-created project alongside BLT

git clone
rm -rf blted8
composer install --working-dir=blt
mkdir blted8
cp blt/blt-project/composer.json blted8/
cd blted8
git init
composer install
./vendor/bin/blt install-alias
git add -A
git commit -m 'Initial commit.'

The new blt-project directory will have a composer dependency on your local clone of BLT via a ../blt symlink. You can therefore make changes to files in blt and see them immediately reflected in blt-project/vendor/acquia/blt.