Closed maelle closed 5 years ago
In the above each event = a md consisting of YAML only. It gets translated to html and ical.
Calendar at www.elm-conf.us/talks/index.ics (well it used to be there!)
My current favorite solution (still not sure):
---
title: "Afternoon Break"
date: "2017-06-05T13:25:00Z"
location: St. Louis Union Station
slot:
start: "2017-09-28T14:30:00-06:00"
end: "2017-09-28T15:00:00-06:00"
---
We'd have more fields like URL, person as name + URL like authors of blog posts, possibly a description.
not linking the events pages from anywhere (possibly not building them?). to exclude events from the sitemap (they'd be needed to build the table and ics but shouldn't be accessible as pages for users of the website) maybe https://gohugo.io/templates/sitemap-template/
creating a partial that creates a table from the events (a list of pages, with no link to the pages -- the list of things aspect is the same as the archive/ page, and you can format it like you want in this case like a table). Call that partial from posts and the community page. this partial would use date variables (system data for the community page, post date in YAML for posts) to filter events for that table.
have a list.ics layout for events that'd allow having a calendar feed, linked from a sentence in the partial i.e. under the table "subscribe to our event feed blabla".
and old events would be translated to md with some R script of mine.
(possibly retrieving the history of the .js, fear not @stefaniebutland)
Now I think there's a benefit to having a page per event which is having it nicely formatted with all details + link to the calendar event.
If comm calls get tags, tags can be added with blogyaml
!
No need for ICS, and calendar PR opened.
Edited the history of this thread.