The problem
Arrivals, dismissal, schedules, purchasing, and deliveries cross multiple people and systems. Staff need quick actions and a consistent record of what happened.
PORTFOLIO / PRODUCTION SOFTWARE, DEMONSTRATED
A school operations platform built around the working day.
Designed, developed, and maintained for a real educational organization. Explore the actual application: its screens, server actions, permissions, and operational workflows, backed by synthetic records and mocked external services.
Cedar Grove Academy is fictional. Rooms, communities, people and integrations use demonstration data. This is a shared fictional environment.
The implementation
Next.js, TypeScript, Prisma, SQL, and Auth.js in one application. An append-only event history connects intake to computed presence, expected location, and drill rosters.
Your demo environment
The same repository runs against a disposable SQLite database. Credentials and external requests are substituted. This local database is shared by demo visitors; it is not browser-only storage.
FOLLOW A SIGNAL THROUGH THE REAL SYSTEM
Integration walkthroughs
Sign in through the demo button, run a scenario, then open its result in the original application.
Gmail push → delivery status
An order update should reach the delivery board without someone checking a mailbox.
Simulated Pub/Sub notification → existing webhook → mocked Gmail label → real parser → order events and notifications.
Push is a nudge to reread the label. Replay the scenario to demonstrate message deduplication. No Google account is contacted.
Pikmykid bridge → one pickup queue
Two ways to announce a family should not produce two disconnected dismissal boards.
Synthetic bridge payload → existing token and schema validation → roster matching → PICKUP_ANNOUNCED → existing office and classroom boards.
The external platform and bridge input are simulated. The real ingest, match handling, queue, and release workflow remain intact. An announcement is not a dismissal.
Google Calendar → school calendar
Staff need community events alongside the school calendar without retyping them.
Mocked Calendar API response → existing normalization → rolling-window reconciliation → calendar and dashboard.
The mock supplies fictional events; the real sync performs creates, updates, and scoped deletions. Repeat to see an idempotent sync.
Amazon Business → shipment tracking
Purchasing and delivery information need to stay connected to each request and purchase order.
Mock token exchange and Reporting API → existing shipment parsing → database mirror → delivery rollups.
Only provider responses are mocked. The purchasing screens, budgets, P-numbers, approvals, and delivery logic use the original code.
Notifications → inspectable demo outbox
A realistic workflow should show its messages without emailing real recipients.
Original notification call → sendMail interface → local captured outbox.
Invitations, password resets, order updates, and visitor notifications all use the intercepted SMTP boundary. The demo outbox below holds the latest 100 messages for this server session.
Explore the full application
Captured outbound messages
Simulated delivery only. No recipients are contacted. Reload this page after sending from an application screen.
No captured messages in this server session.