MkDocs v1, on which this project heavily relies is currently unmaintained mkdocs/mkdocs#4010.
The MkDocs project has shifted to a v2, a complete rewrite with a lot of fundamental changes, such as no longer having plugins https://github.com/encode/mkdocs.
Crucially for us is that Material for MkDocs is and will always be incompatible. https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/
So we will need to start looking at ways forward for eBPF Docs.
Material for MkDocs has created their own replacement Zensical https://squidfunk.github.io/mkdocs-material/blog/2025/11/05/zensical. Which is meant to be compatible with MkDocs v1, and improved. This might be a good option for us as its described to be a slot in replacement.
Ofcourse, another option is to go for the MkDocs v2 upgrade. This would mean needing to switch out everything Material for Mkdocs does for us currently (theming, icons, search, ect.). We also have some custom plugins which will no longer function and we would have to find alternatives for. This does not seem like an interesting approach.
Finally, we could look into some different engine or base for the docs. Including making something more purpose build. But this would likely be an even bigger time investment.
MkDocs v1, on which this project heavily relies is currently unmaintained mkdocs/mkdocs#4010.
The MkDocs project has shifted to a v2, a complete rewrite with a lot of fundamental changes, such as no longer having plugins https://github.com/encode/mkdocs.
Crucially for us is that Material for MkDocs is and will always be incompatible. https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/
So we will need to start looking at ways forward for eBPF Docs.
Material for MkDocs has created their own replacement Zensical https://squidfunk.github.io/mkdocs-material/blog/2025/11/05/zensical. Which is meant to be compatible with MkDocs v1, and improved. This might be a good option for us as its described to be a slot in replacement.
Ofcourse, another option is to go for the MkDocs v2 upgrade. This would mean needing to switch out everything Material for Mkdocs does for us currently (theming, icons, search, ect.). We also have some custom plugins which will no longer function and we would have to find alternatives for. This does not seem like an interesting approach.
Finally, we could look into some different engine or base for the docs. Including making something more purpose build. But this would likely be an even bigger time investment.