The Slow Collapse of MkDocs
fpgmaas.com
fpgmaas.com
The original author (who is also the leading maintainer of httpx, another huge package) started a crusade against male-dominated spaces such as... Github issues and discussions.
>So… sharing the source isn’t the problem here. The issue is the GitHub working environment. I’m not interested in the smokey boys-only-club atmosphere, it feels starkly unprofessional.
>We’re not having any more conversation in all-male online spaces. Not happening.
It looks like 3 weeks ago a similar change happened in httpx - github discussions were disabled. https://github.com/encode/httpx/discussions/3784
>I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value.
As a mkdocs user and a httpx user I find that concerning - I hope personal issues won't harm those projects long term (well it looks like mkdocs is already dead).
Those were the only requirements that made me settle with Material MkDocs, and that are driving me towards the fork MaterialX. The comparison the latter makes with Zensical [0] is _exactly_ how I feel it (again, as a non-technical person).
[0] https://github.com/jaywhj/mkdocs-materialx#differences-from-...
That said, I do think the linked comparison may be a bit misleading. As far as I can tell, MaterialX is still largely based on the Material for MkDocs codebase with mostly some UI changes, several of which the author has taken from Zensical.
I’ve been looking at Zensical https://zensical.org/ as a replacement, but I couldn’t fully reason why they went off and did their own thing. I wasn’t sure if it was a money grab or what their motivation was.
This article provided the context I needed to understand the why. We’re going to definitely give them a shot.
[1] https://docs.google.com/spreadsheets/d/18Riw9yTx6Scix3xv0wiV...