Events calendar page

[madolson]

Description

Created a very simple JS driven calendar for the event page and make the events more YAML driven. There are two types of events: Valkey first party (hosted by LF) and Third Party events. Still missing all of the "Valkey was here" events, easy to add as a followup, but wanted to get alignment here first.

I'm not sold on the data layout, maybe there is a better strategy, but just started with this.

AI notice: Most of the CSS and Javascript was AI generated by Claude but I looked over and fixed the stuff I understood.

** New image**

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

[jaduffy]

Can we at a minimum link to this event calendar from the front page so it’s discoverable?

[stockholmux]

I could pick apart this Javascript all day long but I will refrain: there are a ton of little non-ideal bits and gotchas but there is lots of worse JS in the wild (and this isn't, like, a critical thing). The parseInt w/o radix is a real bug though, you should use Number instead.

My main issue here is that you're creating two different sources for the events (and maintaining long YAML in git is annoying with merge conflicts, IMHO).

Instead of a YAML file, we could have each event as a .md file in /content/events with all the metadata in the front matter (which can either be TOML or YAML or JSON, Zola doesn't care). For third party events., render is just set to false so it won't create a page.

Then, you just loop over section.pages as in the current version to create your events collection.

One other note: creating the calendar via JS is a little suboptimal. The SEO value is definitely reduced (although this isn't as deadly as it was a few years back).

[madolson]

Instead of a YAML file, we could have each event as a .md file in /content/events with all the metadata in the front matter (which can either be TOML or YAML or JSON, Zola doesn't care). For third party events., render is just set to false so it won't create a page.

This was intentional, because some events don't really deserve a md file. It seems dumb to make a dummy page for sake of making a dummy page. I'd rather invert it and have the yaml build out the events markdown if we think it's so important to not duplicate.

[stockholmux]

This was intentional, because some events don't really deserve a md file. It seems dumb to make a dummy page for sake of making a dummy page.

I think you misunderstand, setting render to false won't create a page, just an entry in Zola index that we can run through a section loop. There is very little difference, IMHO, in having one big yaml file vs a bunch of individual ones except it becomes easier to manage and there is a single instruction for people. 1 markdown file per event.

[madolson]

I think you misunderstand, setting render to false won't create a page, just an entry in Zola index that we can run through a section loop. There is very little difference, IMHO, in having one big yaml file vs a bunch of individual ones except it becomes easier to manage and there is a single instruction for people. 1 markdown file per event.

This doesn't work exactly the way you think it does, but I'll see what I can do.

[madolson]

I think you misunderstand, setting render to false won't create a page, just an entry in Zola index that we can run through a section loop. There is very little difference, IMHO, in having one big yaml file vs a bunch of individual ones except it becomes easier to manage and there is a single instruction for people. 1 markdown file per event.

So Render = false does not let them show up in section pages. The simple solution was just to redirect it to the remote URL, which we have. Maybe still useful if we want to track the line with google analytics?

[rlunar]

I'm OK with the current version as it is; we still need to figure out the following items in the next iteration:

• Multi-day events: KubeCon, Open Source Summit, re:Invent!
• Landing page for days that have multiple events
• Naming conventions

[madolson]

@stockholmux ping

[stockholmux]

Overall this is fine. If you're going to do a meta refresh, might as well not render the entire page.

I toyed around with the render= false bit and indeed, it didn't act as I thought it would. Most other SSG (Hugo, Jekyll) have a way to let a page exist in the parent loops but not render HTML. Weird.

I suspect that there is a way to do it but we're just missing it. Nonetheless, the way it is done right now won't do heinous harm, just maybe a little inefficient.

[madolson]

@stockholmux Done, gtg?

[stockholmux]