[Hugo Migration] Render each group as a "course" with proper semesters #34
Labels
🖥️ tool:hugo
The static site generator we use. https://gohugo.io/
🎆 feature-request
🔑 required
Tasks that **need** to be completed, ASAP.
💊 discussion
🚀 done
ship it!
Milestone
Just a note, when referring to
groups
...groups := {intelligence, core, data-science, supplementary}
Feature Request, for ucfai/ucfai.github.io (club website)
Description The current edition of the website uses Jekyll as the static site generator. Generally, given how finicky Ruby/Jekyll has been, in the past, coupled with the speed of Hugo – it makes sense to transition to Hugo. There's also a bomb template, call
hugo-academic
that integrates a tonne of intended feature additions to our current website.These include things like:
Needs
hugo-academic
export_notebook_as_post
function inautobot
to proper render and path the markdown render. (Note this in the comments, once we know this, [Hugo Migration] Metadata generation and directory restructuring #35 will cover the actual development.)<group>/<semester>/_index.md
should list all the<group>
's Coordinators for that<semester>
Initial Comments
hugo-academic
and play with it's directory structure / inject pages. Don't try making a full migration from the Jekyll site to Hugo.autobot
can do this!hugo-academic
's documentation oncourses
(e.g. rather than having
courses
laid out like in the documentation, we instead do...)Once this has completed, the following tasks will be migrated to ucfai/ucfai.github.io:
🔑 Required
) Combine the content buttons fromhugo-academic
'spaper/project
pages🔑 Required
) Ensure thathugo-academic
's "authors" properly link to the "course" pages.🍜 Nice to Have
) Setup "Documentation" structure for...autobot
The text was updated successfully, but these errors were encountered: