mike without mkdocs?

[JuroOravec]

Hi, are you thinking of refactoring mike to work also standalone, without mkdocs? Or is there maybe a similar library that does that?

[jimporter]

I am actually thinking about doing this, but nothing definite just yet. I've debated just how useful it would be to have a tool that only stores multiple versions of generated docs in a Git branch, or whether there's a better way to handle this these days. At the time I made this, it was built around the way Github Pages worked at the time, but with the various updates over the years, it's seemed more and more like a hack.

Fundamentally, I consider generated documentation to be a release artifact just like a tarball or a binary executable, and neither of those really belong in your Git repo. However, unlike those cases, multi-version documentation benefits from being able to cross-link to all the versions (via a version selector). This puts documentation in a weird middle ground where some coordination across versions is necessary, and which mike currently relies on Git for.

[JakeLarimore]

It seem like MkDocs has been shaky with its maintenance for a couple of years now. Material for MkDocs is also in maintenance mode, but that team is building their own static stie generator, zensical.

[JakeLarimore]

Oh I just saw they have mike in their Third-party plugins. Love to see it.