Athenian Schedule & Appointments
Overview
Product overview
Scheduling systems usually break down when the real service model is more complicated than a simple one-person calendar. Some businesses need direct appointment booking with optional staff selection. Others need to schedule against overall service coverage across a team. Availability often lives in spreadsheets, requests arrive through generic forms, and operations teams end up reconciling bookings manually in the admin.
ASAM solves that by acting as a reusable scheduling runtime inside WordPress. It provides a structured data model for appointments and staff schedules, supports both standard and coverage-based booking modes, gives admins a calendar-based interface for managing requests, and exposes scheduling data through REST endpoints for frontend integrations and future platform extensions.
Use cases
- Service appointments
- Staff scheduling
- Availability management
- Booking workflows
Developer
Developer starting point
This baseline documents the Schedule & Appointments architecture. It does not claim that a live appointment, calendar sync, notification, or customer booking has been exercised.
Ecosystem integration story
WordPress admin
ASAM uses native custom post types for appointments and staff schedules, which keeps scheduling operations inside familiar WordPress admin workflows while still allowing Athenian to layer custom interfaces and structured metadata on top.
Frontend booking flows
ASAM provides shortcode-driven booking and calendar interfaces for WordPress pages. That makes it straightforward to embed scheduling experiences into service pages, member areas, or internal portals without building a bespoke scheduling UI first.
Athenian platform projects
ASAM should be understood as reusable scheduling infrastructure for Athenian implementations. It provides the appointment, availability, and capacity layer that other service-focused experiences can build on, whether those experiences stay shortcode-based or move toward custom frontend applications.
Future service-commerce extensions
ASAM does not currently implement service catalogs, pricing, deposits, recurring appointment logic, or messaging automation. Its commercial value is that it creates the scheduling base those capabilities can attach to later without replacing how appointments and availability are already modeled.
Install
- Reviewed source folder: athenian-schedule-appointment-manager
- Plugin version reviewed: 0.1.0
- Local source inventory: 21 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-schedule-appointment-manager at main / 1b0eb1bc14ef01b613dcb4116ae15d217d80a769.
- WordPress and the configured calendar/service environment.
- Customer identity, availability writes, notifications, calendar synchronization, and booking correctness require separate target verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem ASAM solves — see the linked technical reference excerpt.
- What ASAM does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 2
- Static action/filter hooks detected in local PHP source: 10
- REST route registrations detected in local PHP source: 1
Shortcodes
- asam_booking — includes/Shortcodes.php
- asam_calendar — includes/Shortcodes.php
REST Endpoints
- asam/v1 — includes/REST.php
Hooks
- add_meta_boxes — includes/Meta.php
- admin_enqueue_scripts — includes/Admin.php
- admin_init — includes/Settings.php
- admin_menu — includes/Admin.php
- admin_menu — includes/Settings.php
- init — includes/Meta.php
- init — includes/PostTypes.php
- plugins_loaded — athenian-schedule-appointment-manager.php
- rest_api_init — includes/REST.php
- save_post — includes/Meta.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 83c0ee4a8606cf85b1ae71d6cac31da4ee93412d17a39d3b676d517ef2a25e23
- Repository URL: https://github.com/Athenian-Brands/athenian-schedule-appointment-manager
- Repository reference: main
- Repository commit: 1b0eb1bc14ef01b613dcb4116ae15d217d80a769
Source files include: README.md, assets/admin.css, assets/admin.js, assets/frontend-calendar.js, assets/frontend.css, assets/frontend.js, athenian-schedule-appointement-manager.png, athenian-schedule-appointment-manager.php, athenian-schedule-appointment-manager.zip, docs/asam-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/technical-marketing.md, includes/Admin.php, includes/Meta.php, includes/Plugin.php, includes/PostTypes.php, includes/REST.php, includes/Settings.php, includes/Shortcodes.php, includes/Util.php
Troubleshooting
- This baseline documents the Schedule & Appointments architecture. It does not claim that a live appointment, calendar sync, notification, or customer booking has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.