Considerations for the current Event content type

[mandclu]

As someone who has had a lot of conversations with site builders working with dates and times over the years, I thought I would share so initial reactions from the current Event content type in the Starshot prototype:

• a common requirement is a view that list upcoming events, typically ordered by start date (ascending). Often there is a companion display of past events, and a block display of the upcoming events. I would suggest that this be included in the recipe
• currently the date field is last in the form, even though it is the only required field, and often one of the most important data points for an event. I would suggest that the date field be first both in the form and the display
• personally I prefer to call the date field "When" to more explicitly communicate the relevance, but this is a very minor point
• the prototype currently uses the "default" Smart Date widget, even though for legacy reasons the Smart Date module actually defaults to a newer version, the Inline widget, designed to resemble popular calendar software
• currently the date field provides no default value, which means that all of the start date and time pieces need to be manually provided a value, even if zero. If the field was a Smart Date field instead of a datetime range field, it could use a "next hour" default, which often reduces the amount of input required and also aligns with how popular calendar software tends to work
• using a Smart Date field would also allow for managing timezones and/or recurring dates with just a few configuration changes (particularly if the field allowed unlimited values by default, though the empty field set can be hidden on first load)

I'd be happy to provide a PR for any or all of the suggestions above, but thought I would gauge the level of interest/agreement first