{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig5pbkbzxd7wwggk7lf72ferpmgx6mnis7r3xvjmgfefiohgz665u",
    "uri": "at://did:plc:cp5oragmzw4fq7opnsbanqnq/app.bsky.feed.post/3movst5y35bq2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiahdycbjtdj2jjsxusqfgkx2gnszkwp5lwcuxs3cuuatlpherpqvi"
    },
    "mimeType": "image/svg+xml",
    "size": 31981
  },
  "description": "How to get your site's calendar populated and looking great!",
  "path": "/blog/calendar-caddie-part-1-adding-a-source/",
  "publishedAt": "2026-06-22T21:19:13.000Z",
  "site": "https://www.spectralwebservices.com",
  "tags": [
    "https://tools.spectralwebservices.com"
  ],
  "textContent": "Want to get started with Calendar Caddie? Head on over to https://tools.spectralwebservices.com .\n\n### How do I (the curator) get sources onto my calendar?\n\n  * Our goal is to make calendar generation automatic. We want to read sources of community events and get them onto your calendar with minimal or no intervention on your part, _once configured_. But to do that, we have to find the sources!\n  * You hopefully already know (or can do some research) to find out who puts on events in your area that you're interested in including.\n  * Once you have some momentum and a well-filled calendar, remaining sources will (hopefully) start asking _you_ to include them. Thus, our initial goal is to get the calendar looking like a useful resource, to encourage additional sources to want to be included and to be cooperative in making their events accessible to Caddie, if they are not currently.\n  * Some sources may be initially difficult or impossible. Start with the easy ones.\n\n\n\n## Adding a source\n\nUse the auto tool! With luck, it will identify the source for you!\n\n### What if the auto-tool can't identify and configure my source?\n\n  * Sometimes, the human-visible calendar is not the best source (i.e. if a human built it by hand as unformatted – but pretty – text). If it's a high-value and high volume source, a little internet research to see where else their events appear may be worthwhile. Are the events also listed somewhere else? For example, are these events also in Ticketmaster, or a Meetup group, or Eventbrite?\n  * If it's a low volume source, is it worth just adding their events by hand? If a source has two events per year, maybe you just add them using the event submission form, or maybe you maintain a Google calendar where you add any events you want to add, and you add that Google calendar as a source. (Adding events to Google calendar may be faster than submitting them via the form.)\n  * Ask the source!\n    * It's possible that they actually do have a readable feed that just isn't obvious or we just haven't found.\n    * Or it's possible that whoever takes care of their website can turn on a readable feed with a couple clicks. Ask for an ICS feed.\n  * If someone is regularly submitting events via the form, consider some outreach. It would be faster for them and MUCH faster for you if they put their events on a calendar and shared that calendar link with you. [This assumes you don't want to pre-approve their events.]\n  * Events that fail the auto-tool can be submitted for further investigation. My priority will be sources with many events (because a single annual event can just be added manually) and sources that are going to be generally useful (i.e. a common CMS/calendar system used by many organizations that will help many curators).\n\n\n\n### What happens after I add a source?\n\nYou can trigger a refresh on your source. Changes are typically live in 2-10 minutes, depending on source type. Sources are checked for new and updated events once daily.\n\n(more to come!)",
  "title": "Calendar Caddie part 1 (adding a source)",
  "updatedAt": "2026-06-22T21:19:13.704Z"
}