Event URLs use of created date can be misleading

[kylewm]

This is exacerbated by the fact that I use /year/month/slug urls instead of the default /year/slug, but it would still be a problem if you posted an event in December 2016 for January 2017.

For example an HWC for next month has the URL https://kylewm.com/2016/04/sf-homebrew-website-club-14. The 04 (April) is misleading there since the event is actually in May. I approached this problem in my previous blogging platform by using the start date to generate the path (/2016/05/sf-homebrew-website-club). However since Known's slugs are unique IDs across all datetimes, it might be nice to include the date in the slug itself.

If we built the path from the parsed start time, and the slug included the start time, that would be better but a little bit redundant, e.g. /2016/05/sf-homebrew-website-club-2016-05-04

I'm considering sort of a radical option: serve events from /events/ ... which implies they are categorically different than the posts in the regular chronological stream.

I would build a slug by:

• try to parse start time with strtotime(); take the date component and append it to the title: /events/sf-homebrew-website-club-2016-05-04
• if parsing fails (e.g. for international formats); just take the whole start time string and append it to the title: /events/homebrew-website-club-04-mai-2016-17-30

[mapkyca]

Don't use events that much, but yep, it's annoying...