Martin Donath

In the light of the latest MkDocs developments, we've updated our plugin section to outline how we plan to reach feature parity as quickly as possible, and how MkDocs plugins relate to @Zensical modules. zensical.org/compatibility/…

@sbarnea Thanks for your feedback. Theme extension is already on our roadmap! ☺️ We're currently focusing on support for the most popular plugins, as we see this as critical. If we see more interest for theming in Zensical Spark, we will prioritize it. github.com/zensical/backl…

@squidfunk I am looking forward for the ability to load theme customisations from python packages. This is a migration blocker, duplication is not acceptable across projects.

We've just released Zensical 0.0.25, which includes several improvements for authoring and user experience, as well as accessibility. We're also making good progress on the module system, so shouldn't be long ☺️ github.com/zensical/zensi…

@adamtwar On a last note: we're not forcing anyone to switch to Zensical. We are just trying to save millions of hours of work put into documentation projects used in and outside of organizations. Zensical is already much more compatible with MkDocs 1.x than MkDocs 2.0 will likely ever be.

@adamtwar Additionally, we're seeking to consolidate the functionality of several MkDocs plugins. For instance, there are 4-5 PDF plugins – we won't support all of them, but provide a unified way of creating PDFs. "Copying everything over" would mean to drag the baggage of MkDocs with us.

We've updated our MkDocs 2.0 analysis with the latest developments – the change in its contribution model, why we didn't fork, and a full timeline of events. squidfunk.github.io/mkdocs-materia…

@MatthewRideout 1. MkDocs 1.x is unmaintained, so we created Zensical, and put Material for MkDocs into maintenance mode. 2. Now, MkDocs 2.0 was announced, breaking your MkDocs 1.x projects. We're working on porting all functionality from the MkDocs ecosystem to Zensical. That takes time.

i just found out my mkdocs are being deprecated because material maintainers announced a push towards Zensical, but Zensical still in alpha, but material is still compatible with mkdocs 1, but mkdocs 1 is being deprecated, and material is not compatible with mkdocs 2 (which is in alpha and unstable) and I have no ability to follow along and am having codex switch it all to HUGO.

@sdelquin @zensical If you find a bug, please create an issue with a minimal reproduction like everybody else ☺️ Social media is not the right medium to report bugs.

Hi @squidfunk. Issue with @zensical. Sometimes (in production) equations don't render properly. I need to reload the page to see them rendered. Do you have any clue? 🤔 Check this out! #recursion" target="_blank" rel="nofollow noopener">aprendepython.es/core/modularit…

@muratkocerr I have no affiliation with RoseBot, never heard of it.

@squidfunk Hello I have a problem with RoseBot. Can we talk privately?

If the first version of the thing you release doesn't suck in one or the other way, while still demonstrating where you want to go with it, you shipped too late. 1/4 Thread ↓

4/4 We're working hard to allow everybody to switch from Material for MkDocs to Zensical as soon as possible, so you don't need to scrap your existing documentation projects and start from scratch to make it work with the upcoming MkDocs 2.0 update.

3/4 We're very thankful for everybody that has tested Zensical, maybe already migrated their sites, and uncovered the problems reported. Once the ZRX overhaul is complete and the module system is in closed preview, we'll start shipping support for all popular MkDocs plugins.

Great episode of Factually! Over the last 30 years, companies have shifted us to a computer-based society – "every work is email" [...] and now they're saying: "you don't use computer anymore, computer uses itself – it doesn't need you". open.spotify.com/episode/1zQnlZ…

@janaka_a It's easy to miss, but no license = all rights reserved by default. Legally, no one can use, modify, or redistribute the code, or even fork it. It's not Open Source in any meaningful sense until a license is added.

@squidfunk thanks for sharing your take in the post. very interesting that it's unlicensed at the moment.

A look at the upcoming changes in MkDocs 2.0 squidfunk.github.io/mkdocs-materia…

@banteg For reference: github.com/zensical/zensi…

@banteg Additionally, requiring sign-off to comply with the DCO + verified commits mitigates supply-chain risks, and only needs to be set up once. Moreover, I checked – we considered all of your ideas + merged your PR and did not turn down anything.

some open source projects think too much of themselves. this has happened several times in a row to me when tried to do high quality contributions to zensical and quarto. both were killed because i didn’t study their bureaucratic process enough. in case of zensical the maintainers gave some useful pointers and ultimately admitted my ideas were worth considering. still, they have an insanely strict and detailed contribution guidelines that far outweigh the volume of external contributors. the repo sees maybe a couple of issues per month, yet it’s run like a 100k employee company. in case of quarto i added cloudflare wrangler support. the codebase was in a pretty bad shape, but i took my time to figure out my way around poorly structured code. then my pr just sit there for a month. today it was closed because i didn’t follow the pr template exactly. i won’t reopen because this just insulting. it’s peak stupid. if you run an oss project, try to engage with the core of the ideas proposed or don’t accept contributions at all (also a valid position). don’t kill contributions with process nitpicks or overeager ci bots. don’t make people sign cla and whatever other meaningless acronyms.

@VedranMiletic Yup, we're working hard on making that happen, giving a new home to the tens of thousands of projects that depend on Material for MkDocs 🚀

@squidfunk Zensical looks like the way to go.