Ludwig

Contributed modules often require external PHP libraries. To use them Composer is needed. Ludwig provides an UI alternative to Composer.

However, please note that Composer is highly recommended whenever possible!

Please, read "Switch to Composer", "Switch to Automatic Updates contrib module" and "Ludwig EOL" sections below before you decide to use Ludwig!

Documentation

Developer's guide

Ludwig integration developer's guide and FAQ

Ludwig integrated projects (30+)

For the list of all contributed projects with active Ludwig integration scroll down to the "Project information / Ecosystem" section below.

Ludwig integration support tickets (80+)

For the list of all contributed modules with "Add Ludwig integration" support tickets (both closed and active) see the "Add Ludwig integration tickets" list.

Switch to Composer!

Ever since Drupal 8.8.0 and Composer 2 are released it has become a lot easier to manage Drupal with Composer.

If you are familiar with command-line tools, please consider Migration from Ludwig to Composer (highly recommended).

Can I use both Composer and Ludwig in my project?

If you are using Composer to manage your Drupal project you don't need Ludwig, and you shouldn't use it!

If you decide to switch your Drupal project from Ludwig-managed project to Composer-managed project at some point - don't forget to uninstall and remove Ludwig module from it.

Switch to Automatic Updates contrib module

Please, consider the use of the Automatic Updates contrib module instead of Ludwig!

The Automatic Updates contrib module has a stabile release now. It is a long-term Drupal UI solution for package management. So, try it and find out if it works for you. If not... you can come back to Ludwig always. :)

Ludwig EOL?

The current plan is to maintain Ludwig until a new official module to fetch libraries via UI (Automatic Updates) becomes available in Drupal Core. For Ludwig Retire/End-Of-Life plan and discussion take a look at: #3377094: Retire Ludwig?