Problem/Motivation
Umami is here to show off the cool things you can do with core.
Events are an incredibly common need in websites of all sorts.
Currently, core's datetime handling is all kinds of broken (says someone who's unofficially helping to co-maintain it -- no offense meant to anyone -- Dates Are Hard(tm)).
To "eat our own dogfood" on this, let's try to have an event listing in Umami.
That'll help us realize how bad our datetime handling is, and give focus and purpose for fixing those limitations.
Beyond #bugsmash and #dogfood, a food magazine might want to offer readers info about various events, both IRL and online:
- Cooking classes.
- "Meet the author" or "Meet the chef" events.
- Food/drink festivals
- ...
Proposed resolution
- Add an 'Event' node type.
- Have an 'Events' menu item that leads to an event listing/view for end users.
- Add something (another view) for admins to review pending events, moderate, manage, etc.
- Fix core's date handling enough to make this actually usable and slick. ;)
Remaining tasks
- Start trying to do this with current core.
- Identify limitations and link them to this plan as related issues.
- Smash the bugs.
- Add the features.
- Circle back to Umami and make it work.
- Reviews / refinements / improvements.
- RTBC.
- Commit.
- Feast on large pile of home-grown dogfood! ;)
User interface changes
New 'Events' menu item and 'Event' node type in Umami demo profile. Details TBD.
API changes
None directly.
Data model changes
Not sure how this applies to a profile issue. New node type, fields, etc.
Release notes snippet
TBD.
Comments
Comment #2
dwwClarifying a few views I think this would need.
Comment #3
mandclu commentedI'm notoriously opinionated about datetime and some other admin UI issues, so I'll chime in a few thoughts, based on what I would consider best practices:
I will also add that I created the Smart Date Starter Kit as a way to package together what I consider best practices as an easy-to-manage configuration for events. If we want a contrib space to hammer out some ideas on what we think a "best of breed" solution could look like, that (or something similar) could work as a place collaborate on ideas and make them tangible before getting into the work of moving the final changes into core.
Comment #4
markconroy commentedI like this idea (speaking as a maintainer of Umami).
I don't know enough about dates/date fields/date range/etc to be a great help (except I know how frustrating it is to try set up event content types as a site builder.
The only item of issue I have here is that after a while all the events will be out of date as time passes, so we need to figure out some way to put (at least some of the events in the future). Maybe part of the migration script for installing Umami can set the dates for specific events as one one, one week, one month, two months, etc from "now".
Comment #5
mandclu commentedGreat point about being able to create event with an offset from the time of installation. Maybe this script could also be used to manually "refresh" event date so they're recent or upcoming rather than in the distant past.
Comment #11
markconroy commentedI wonder should we mark this issue as 'Postponed' for two reasons:
1. It doesn't look like any one has worked on it since it was created 2 years ago, and
2. We don't have an events content type in Umami so it would be impossible to create an events listing.
Comment #12
dww1. True. ;) no one wants to put their hand in the blender on this one.
2. The intention of this issue would be to add events and an event listing. That’s not a reason to postpone this issue. No one would agree to an issue to “add events to Umami” if there was no listing of them or way to browse them. This is the issue for both (if we’re ever going to try eating our own dog food on this topic). 😅
Anyway, I’m not sure postpones makes sense. It’s not blocked on anything, other than time and interest.
Thanks,
-Derek
Comment #13
markconroy commentedThat sounds fair @dww.
I'll leave it as is for now so and if someone feels like firing up the blender later, we'll be waiting with open arms (and bandages).