This rebuilds the site keeping the existing appearance but building from Jekyll with a custom theme and Markdown-based content. Jekyll is the static site builder that powers GitHub Pages. For me, the main selling point is that content can be in Markdown. Though, in this case I recognize the existing page almost has enough going on sticking with HTML would have been more appropriate.
This is extreme overkill and adds complexity if nothing much ever happens on the site; however, having Jekyll will be useful if anyone wants to do more with the site.
I probably did not make all the right decisions how what should utilize what Jekyll features, so experience may show some things here should change.
This rebuilds the site keeping the existing appearance but building from Jekyll with a custom theme and Markdown-based content. Jekyll is the static site builder that powers GitHub Pages. For me, the main selling point is that content can be in Markdown. Though, in this case I recognize the existing page almost has enough going on sticking with HTML would have been more appropriate.
This is extreme overkill and adds complexity if nothing much ever happens on the site; however, having Jekyll will be useful if anyone wants to do more with the site.
I probably did not make all the right decisions how what should utilize what Jekyll features, so experience may show some things here should change.