CHKM8 Custom Component Inventory and Verification

Known component names

• chkm8-competency-expiry-widget
• chkm8-daily-site-report
• chkm8-dynamic-qr-codes-large-wordmark
• chkm8-evidence-photos
• chkm8-form88-photo-optimizer
• chkm8-loler-expiry-widget
• chkm8-operative-activity
• chkm8-operative-certificates
• chkm8-page-access
• chkm8-signature-full-width
• chkm8-submission-dashboard

How to document a component accurately

1. Record its installed plugin name, version and source (plugin, snippet, theme or other code).
2. Identify its admin settings page, if any.
3. Record its data source and any required Gravity Forms IDs.
4. Record which roles can see and use it.
5. Test the intended workflow using a test account and sample record.
6. Record errors, dependencies and known limitations.

Documentation boundary

The component names above are known identifiers, not a complete technical specification. Settings, data relationships and permissions must be verified against the code/version actually installed on the CHKM8 site before the guide is treated as authoritative for those details.