I just migrated my personal site from Mkdocs to Zensical.

My site: https://maulonobile.codeberg.page/
Learn more: https://zensical.org

#Zensical #MkDocs #Codeberg #OpenSource

MLNotes - MLNotes

maulonobile markdown notes

So, remember how all the cool kids dumped #Sphinx and went for the shiny #MkDocs thing? And then used the shiny Material for MkDocs theme?

Well, apparently MkDocs 1.x is dead, and MkDocs 2.0 is coming with no support for plugins, incompatible theming system, closed contribution model and unclear licensing.

So which hype train are the cool kids jumping to these days?

https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/

#Python

What MkDocs 2.0 means for your documentation projects - Material for MkDocs

MkDocs 2.0 is a ground-up rewrite of the documentation tool tens of thousands of projects rely on, introducing potentially significant breaking changes

Die Hölle friert zu: Nele Hirsch empfiehlt Publii

Mir gefällt die kompetente und unaufgeregte Art, mit der Nele Hirsch ihr eBildungslabor betreibt, und darin die Themen zur Bildung im digitalen Wandel behandelt. Lediglich eines hatte bei mir immer ein Stirnrunzeln erzeugt: Wenn es um die Frage »Publizieren im Web« ging, kannte sie bisher nur eine Lösung – ein selbstgehostetes WordPress. https://kantel.github.io/posts/2026030402_publii/ #StatischeSeiten #Publii #Webworking #Markdown #MkDocs

So sad to see the Mkdocs drama leading to a version 2 which smells lock-in by a lonely developer ignoring a community of thousands of users/contributors and the other part the @zensical team releasing a latest version of unmaintained Material for Mkdocs with a huge and unnecessary warning about mkdocs 2 incompatibility that feels somewhat FUD-driven.

#Mkdocs #MaterialForMkdocs #opensource

@squidfunk I used #MkDocs and #Material for a tiny project. Awesome resource: fast, elegant and easy to use (for a beginner like me).
@steff @sigmasternchen I'd do something like #MkDocs-Material likely just to have something useable and nice...

I've recently migrated a few (small) sites from #MkDocs (no longer maintained) to #Zensical, which went very smoothly.

It also motivated me to write a small Markdown extension for including source code for #Python functions, classes, methods, etc, similar to the `:pyobject:` option in reStructuredText's `literalinclude` directive:

https://includepy.readthedocs.io/en/latest/

(I'm aware of the snippets extension, which has many more features, but requires adding markers to the source files)

Get started - IncludePy

Include Python source code in Markdown files.

When installing dependencies, formatting code, linting it, type-checking it, and building docs with #Poetry or #PDM, #Black, #Flake8, #Mypy and #MkDocs would previously take from 2min to several more, it now takes less than 15 seconds for the whole thing, thanks to #uv, #Ruff, #ty and #Zensical.

This is for 5 #Python versions (3.10 to 3.15).

The DX got much better 🥰

I want to share my experiences with #DecapCMS [1]. I set up a lot of static pages with #CI&CD in the past. #mkdocs material, #jekyll, #hugo. You name it. The challenge was always to bring in people not comfortable with #Git/ #Gitlab.

DecapCMS elegantly solves this without much overhead: You place a `js`, `config.yml` and `index.html` in your static site. DecapCMS connects to your Gitlab (or #Github etc.) via Application integration. Tada. Your users can now edit your Markdown based static site directly in a #WYSIWYG-like editor, without ever touching Git, Gitlab or Github. The backend and CI&CD all remain the same.

I had this on the radar for a long time, but only now was able to test it. The integration and setup process was much simpler than I thought. No additional service required, just static files!

[1]: https://decapcms.org/

Material for MkDocs

Write your documentation in Markdown and create a professional static site in minutes – searchable, customizable, in 60+ languages, for all devices