drupal / quorum

1.0.0-alpha1 2026-09-08 15:50 UTC

Requires

• dompdf/dompdf: ^3.1
• drupal/disable_html5_validation: ^2.0
• drupal/entity_browser: ^2.9
• drupal/geofield: ^10.0
• drupal/gin: ^3.0 || ^4.0 || ^5.0
• drupal/gin_login: ^2.0.3
• drupal/leaflet: ^10.0
• drupal/localgov_base: ^1.3.1 || ^2.0.0
• drupal/localgov_core: ^3.0
• drupal/localgov_page: 1.x-dev
• drupal/masquerade: ^2.0
• drupal/redirect: ^1.12
• drupal/simple_media_bulk_upload: ^2.0
• drupal/simple_sitemap: ^4.1
• drush/drush: >=10
• setasign/fpdf: ^1.9
• setasign/fpdi: ^2.6

Requires (Dev)

• drupal/core-dev: ^11.0

GPL-2.0-or-later

Published on Packagist.org on 2026-09-09 15:53 UTC

README

Quorum is a committee management system for local government: forward plans, agendas, meetings, decisions, sign-off workflows, councillor registers of interest, and the public-facing meetings calendar and decisions list that go with them.

It's a Drupal 11 install profile (quorum) for the public-facing pages and theming, with the data model: committees, councillors, meetings, agenda items, forward plan items, sign-offs, registers of interest, defined by Quorum's own custom modules.

These custom modules will be spun out into separate projects as this project matures.

Custom modules

Module	Purpose
quorum_committees	Committees, councillors, wards and parties. These are the core entities everything else refers to.
quorum_meetings	Committee meetings, attendance, and the public meetings calendar.
quorum_agenda	Agenda items, minutes and published decisions for meetings.
quorum_forward_plan	Forward plan items, sign-off by lead directors, and published forward plans.
quorum_signoff	Named sign-off checkpoints (e.g. Legal, Finance) with a visible, logged status per step.
quorum_interests	Structured, revisioned registers of interests for councillors.
quorum_dashboard	A personal to-do list for governance work, and deadline reminder emails.
quorum_notify	Emails the distribution list when a meeting agenda is published.
quorum_pack	Compiles a meeting agenda pack into a single PDF with continuous page numbering.
remote_template	Fetches a remote HTML template and uses it to wrap local Drupal page content.

Loading data

A fresh install has no committees, councillors or meetings. There are multiple ways to populate data:

• Example data — fictional data for the "London Borough of Silverbrook", useful for local development and demos:

  ddev drush quorum:setup-example-data
  

  This creates wards, parties, councillors and committees, then invokes hook_quorum_example_data() so quorum_meetings, quorum_forward_plan, quorum_agenda and quorum_interests can each install their own example data too, in dependency order.

  This command refuses to run unless $settings['quorum_allow_unsafe_operations'] = TRUE; is set, which safeguards it from being run in production. Don't set that option to TRUE in production.

• CSV import — drush quorum:import-committees and drush quorum:import-councillors load committee and councillor data from CSV.

Using a remote template

To consume a template from an existing site, set the site to use the quorum_base template, and configure the remote_template module at /admin/config/services/remote-template. Existing templates for popular committee management systems should just work. quorum_base can be extended by a custom theme if required to alter the handling of remote templates.