• 0.5.0: Two new blocks and a single-document template. The Governance documents index block lists a site's governance documents grouped by type (constitution, policies, procedures, codes of conduct, terms of reference, then any others), and each document only appears to visitors who can read it, so restricted, confidential and private documents stay hidden from those without access. The Governance document details block shows a document's type, who approves it, when it was adopted and amended, its registration date, how often it is reviewed and when its next review is due. Single governance documents now use a plugin block template that shows the title, then the details, then the document itself, between the theme's header and footer, so these dates no longer need to be written into the document text and every document shows them however it was created. Themes can replace the template with their own single-lh_governance_doc template or edit it in the Site Editor. The template needs a block or hybrid theme; classic themes show documents as before, without the details panel unless the theme adds the block itself. The plugin now requires WordPress 6.7.
  • 0.4.0: Governance document owners now get BuddyPress notifications when a review needs doing. A document that is in force (not a draft, pending or scheduled) raises a notification when its next review comes within 30 days, again when the review becomes overdue, and again every 30 days while it stays overdue; the repeat interval can be changed with the lh_governance_documents_overdue_reminder_interval_days filter. Each new notification replaces the previous one, so an owner never has more than one per document. Notifications go to the document's owner user, or to everyone holding its owner role on the site when no user is set. The notification wording is worked out when it is shown, so a due notice reads as overdue once the date has passed, and several at once are grouped into a single notice linking to the Review due list. Recording a new adoption or amendment date, which moves the next review date, clears the notification straight away, as does trashing or deleting the document. The check runs once a day on Action Scheduler when it is available, otherwise on WP-Cron, and is unscheduled when the plugin is deactivated. Nothing is sent on sites without BuddyPress notifications.
  • 0.3.0: Governance documents now have a working admin list. The list shows each document's type, owner (a user, or a role when no user is set), adoption date and next review date after the title, and can be sorted by adoption or next review date without dropping documents that have no date yet. A new Review due view, with a count, lists the documents whose next review falls within the next 30 days or has already passed, and those dates are shown in bold with (due) in the list. Every document type now defaults its owner role to Administrator, so a document with a type always has someone responsible for it; setting an owner user or a different role overrides this. Governance documents can now be drafted and edited through the LH MCP General Abilities create-post and update-post abilities, and can be locked by the post locking plugin. They already work with LH Membership's restricted and confidential statuses. Type defaults for approval body, review cycle and owner role are now also filled in when a document's type is set after it was created, which is what happens when a document is created through the MCP abilities; previously they were only filled in on a save that already had a type. The next review date now also corrects itself if something writes to it directly, rather than keeping the wrong date until the document is next saved. Also removes a redundant array_values() call when saving amendment dates.
  • 0.2.0: Governance documents now have a home of their own. This release registers the Governance documents post type (hierarchical, where a parent means the document implements that one, with permalinks under /governance/ and no archive, so a site can keep its own page there) and a document type taxonomy seeded on each site with Constitution, Policy, Procedure, Code of conduct and Terms of reference. Each document records its approval body, adoption date, full amendment history, review cycle (none, 1, 2 or 3 years, or on change), owner (a user or a role), and for a constitution the date it was registered with the regulator. The next review date is worked out automatically from the latest adoption or amendment date plus the cycle, and is kept up to date whenever those change. Documents with no cycle or an on-change cycle are never due by date. Approval body and review cycle are filled in from the document type when not set: constitutions go to a general meeting with no review cycle, policies, codes of conduct and terms of reference go to committee every two years, and procedures go to committee and follow their parent's cycle. All fields are available through the REST API. The plugin header now declares Requires at least 6.5 and Requires PHP 7.4.
  • 0.1.0: Initial scaffold.