mkdocs has slowly collapsed from a maintenance perspective over the last 2 years:
https://fpgmaas.com/blog/collapse-of-mkdocs/
This means that:
mkdocs v1.x will likely receive no further support
mkdocs v2.x will break everything
Additionally, mkdocs-material is also in maintenance mode due to the above.
There are alternatives that have sprung up:
properdocs to replace mkdocs from the last active maintainter of mkdocs
mkdocs-materialx to replace mkdocs-material
Ultimately, these issues don't have to be handled yet, only when something breaks. However, IMO:
- We should be interoperable with these alternatives.
- We should prefer these alternatives.
- We should version limit
mkdocs to 1.6.1 and not accept anything newer, given the current state of the maintainership.
mkdocshas slowly collapsed from a maintenance perspective over the last 2 years:This means that:
mkdocsv1.x will likely receive no further supportmkdocsv2.x will break everythingAdditionally,
mkdocs-materialis also in maintenance mode due to the above.There are alternatives that have sprung up:
properdocsto replacemkdocsfrom the last active maintainter ofmkdocsmkdocs-materialxto replacemkdocs-materialUltimately, these issues don't have to be handled yet, only when something breaks. However, IMO:
mkdocsto1.6.1and not accept anything newer, given the current state of the maintainership.