• Setup axe CI scripts
• provide hooks for customization / exclusion
• How do dependent repos pull in updates?

https://github.com/jekyll/jemoji

It's quite useful to run axe tests on all individual pages. However, there are two challenges:

• common errors are repeated across pages
• there's not a great summary of pass/fail results.

• Create a _base_config.yml which is basically the stuff you don't need to change
• Update _config to be only class-specific data.
• Consider whether per-semester configs should be separated?

All the tools have course calendars which are a PAIN to write.

One file per week as an authoring tool seems hard.

• the programming is easiest if every date is defined explicitly, but in classes with consistent schedules, that is hard.
• I, personally, prefer 1 file with all assignment dates
• each assignment needs:
  • release date
  • due date
  • content / spec link
  • submission link
  • probably number of points
  • This info is ideally not duplicated manually.
• How can we support the table-style calendar (CS10, 161, 188, others)?

Long Shot: Google Sheets / CSV sync?

Does it make sense to have the tool build a calendar file from a Google sheet?
If a sheet URL is shared via link, it's trivial to get/import a CSV. This means at build time (if desired) or locally (if the output is committed to the repo) we can generate a calendar from a format easier to write/update.

I'd like to extend this to be Berkeley-specific.

• Define berkeley brand color a CSS var
• Import berkeley fonts (How do we use Freight on the web?)
• Provide common class names for accessible color combos
• Provide hooks for DS / EECS / dept-level customizations

As of #20 , the github-pages gem has been removed from the Gemfile list of dependencies, which is good because this allows us to use custom plugins and plugins that are not whitelisted by the github-pages gem.

However this means we need to figure out how we are going to deploy the site without using the nice GitHub Pages/Jekyll integration. From preliminary research, it seems the way to do this is to check into git the _site directory and deploy the html generated there, but the repository needs to be configured as does the CI workflow (jekyll.yml may not work anymore).

Potential resources to look into:

• https://github.com/actions/jekyll-build-pages
• https://github.com/jeffreytse/jekyll-deploy-action
• https://www.yegor256.com/2014/06/24/jekyll-github-deploy.html
• https://jekyllrb.com/docs/plugins/installation/ (see "Plugins on GitHub Pages" section)

See commit message here: e1efa4e

See also #17

https://github.com/berkeley-eecs/berkeley-class-site/actions/runs/9575380090/job/26400293672

https://github.com/gjtorikian/jekyll-last-modified-at

We can update the theme but we should pull in specific functions from the just the docs repo:

• Devcontainer
• Updated CI flows
• README notes?

What is the best flow for a new semester?

• I strongly believe the deployment of each semester should be its own destination, even if the content is in a shared repo.
• How do we reconcile updates with this repo with customizations of each class's site?
• Should courses make a new repo each semester, copying the previous one?