BoardScribe

Publish board meeting dates, agendas, and minutes on your WordPress website, accessibly. BoardScribe manages meeting minutes as a native custom post type (no ACF required) and displays them with a paginated, accessible table via the [edbs_boardscribe] shortcode or the equivalent Gutenberg block, backed by a built-in REST API endpoint.

• Plugin Website
• Documentation
• Live Demo

• Custom post type for meeting minutes with native meta boxes (no ACF required).
• Shortcode builder in the admin settings page generates a ready-to-copy shortcode.
• Paginated, accessible table display via [edbs_boardscribe] shortcode, or the equivalent BoardScribe Gutenberg block.
• Supports multiple shortcodes/blocks on the same page, each independently configured.
• REST API endpoint (/wp-json/edbs/v1/boardscribe/) for fetching meeting minutes.
• Responsive stacking layout on small screens with accessible column labels.
• Extensive filter/action hooks and JavaScript registries for building add-ons (see Developer Hooks below).

1. Upload the plugin files to the /wp-content/plugins/boardscribe directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the Plugins screen in WordPress.
3. Add meetings via Meeting Minutes > Add New in the admin menu.
4. Use the Meeting Minutes > Settings page to build your shortcode, then paste it into any page or post.

[edbs_boardscribe]

Use the Settings > Shortcode Builder to generate the shortcode with your preferred options. You can also write the shortcode manually using the attributes below.

[edbs_boardscribe included_years="2023,2024" posts_per_page="10" held_date_format="F j, Y"]

A BoardScribe block (equalize-digital/boardscribe) is also available in the block editor, listed under the "BoardScribe" block category. It renders through the same shortcode pipeline and its Inspector Controls expose the same set of options as the shortcode attributes above (including any added by add-ons), with a few caveats: only fields the registry flags with rest_arg are also exposed as REST parameters, a field marked hidden_from_ui is excluded from both the block's Inspector Controls and the settings-page builder (though still valid on existing shortcodes/blocks that already use it), and class/className isn't rendered by the block's generic Inspector loop at all, it's handled by Gutenberg's native "Additional CSS Class(es)" Advanced-panel field instead.

Each meeting minute post has four native meta fields:

• Meeting Date — Required. Date the meeting occurred (YYYY-MM-DD).
• Agenda URL — Link to the meeting agenda document.
• Minutes URL — Link to the published meeting minutes document.
• Meeting Not Held — Checkbox to mark that a scheduled meeting did not take place.

The plugin exposes a public REST API endpoint for fetching meeting minutes data. This is intentional — meeting minutes are public records.

Endpoint: GET /wp-json/edbs/v1/boardscribe/

Example:

GET https://yourdomain.com/wp-json/edbs/v1/boardscribe/?included_years=2024&posts_per_page=10&page=1

The plugin exposes a large set of hooks, JavaScript registries, and reusable methods for building add-ons (Equalize Digital's own Pro plugin is built entirely on top of these).

The front-end table renderer can be replaced or extended without a build step. Add-ons register against these plain window globals before DOMContentLoaded:

The following CustomEvents bubble on each instance's .edbs-boardscribe-wrap container (bind with addEventListener, or on document to catch every instance):

At Equalize Digital, we make use of a specific toolset to develop our code. Please ensure you have the following tools installed before contributing.

• Composer
• NPM

Check out this repository from GitHub, then run:

composer install
npm install
npm run build

assets/build/ is gitignored, so npm run build (or npm start for webpack watch mode) is required after every clone before the shortcode/block will render anything.

There are no special requirements for the dev environment aside from the standard WordPress/PHP runtime used by the plugin, use whatever local stack you prefer (e.g. Local by Flywheel, DesktopServer, LocalWP).

As long as you follow the Getting started steps above, the plugin will run in your local environment.

composer lint      # php-parallel-lint syntax check
composer check-cs  # phpcs (WordPress Coding Standards)
composer fix-cs     # phpcbf, auto-fixes what's fixable
npm run lint:js     # eslint over src/js
composer test       # phpunit (requires ./scripts/setup-phpunit.sh first, or Docker via npm run test:php)

• npm run build - builds the frontend, block editor, and shortcode builder JavaScript bundles
• npm start - watches and automatically rebuilds JavaScript on change
• npm run lint:js - lints the plugin's JavaScript
• composer lint - syntax-checks the plugin's PHP
• composer check-cs - checks the plugin's PHP against WordPress Coding Standards
• composer fix-cs - auto-fixes fixable PHP Coding Standards issues
• composer test - runs the plugin's PHPUnit tests

This is a developer portal for BoardScribe and should not be used for support. Please visit the support forums for support.

Anyone is welcome to contribute to BoardScribe. Please read the guidelines for contributing to this repository.

There are various ways you can contribute:

• Raise an issue on GitHub.
• Send us a Pull Request with your bug fixes and/or new features.

Please also review our Code of Conduct and Security Policy before contributing.

This repository includes generated developer documentation to make it easier to work with the plugin:

• docs/hooks.md - a generated inventory of every edbs_ PHP action and filter in the plugin, kept current by a weekly CI job. It's a mechanical supplement to the curated Developer Hooks section above, not a replacement for it: it doesn't cover the JavaScript registries/events or the reusable PHP methods documented there. Regenerate it locally with:

composer run generate-hooks-docs

This plugin is licensed under the GPLv2 or later.