Kill off Hugo site for Training?

stevepiercy · August 23, 2022, 8:45am

First, I am NOT talking about the current Trainings documentation and its repo:

I am talking about this Hugo site, which has no path prefix of 5, and its repo:

There are several issues with this site and project.

No one keeps its meta navigation and doormat in synch with plone.org.
It has two other pages that are redundant to content in the Training documentation itself.
Its home page content is abridged compared to what is comprehensive on the Trainings home page at Plone Training — Plone Training 2022 documentation
Only a few trainers updated their bios since the site was created 6 years ago, preferring instead to put their information in the training itself or on ploneconf.org where it gets considerably more visibility.
No analytics.

I think there were good intentions for this site, but it's now a maintenance burden and should be archived. If we need a landing page, then we can use plone.org/training as the URL for this content.

Archival of the Hugo site would also free up the root of the site to always be the most current Trainings available, without the path prefix of the Plone version 5 (which should be 6 by now, but that's another issue).

jensens · August 23, 2022, 10:54am

+1

pbauer · August 24, 2022, 1:47pm

+1
I'm sure we've already discussed and decided this. Just use index and drop the 5.

stevepiercy · August 28, 2022, 9:16pm

To close the loop on this, here's a todo list, in order of operations. Please add or correct anything I might have overlooked. I've done what I have permission to do so far. Who can help with things I cannot do?

Create a new page Trainings — Plone: Enterprise Level CMS - Free and OpenSource - Community Driven - Secure.
Review, revise, and publish Trainings — Plone: Enterprise Level CMS - Free and OpenSource - Community Driven - Secure. This item needs someone with permission to do so. Feedback appreciated.
~~Merge PR Link to new Training page by stevepiercy · Pull Request #24 · plone/ploneorg.theme · GitHub and deploy.~~
Archive trainings from PloneConf 2022 on the main branch with a new tag for every year, such as 2022. This will also become an annual maintenance task about two months after each PloneConf. This will allow updates to continue to be made to main for a period after PloneConf and have them automatically deployed.
~~Server configuration: set redirect of path from 5 to 2021.~~
Server configuration: set default server path for trainings from 5 to root.
Update GitHub workflows for Trainings to push to the proper server location.
Revise links on Trainings — Plone: Enterprise Level CMS - Free and OpenSource - Community Driven - Secure to point to root path instead of 5.
Update readme of training.plone.org for archival and set as read-only.