Create data file format for event

[mattstratton]

File should live in data/events and be named YEAR-CITY.yml

Should contain various items such as sponsors, twitter, etc, that will drive lower level pages

[mattstratton]

After fighting a bit with date comparison in hugo, and combined with #30, I think that another field needs to be added called status which can be set to "past" or "current".

Suggestions welcome as to what the values should be...

[mattstratton]

I'm also still bikeshedding with myself about TOML vs YAML and have gone back and forth at least twice in implementation on this :)

[m1keil]

from what I've stumbled (and saw you did as well), it's YEARCITY.yml/toml as - or _ are forbidden to use.

Regarding #30, can events without dates be in past?

Regarding yaml vs toml - I currently prefer yaml, since it looks a lot cleaner (no "[] chars). But I think we just need to create a yaml vs. toml file once we finalize the event data structure and decide on the better default.

[mattstratton]

Per @bridgetkromhout, events can be posted before dates are set. So events without dates will be future, not past.

Since Hugo doesn't like dates without times, etc, I've been using the "status" key in the event YAML file to determine past or current/future. This gives a bit more flexibility as to when events should be archived, etc.

[m1keil]

In that case, maybe instead of status: [past | current] we should switch it to future: [true | false] ?
My general logic is that you can figure out if events are past or future by event end date. And future keyword is a marker to handle special case of events without dates set yet.

I might over thinking it as well.

[mattstratton]

The problem with using the date to decide if it's a current or past event is that hugo doesn't like dates without times, and that's adding overhead to the person creating the file to add some faked up timestamp. But we might be able to code around it.

I think that you could also just assume if there is not date, it's a future event. Let's put it this way - if we can handle the datetime issue in datafiles from hugo, then this becomes a solved problem.

Reference: https://discuss.gohugo.io/t/trying-to-filter-data-files-based-upon-a-date-field/2114

[m1keil]

Great, I'll check that reference.

On Sun, Nov 22, 2015 at 6:05 PM, Matt Stratton notifications@github.com
wrote:

The problem with using the date to decide if it's a current or past event
is that hugo doesn't like dates without times, and that's adding overhead
to the person creating the file to add some faked up timestamp. But we
might be able to code around it.

I think that you could also just assume if there is not date, it's a
future event. Let's put it this way - if we can handle the datetime issue
in datafiles from hugo, then this becomes a solved problem.

Reference:
https://discuss.gohugo.io/t/trying-to-filter-data-files-based-upon-a-date-field/2114

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

[mattstratton]

I think this is basically resolved. Discussion can continue in #133