Deployment

Deploying the theme to production is the same as enabling it locally: require it with Composer, enable the theme, import config, and rebuild caches. All assets are bundled in the theme, so there is no Node build step and no CDN dependency.

1. Require and deploy the code

Add the theme to your project's composer.json and commit the lock file so production installs the exact version:

composer require drupal/adminlte
git add composer.json composer.lock
git commit -m "Add AdminLTE 4 admin theme"

On the production host, install from the lock file:

composer install --no-dev --optimize-autoloader

2. Enable and set as the admin theme

drush theme:enable adminlte
drush config:set system.theme admin adminlte   # administration theme

3. Import configuration

If you manage your site config in code, the enable + block placement should be captured in your config export. On deploy, import it:

drush config:import -y

4. Rebuild caches

Always rebuild the cache after enabling a theme or changing templates/libraries so Drupal picks up the new template overrides, library definitions and asset aggregates:

drush cr

Typical deploy sequence

composer install --no-dev --optimize-autoloader
drush updatedb -y          # run pending database updates
drush config:import -y     # sync configuration from code
drush cr                   # rebuild caches

Production asset aggregation

For best performance, enable Drupal's CSS/JS aggregation at Administration → Configuration → Development → Performance (/admin/config/development/performance), or via Drush:

drush config:set system.performance css.preprocess true
drush config:set system.performance js.preprocess true

The theme's libraries are already marked minified where appropriate, so aggregation bundles them efficiently. Bootstrap Icons fonts ship inside the theme (css/vendor/fonts/), so there are no external font requests.