What you see below is an iteration of the new community calendar we’re working on. It starts with the premise laid out by Jon Udell in the Read Me documentation of the Github repository from which this calendar instance is forked:

“Public events are trapped in information silos. The library posts to their website, the YMCA uses Google Calendar, the theater uses Eventbrite, Meetup groups have their own pages. Anyone wanting to know "what's happening this weekend?" must check a dozen different sites.

Existing local aggregators typically expect event producers to "submit" events via a web form. This means producers must submit to several aggregators to reach their audience — tedious and error-prone. Worse, if event details change, producers must update each aggregator separately.

This project takes a different approach: event producers are the authoritative sources for their own events. They publish once to their own calendar, and individuals and aggregators pull from those sources. When details change, the change propagates automatically. This is how RSS feeds work for blogs,iCalendar can do the same for events.

The gold standard is iCalendar (ICS) feeds — a format that machines can read, merge, and republish. If you're an event producer and your platform can publish an ICS feed, that's great. But ICS isn't the only way. The real requirement is to embrace the open web. A clean HTML page with well-structured event data works. What doesn't work: events locked in Facebook or behind login walls.”

Please don’t assume everything about this display reflects an intentional choice about something. And not everything is going to necessarily work right now. But if you see something you’d definitely like us to preserve, or something you really really hate, and would like the option to make it go away, let me know: dave@bsquarebulletin.com