I can do the same thing with a Ghost theme, or even with code injection. The script that pulls calendar events just needs an API key and the link to the public calendar. But the problem with this approach is that it doesn't take advantage of the Ghost WYSIWYG editor (which is far nicer than the Blogger calendar event editor), events won't be searchable (because Ghost itself knows nothing about them), storing images for events is another layer of complexity, and so on. And maybe we do care about SEO for those faked-up event postings that a Google crawler won't see.
So... I thought I'd get clever and create a tighter linkage. I still wanted to use Google Calendar, to deal with Ghost not having custom data storage and because letting Google deal with some of the complexity seemed like a good idea.
Here was my idea going out the gate:
- Make a custom page on the ghost site that creates a stub-ish post with the event name, a custom_excerpt, a callout like block of text with time, location, and other calendar-type data, and some custom tags.
- Make a Google Calendar event with the same id as the Ghost post using all the same data. Set the description to the the custom_excerpt plus the link back to the Ghost post.
- After both creations are complete, redirect the user to the actual WYSIWYG editor for the new post, so they can add images, rich text, etc.
- Users can view event posts on Ghost just like any other post. Events are tagged, so it's easy to make an "upcoming events" stream, sort of like the "related posts" partial.
I pretty much got everything to proof-of-principle yesterday. Here's a short summary of what I think of this approach, at this point:
Experience for Site Visitors
Experience for "Event Editors"
- Event editors visit a custom page on the Ghost site and enter basic information about the event. Then they hit submit, which triggers calendar event creation and blog post creation.
- A standard OAuth pop-up asks event editors to choose a Google Account to use and then to grant the site permission. (I think the permissions request only happens once.) Unfortunately, "event editors" need to give the Ghost site permission to edit all their calendars. [There's no scope provided for editing just the one public calendar.]
- Event editors are redirected to the Ghost Admin WYSIWYG editor to finish their event post.
Needing to remember the URL for the event creator is a little clunky, since it isn't linked from the Ghost Admin pages.
- Create a Google Calendar and make it public. (~2 min)
- Give any other Google accounts that will edit it permissions (through the sharing feature). (~2 min)
- Grab the Calendar ID, copy it over to Ghost. (~2 min)
So now what?
Would you work through the setup headache for this sort of package? Or would it make more sense to just create and aggregate events from the Google Calendar, without trying to integrate with posts? What do you think? Poll below, and I'd love to hear your comments, too!