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

Creator of Zensical here! Would you mind sharing a bit more detail on why you feel the comparison is on point? One of our core goals with Zensical is to simplify things – not add complexity. We’re also working toward making it an almost 100% drop-in replacement for Material and the broader MkDocs ecosystem, so I’d be especially interested in understanding what feels more complicated from your perspective. I’d appreciate any specifics on where we can improve.

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.