Open danerwilliams opened 4 years ago
Still trying to figure out what to do about this one. I'm tempted to play with switching to a static site generated by hugo
or something, since we can just keep the pages that need JS/non-static stuff separate from hugo
.
Going with something like hugo
would ensure a consistent look across the entire site, and using Markdown for that would mean that we could make some of the denser text a lot more structured. I need to look into whether we would be able to keep things like the Welcome Weekend profile cards while using hugo
.
I haven't been able to find much about non-static Markdown rendering (searching tends to just show me static site generators). I'll dig in more to see what I can find, but I'm concerned about performance with any non-trivial rendering. We might be able to use pandoc
or something at build time to generate it, but, at that point, I feel like we've almost reinvented the static site generator wheel.
Instead of html files for new pages, render html files from markdown or yaml (like in a hugo templated site)