Capitol GAINS (Government Archives & Information Navigation Suite) is a comprehensive WordPress plugin that provides a suite of tools for managing congressional operations, including meetings, participants, members, files, and related data. The plugin integrates with Advanced Custom Fields (ACF) Pro and Elementor for content management and display.
The plugin registers the following custom post types:
meeting) – Main meeting post typemeeting_participant) – Witnesses and nomineesmeeting_member) – Committee membersmeeting_file) – Files associated with meetingsmeeting_status)meeting_type)committee_type)privacy_type)congress)subcommittee)participant_type)Taxonomies can be enabled/disabled and assigned to different post types via plugin settings.
The plugin uses custom database tables for optimized data storage:
wp_capigacr_meetingmeta – Meeting metadatawp_capigacr_participantmeta – Participant metadatawp_capigacr_membermeta – Member metadatawp_capigacr_filemeta – File metadataDatabase migrations are handled manually via admin UI.
The plugin provides a comprehensive REST API for external system integration with endpoints for:
Base URL: /wp-json/meetings/v1/
This plugin may fetch data from external services in the following scenarios:
api.congress.gov), operated by the Library of Congress. This request only fires when a site administrator has entered a Congress.gov API key in Meetings Settings, and only while that administrator is browsing the member picker on a meeting edit screen or selecting a senator from it — with no key entered, no request is ever made. Each request sends the site’s Congress.gov API key in a request header, the congress number being browsed, and, when a senator is selected, that senator’s bioguide identifier; no site content, user data, or personal information is sent. The service returns public-domain congressional member records (name, party, state, chamber, official website), which are stored on the created member post. See the Congress.gov / Library of Congress terms of use and privacy policy.All external requests use WordPress’s built-in HTTP API with proper SSL verification and timeouts.