README

A Drupal recipe that layers a complete learning management system onto an existing Drupal site, built on the LMS module ecosystem. Applying it sets up:

• Course and class group types (via Group) with membership requests and approval workflows.
• Activity types with answer plugins: true/false, single/multiple select, fill in the blanks, and free text — each with an optional feedback variant.
• LMS admin and teacher roles with sensible permissions.
• Certificates awarded on course completion.
• Course views and navigation blocks, placed in Olivero and Claro.
• Demo course content so the system is explorable immediately after apply.

The recipe also sets the site name to "Drupal LMS" and the front page to /courses; adjust after applying if you are adding the LMS to an existing site.

Requirements

• Drupal core ^11
• PHP per core requirements
• Drush 13+ recommended for applying the recipe

Installation

If your project was created with drupal/recommended-project on Drupal 11.2+, skip to the require step. Otherwise, first configure Composer to place recipes in the recipes/ directory:

composer config allow-plugins.drupal/core-recipe-unpack true
composer require drupal/core-recipe-unpack composer/installers:^2.3
composer config --json --merge extra.installer-paths '{"recipes/{$name}": ["type:drupal-recipe"]}'

Some of this recipe's dependencies are pre-release, so allow their stability levels, then require the recipe:

composer require \
  drupal/lms_certificate:^1.0@alpha \
  drupal/lms_certificate_entity:1.0.x-dev \
  drupal/lms_membership_request:^1.1@beta \
  drupal/lms_xapi:^1.0@beta \
  drupal/lms_yaml:^1.0@beta \
  drupal/lms_demo_kit

Applying the recipe

Recipes are applied once, not installed like modules:

drush recipe recipes/lms_demo_kit
drush cr

Or without Drush, from the webroot:

php core/scripts/drupal recipe recipes/lms_demo_kit

After applying

• Browse to /courses to see the demo courses.
• Assign users the LMS admin or teacher role to manage courses.
• Demo content is regular content — delete it when you no longer need it.

Maintainers

Developed by Tag1 Consulting.