Centralise course schedules and operational configuration inside WordPress.
Client system / course operations
AWR Course Manager
Keep scheduling, forms and marketing automation consistent across the whole course flow.
01 / Purpose
A tool with a reason to exist.
A WordPress application for course schedules, forms, local submissions, permissions, archives, frontend popups and ActiveCampaign tagging.
Connect participant forms with local records and ActiveCampaign automation.
Expose only the next safe public schedule item to frontend experiences.
Package and promote changes as versioned, inspectable WordPress artifacts.
02 / Decisions
The interesting part is why.
Browser-aware time
A course scheduled in one timezone should appear correctly for an international visitor without rewriting the source record.
External success before local commit
Local state must not claim a participant is synchronized when the marketing platform rejected the operation.
Tiny public contract
The schedule endpoint returns one whitelisted event, not plugin options or participant data.
Immutable packages
Single-root, linted, versioned archives make deployment and rollback inspectable.
03 / Architecture
A deliberate path through the system.
Schedule
Store source-timezone course dates and convert them for each browser at the presentation boundary.
→Submit
Validate participant input and synchronize the required external marketing state.
→Commit
Persist the local submission only after the external synchronization succeeds.
→Publish safely
A whitelisted read-only endpoint exposes only the next event needed by public frontend banners.
04 / Technology
The working parts.
PHPWordPressJavaScriptCSSActiveCampaign APIWordPress REST APITimezone conversionVersioned packages
05 / State & roadmap
What is real now—and what comes next.
- Version 0.5.9 is verified in production.
- Version 0.5.11 is packaged and locally tested but not deployed.
- Core schedule, form, archive and integration paths exist.
- The public next-event endpoint is part of the newer undeployed generation.
- Deploy the accepted 0.5.11 generation through the existing review gate.
- Connect the verified schedule endpoint to the public conversion experience.
- Continue improving operational reporting and administrator clarity.