Saw this and thought it was important, since our docs are based on Material for MkDocs.
This one line jumped out at me, which tells me that the future of Material for MkDocs is questionable:
We also mentioned in our update on our foundational work that MkDocs must be considered a supply chain risk, since it’s unmaintained since August 2024. It has seen no releases in over a year and is accumulating unresolved issues and pull requests. These developments have forced us to cut our ties to MkDocs as a dependency.
Oh interesting . This could either be a good or bad thing for Athena as it makes use of the Crystal plugin for its API docs, along with some other customizations. Thanks for posting this! I shall read more up on it and report back my findings for posterity.
EDIT: Yea, I can install and serve things, but it just doesn’t work because it seems they don’t currently support their projects plugin among others. So likely will just have to wait until they get to subprojects on their roadmap.
We want to be transparent about the risks of staying on Material for MkDocs. With MkDocs unmaintained and facing fundamental supply chain concerns, we cannot guarantee Material for MkDocs will continue working reliably in the future. We’re aware that transitioning takes time, which is why we commit to support it at least for the next 12 months, fixing critical bugs and security vulnerabilities as needed, but the path forward is with Zensical.
So, yeah, they intend to drop Material for MkDocs.
I have like 95% of a replacement for mkdocs spread between different projects. Just wondering if there is somewhere a historical discussion of what is needed for crystal’s usage?
. This could either be a good or bad thing for Athena as it makes use of the Crystal plugin for its API docs, along with some other customizations. Thanks for posting this! I shall read more up on it and report back my findings for posterity.
Material for MkDocs is now in maintenance mode