My calendar is one of the primary ways I make commitments visible and real.
If something is not on the calendar, it is much less likely to happen reliably. I use calendaring not only for scheduling meetings, but for protecting time, coordinating with others, making obligations visible, and reducing ambiguity around what I am available for.
A well-maintained calendar is part of how I keep work, communication, and commitments from becoming vague or accidentally conflicting.
Public site: calendar.mikeaorlando.com
What This System Is For
- keep my calendars updated
- keep client and team visibility aligned
- publish availability through multiple surfaces
- enable others to schedule my time without guesswork
- make commitments visible to the other systems that depend on them
How The Calendar Architecture Works
The calendar system has multiple visibility layers rather than one single calendar for every audience.
- I keep full-edit source calendars for my own day-to-day use across Google and O365.
- There are shared views for external groups I do not control, such as clients or prospective collaborators.
- There is a merged internal visibility layer for operations use.
- There is a public availability layer that hides unnecessary detail.
- There is a booking surface for people who need to request time directly.
- There is API and downstream access for tools such as Slack and other automation.
Implementation Notes
The current setup uses CalendarBridge to copy events one way from source calendars into a merged destination calendar. That preserves a unified view of time without forcing every system to share the same source calendar directly.
That merged calendar can then support different downstream surfaces:
- internal read-only visibility
- public no-details availability
- bookable scheduling
- integrations that need to know whether I am in a meeting or available
Changes to source calendars propagate quickly to the merged view, which lets the public booking and visibility layers stay current without becoming the source of truth themselves.
I also created a static page for calendar.mikeaorlando.com hosted on S3 and served through CloudFront. That page makes availability easier to understand for people who do not want to work directly inside Google Calendar.