Statische Seiten mit MkDocs (Material)

Als ich vor etwa einem Jahr meinen Rechnerumzug organisierte, stolperte ich auch wieder eher zufällig über MkDocs, einen schnellen und freien (BSD-Lizenz), in Python geschriebenen, Markdown-basierten Generator für statische Seiten, der allem für die Dokumentation von Software-Projekten entwickelt worden war. https://kantel.github.io/posts/2025062101_mkdocs/ #MkDocs #Markdown #StatischeSeiten #Webworking

クラスメソッドによる2025年OSS支援（5件）を紹介します
https://dev.classmethod.jp/articles/oss-sponser-2025/

#dev_classmethod #OSS #runn #Hono #MkDocs #fastapi

and there it is. 11-month blocker defeated.

#MkDocs #MkDocsMaterial #Surfhosting

What is the de facto standard for creating static #documentation websites for #OpenSource libraries? So far I've found #Docusaurus and #MkDocs, which both are popular options. I like that MkDocs' sources are #Markdown files. What else should I consider? Any suggestions?

#AskFedi #docs

Tried to use (& like) #quarto for websites (docs) for quite some time now, but I finally give up.

Too slow, bloat, dark-mode not prod-ready, site flashing and reordering on page load, etc.
Building and rendering in CI is another topic which does not work "nicely" (no slim/Alpine images, deno memory issues).

#mkdocs or #starlight (Astro) are way more mature (and slim) in every aspect. (I've started checking them out after I got mad with quarto).

#Documentation

Is there a way I could have folks collaborate on a folder of markdown docs, (like in interactive mode where multiple people can type at the same time), and then some smarty pants in the group could do a pull request to a git repo.

I’m wanting both of these things, for a multisite multi group collaborative documentation project.

Need the git workflow and would like to be able to have technical and non-technical collaborators in the mix.

#Markdown #Documentation #DigitalGarden #GitBasedWiki #Wiki #FOSS #Docs #Mkdocs