The State of (Material) MkDocs

[olivia-banks]

I was reading a HN Thread earlier, and saw that the Material MkDocs people (who's theme we're using) have recently spun off into their own project, because MkDocs has become unmaintained and they were running up against the limits of what was possible. Are we concerned that our nascent documentation system is built on two now unmaintained technologies?

[olivia-banks]

Perhaps this could be interesting?

[gvegayon]

Ugh, just when I was starting to get attached to it. Sure, let's migrate whenever we can. Perhaps we can ask copilot to give it a go. What do you recommend?

[olivia-banks]

Jupyter might be interesting, if only to use EpiworldPy to generate figures behind the scenes for example Epiworld code.

I know that the new project by the MkDocs Material people is supposed to be pretty backwards compatible, so that might be looking into if it's easy.

[gvegayon]

I don't like jupyter + GitHub 🫢! In a different project, we used quarto https://github.com/CDCgov/pyrenew

[olivia-banks]

Can we set multiple agents on different tasks and compare the new Material project and Quarto? Or is that not a possible?

[gvegayon]

I think we would need to create two separate issues to do that.