Mostly posting here for posterity, @causallycausal and @ionlights have already finished most of this.

Tasks:

• (🔑Required) Test present markdown renderings on ucfai.org in hugo-academic's Documentation structure
• (🔑Required) Added on 01/07 Markdown is needed for ToC to work, however pygments doesn't work unless code is rendered in HTML. _This mandated changes to autobot to combine the rendering of Markdown and HTML (in specific sections).
• (🔑Required) Extract front-matter that needs to be filled out for autobot, place this in autobot/templates/notebooks/hugo-front-matter.html.j2. The corresponding places to make edits for this in autobot are here: https://github.com/ucfai/bot/blob/836879d680805c5a86de505666011c175fba39a5/autobot/utils/ucfai_exporter.py#L70
  There's some string concatenation that needs to be done, but otherwise, we should be able to use the FilesWriter that's already present.

this is a test, will be deleted asap

The Documentation Menus from hugo-academic are pretty powerful and configurable, however we need to strike a balance of "ease of navigation" and "ease of understanding/consumption."

Tasks:

• (🔑Required) Develop a better model of how the navigation structure works and how hugo-academic figures out which set of menus to use. Take notes here.
• (🔑Required) Decide on a navigation structure, this should make it's way into the templates we end up using.

Note on Tasks: While these are ultimately going to be the autobot, we need to first design these templates and see how they look on the website itself before extracting the template content into autobot.

Every group should have a programmatic setup, which is run during semester-setup

Tasks:

• (🔑Required) Display group meeting date, time, and room.
• (🔑Required) Display group's Coordinators (this should be based on info in their author page).
• (🔑Required) Display an abbreviated syllabus (should be title, banner image, and a summary).

Use the above information to design the necessary front-matter that we can extract and to determine the needed changes to HTML layout files.

• (🔑Required) Extract Jinja2 template for the group setup. This should be in autobot/templates/seed/website/group.md.j2 but render to groups/<group>/<semester>/_index.md.
  • This should be done both during semester-setup and semester-upkeep, as we may bring on Coordinators during the semester.
• (🔑Required) Fill out as much info as possible from the syllabus.yml and overhead.yml files. (This should also be Jinja2 ready.)

Note on Tasks: While these are ultimately going to be the autobot, we need to first design these templates and see how they look on the website itself before extracting the template content into autobot.

Tasks:

• (🔑Required) Decide on the navigation elements we should have and need.
• (🔑Required) On page scroll, the navigation should transition to the dark grey that's used elsewhere on the site (especially on mobile).
• (🔑Required) Update navigation element highlights, based on page we're on (including if in sub-menus, e.g. "Groups > Core" – groups should be highlighted).

Each Coordinator should have a profile on the website to document their contributions to the club.

Tasks:

• (🔑Required) Take the known Coordinators and add them to content/authors/ by their GitHub username (that is, create folders for them)
  • This should be done both during semester-setup and semester-upkeep, as we may bring on Coordinators during the semester.
• (🔑Required) Copy a Jinja2 template _index.md for each author and fill it out with as much info as possible (this should be done when they're added, only – to avoid overwriting).

Order in the title is arbitrary.

We need to have links out of the notebook onto the rest of the web where we have content. This should also be done, but needs to have its generalization tested.

Tasks

• (🔑Required) Add buttons for each platform with helpful icons and text.
• (🔑Required) Blocked on 01/07: Guarantee that autobot will make the appropriate translations from the syllabus.yml to each page.
• (🍜 Nice to have) Potentially re-color the buttons to match the brand identity of each platform? This might help with visual grepping, just like the icons.

Use the colors specified here: https://brandcolors.net/