Our Continuation of MkDocs
serhack_
45 points
16 comments
May 06, 2026
Related Discussions
Found 5 related stories in 83.9ms across 8,303 title embeddings via pgvector HNSW
- The Slow Collapse of MkDocs nogajun · 11 pts · March 22, 2026 · 67% similar
- The Slow Collapse of MkDocs zdw · 21 pts · March 22, 2026 · 67% similar
- Show HN: Continual Learning with .md wenhan_zhou · 23 pts · April 13, 2026 · 53% similar
- Why are we still using Markdown? veqq · 84 pts · April 03, 2026 · 49% similar
- Show HN: MDV – a Markdown superset for docs, dashboards, and slides with data drasim · 105 pts · April 18, 2026 · 48% similar
Discussion Highlights (6 comments)
yuppiepuppie
Did something change? cause this was published back in March.
kylebarron
See recent discussion in [0] [0]: https://news.ycombinator.com/item?id=47482185
kstrauser
Two open source dramas in one week? Get the popcorn. From one of the links[0]: > I do not see him as qualified to keep this project maintainership and if I had the choice, would I remove him. …where “him” is Tom Christie, aka lovelydinosaur, the original author from what I can tell, and the copyright holder from the license file. I don’t know what’s going on, but if someone contributing to one of my projects, that I wrote, started a public conversation about how to remove me, my public response might appear as that person disappearing from the project. Sure, feel free to follow the license and fork the project. Make it clear that it’s a fork, though. It feels misleading to describe it as a continuation of the existing project. [0] https://github.com/mkdocs/mkdocs/discussions/4088
esafak
This is a timely discussion for me. I've been dealing with several open source packages that aren't moving nearly as fast I need to get work done. I fork them, creating feature branches to upstream and merge them into a vendored dev branch I can use myself. But when I can push a dozen PRs a day and the maintainers barely merge a few a month, the math does not add up. I bet many AI-powered developers are facing this problem. I tested the waters with some PRs and regretfully came to the conclusion that I have to work on my fork. Also, this MkDocs maintainer sounds crazy. Nobody is discouraging women from contributing.
athorax
Zensical has been a solid replacement for us so far. In general everything "just works" out of the box and is way quicker to build/reload. It is still in fairly early stages, but is actively being worked on https://zensical.org/spark/proposals/zap-005-navigation-auth... I hope they are able to monetize in a way the keeps the core project open while making it a sustainable venture going forward.
slipfold
This is probably a relevant exploration of the issues: https://fpgmaas.com/blog/collapse-of-mkdocs/