Install additional modules

For installing additional contrib modules or other packages (libraries) we strongly recommend to use Composer because it allows you to install all dependencies and check if installed modules (and vendor packages) don't have any incompatibilities with added module.
For installing vendor packages and javascript libraries you can use commands in the table below.

But if you want to install a new contrib module you should bearing in mind than Opigno can be installed in two different ways - with Composer or from a tarball.

If you install Opigno with Composer (see details):

Task	Composer command
Installing a contrib project (latest version)	composer require drupal/PROJECT
Installing a contrib project (specific version)	composer require drupal/PROJECT:1.0.0-beta3
Installing a javascript library (e.g. dropzone)	composer require bower-asset/dropzone

If you install Opigno from downloaded tarball (see details):

For maintaining tarball version installation you need to specify a path to contrib modules to avoid duplication and incompatibility with Opigno.
In this case, in the root "composer.json" file you should replace the string:

"modules/contrib/{$name}": ["type:drupal-module"]

with this:

"profiles/opigno_lms/modules/contrib/{$name}": ["type:drupal-module"]

When you specify a path to contrib modules for module installation you can use commands from the table above.

Anvanced way how to manage your dependencies for Opigno

You can add your own custom module to manage added dependencies for Opigno. See here for more details.