How e-collectivites/pleiade-custom-modules works
Project type and purpose
• This is a set of custom Drupal modules (a plugin-based architecture) built to extend the Pléiade Virtual Dashboard.
• The core “module_api_pleiade” provides a common API manager and must be enabled first.
• api_lemon_pleiade is the first connector to LL:NG endpoints, then a series of modules each connect to an external application (GLPI, HumHub, Moodle, Nextcloud, Parapheur, Pastell, Zimbra, etc.).
• Several utility modules (datatable_pleiade, guide_utilisateur_pleiade, module_actu_pleiade, module_general_pleiade, module_postit_pleiade, msg_informatif_pleiade, notification_module_pleiade, accessibility_tools) supply UI widgets, blocks, alerts, and styling.
File structure
• Top-level directories: one folder per custom module, each containing:
– info.yml (Drupal metadata)
– libraries.yml (CSS/JS grouping)
– routing.yml (Symfony routes → controllers)
– module_name.module (hook implementations)
– src/Controller (PHP controllers for AJAX and page callbacks)
– src/Form (configuration forms)
– css & js (frontend assets; often jQuery, DataTables, Moment.js)
– optional config/install (default settings)
• module_api_pleiade sits at the center: it exports an ApiPleiadeManager class used by all connectors.
• Each connector module uses Drupal’s MVC (Controller + Form + Block plugin) pattern.
Additional insights from README
• Installation order: module_api_pleiade → api_lemon_pleiade → other connectors.
• Configuration: each connector exposes a settings page (via Form classes) where endpoints and credentials for the external service are entered.
• The modules render blocks, pages, or menus in the dashboard, pulling data from external APIs through the shared API manager.