I like it overall. I'm a little concerned about the backend. Would it
work better to have "outageStarts" and "outageEnds" timestamps in the
file for each outage so that the person handling it doesn't have to
both with moving the files into the right directory?
At the moment the date metadata item time stamp is essentially the outagestart. This field is required by pelican, and is used for sorting etc.
Making it automatically recategorize when the time ticks over is kind of not possible. As the site would have to be regenerated anyway.
Or maybe just use
labels instead (I'm not familiar enough with Pelican to know how
flexible it would be in that regard).
Ongoing, proposed and resolved are just categories in a blog type context. By default, pelican lets a user set the category in the md file metadata, however I set up this example to use the directories, to make it simpler to edit an ongoing or proposed entry. Over time there are going to be a lot of resolved entries to sift through to find the one proposed or ongoing one.
Cheers
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure