Commit 68ad34d2 authored by Jamie Tanna's avatar Jamie Tanna

Add support for calendar events for /events/

Plus an announcement post.

Closes #481.
parent 873c72e9
......@@ -40,6 +40,7 @@ enableGitInfo = true
home = ["HTML", "RSS", "jsonFeed"]
section = ["HTML", "Calendar"]
title: "Adding iCalendar Feeds for Events in Hugo"
description: "Using Hugo's custom output formats to automagically create an iCalendar feed for events."
- announcement
- announcement
- events
- hugo
license_code: Apache-2.0
license_prose: CC-BY-NC-SA-4.0
date: 2019-05-22T12:15:03+0100
slug: "ical-events-hugo"
- text: IndieNews
- text: /en/indieweb
While running [Homebrew Website Club Nottingham](/events/homebrew-website-club-nottingham/), I've been manually reminding the group of when the next event is.
However, this hasn't been the best because if I'm not on top of it, it means others won't see the events being posted.
I'd created an [h-feed]({{< ref "2019-05-12-implementing-hfeed-making-content-discoverable" >}}) for the events, but as not everyone has support for an [Indie reader](, it doesn't quite make sense.
So I posted in the Slack channel we're using to talk about it, and a couple of the comments were "don't use" and "what about calendar invites".
However, being the super lazy person I am, I didn't want to have to create a calendar entry _each and every event_ so I've now created an iCalendar feed, which is linked on each of the events pages to let others subscribe to that and have it handily appear in your calendar app of choice.
This was fairly straightforward easy with Hugo, as it already supports rendering iCalendar entries. To get it fully working, I had to create the ICS file in `layouts/events/section.ics`, and then hook it in correctly in my `config.toml`:
-section = ["HTML", "RSS"]
+section = ["HTML", "RSS", "Calendar"]
Subproject commit e7df6c85f829e0d26e02cef23917ccd1fe86ab79
Subproject commit ed1271f65fbd2d6f41afae928ee8c9452ae2984c
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment