It shouldn't be too hard to have a backup domain point to the same resources. Could even be setup as a fallback mirror by default.
You can't pick a Scottish accent for your character in Baldurs Gate 3 and now my Dwarf just sounds British. It sounds, well... off
The "ICH POLICE" with the door opened is a rather Schwarzenegger way to state your occupation, too 👌
At least they tired
By now, the pymdownx.snippets extension that retrieves sections from plain pytest Python files seems to be my way to go. Tests run code as always, which is also formatted as always, specifically marked sections end up in docs. Win, win, win by grace of the scissors operator.
Tried it for a week or two, but since I reinstalled Firefox I really don't understand why I was judging/hating so much in the past years. Yes, Chrome/ium used to be waaaay faster, but Mozilla just has their shit together most of the time. The Debian of browsers so to speak.
Testable examples with MkDocs
Hey there!
I'm looking to move my documentation over to MkDocs (+Material Theme), but I'm struggling to integrate testable code examples. Does anyone have a workflow for this?
Main requirements:
- Testable. Want to make sure my examples work as intended.
- Continuable code fences (i.e. some regular Markdown in between chunks of code)
Nice-to-have:
- Formatting
- Output checking (otherwise, regular asserts will do)
I would have thought Python to have near first-class support for this, but there doesn't seem to be a clear winner as far as plugins go.
Any ideas?
Keep in mind that they are still on the 0.x.x versions. That usually signals a not yet fully matured platform. I'm sure there will be some bumpy times ahead while users keep pouring in.