Senior Drupal Team for Low-Code Association & Producer Platform

## Drupal Configuration-First Technical Approach To reduce custom development, simplify long-term maintenance and allow the client to manage most of the platform through configuration, the MVP must be built with Drupal 11, preferably using Drupal CMS as the starting point. The project should follow a configuration-first and low-code approach. Drupal core and established contributed modules should be used for: * Structured content types and fields * User accounts, roles and permissions * Member and producer profiles * Multi-step forms * Conditional form logic * Editorial and administrative workflows * Dashboards and reporting * Search and filters * Multilingual content * Media and document management * Notifications and automated actions * CSV and Excel exports * PDF generation * REST and JSON:API access The expected module ecosystem may include: * Drupal CMS / Drupal 11 * Webform * ECA * Profile * Views * Workflows * Content Moderation * Search API and Facets * Entity Print * Views Data Export * Geofield and Leaflet * Group and Subgroup, where appropriate Applicants may recommend alternatives, but they must explain why those alternatives provide better maintainability. The platform must not be developed as a fully custom PHP application inside Drupal. Custom code should be limited to functionality that cannot be implemented reliably through Drupal configuration, such as: * Versioned producer scoring rules * Complex geographic access control * Specialized PDF and QR-code generation * External payment or Mobile Money integrations * Future marketplace synchronization All necessary custom functionality should be consolidated into a small, modular custom module provisionally. Business logic must not be placed inside the Drupal theme. All Drupal configuration must be exportable, stored in Git and deployable between local, staging and production environments. The project must be managed with: * Composer * Drush * Git * Configuration Management * Separate staging and production environments The selected team must provide: * A complete list of modules used * The reason for each module * Confirmation of Drupal 11 compatibility * Confirmation that production modules are covered by Drupal security advisories * Exported configuration * Installation and deployment instructions * Administrator documentation * Automated tests for custom functionality * A 60-day corrective warranty The client is an experienced software developer but wants to maintain the platform mainly through Drupal configuration rather than ongoing custom coding. Applicants must clearly identify which requirements will be delivered through configuration and which requirements will require custom code.