A very surprising development indeed.

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).

As a non-technical person (not a dev, not a SWE, just a curious and selftaught tinkerer), I only want my _local_ markdown files to render as a beautiful - or at least, clean - webpage, to ease reading and sharing. No Github involved, no contorsionism needed. Just local md files. It should not be that complicated, at least that's what I felt.

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-...

Is there anybody in this story who ends up appearing as not a complete nutjob?

What are the best alternatives around? Not super keen to get locked into anything - don’t need crazy features. I’ll just set an agent migrating.

Imagine if oprypin is actually the original developer's sockpuppet account...