We need 75+ stars on GitHub to publish to homebrew!
Share the #mdbabel love to make your #markdown documents executable:
https://github.com/md-babel/swift-markdown-babel
New Kitten release 
• Fix for Markdown pages¹: import { Multiple, Exports } … and import { Foo as Bar } … now properly supported in front matter when importing components.
Enjoy!
¹ https://kitten.small-web.org/reference/#markdown-pages-page-md-files
New Kitten release 
Fixes:
• Components with slotted content in Markdown pages¹ are now properly supported.
• Backticks in content slotted into components in Markdown pages are now automatically escaped.
Enjoy!
#Kitten #SmallWeb #release #markdown #fixes #components #web #dev
¹ https://kitten.small-web.org/reference/#markdown-pages-page-md-files
New Kitten release 
• New: Lovely new icons¹ and new callouts in Kitten Settings²
• New: Markdown now supports attributes and bracketed spans³
• New: client-side `kitten` global with `trigger` function for triggering events on the server from the client. (Useful when streaming client-side JavaScript when using Kitten’s Streaming HTML⁴ workflow. e.g., when you have to use a client-only web API like the Clipboard API but you want to keep all your logic on your server-side page.⁵)
• Fixed: The bound render function returned by `KittenComponent` class’s `component` getter now correctly awaits asynchronous templates. (In Kitten, you don’t have to care whether your templates contain promises. Kitten handles all that for you.)
Enjoy!
¹ https://kitten.small-web.org/reference/#icons
² https://mastodon.ar.al/@aral/114381983893061099
³ https://kitten.small-web.org/reference/#markdown-support (also see https://mastodon.ar.al/@aral/114381462302862256)
⁴ https://kitten.small-web.org/tutorials/streaming-html/
⁵ e.g., See how I use this to implement a copy to clipboard button in the database page of Kitten’s Settings: https://codeberg.org/kitten/app/src/branch/main/web/%F0%9F%90%B1/settings%F0%9F%94%92/db/index.page.js#L33 Of course, you don’t have to use this and you can just write client-side JavaScript or use the built-in Alpine.js integration. e.g., how I do it on the (older) settings/identity page: https://codeberg.org/kitten/app/src/branch/main/web/%F0%9F%90%B1/settings%F0%9F%94%92/identity/index.page.js#L7
Coming soon: quite loving how much you can do in Markdown in Kitten now that I’ve added the ability to specify attributes and have bracketed spans.
Will release after I’m finished redoing the Kitten Settings pages with the new Kitten icons available at `kitten.icons`.
EDIT: Sarcasm? See https://civv.es/notes/a6sj1ccdd65e00qu
I was at a group this morning where folks were raving about Ulysses (the writing app). I kept trying to remember why I stopped using that, and finally searched email, and oh right, here it is. I was a user until I got this newsletter. It's the last one I have, must have unsubscribed after that.
I'd like a new #markdown app and would like to try Ulysses again, but does anyone know if they have corrected their stance here?
In case you don’t know: when writing text in #Markdown, you add a footnote like this `my text needs this footnote[^afootnote]` and somewhere else in your text you add `[^afootnote]: And this is the footnote`. The colon is important! When this gets rendered and your markdown renderer supports footnotes, they will be converted to consecutive numbers and added as list to the end of the text. The labels will become navigation anchors. Quite cool! See https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/ for an example.
I have to write more #Markdown so that stuff like footnotes and block quotes come naturally without forcing me to look up again and again how stuff works ;)
Geany (Linux, Win, Mac) ist ein "unscheinbarer" Texteditor, der sich auf vielen Systemen findet, aber oft unterschätzt wird.
Schlank, flink, erweiterbar, sehr gut auf eigene Bedürfnisse anpassbar und doch aufgeräumt - es lohnt sich, mal einen näheren Blick darauf zu werfen.
Ebenfalls nützlich: Die Markdown-Erweiterung:
"Most guides to docs like code, even the ones for non-devs, assume you have some developer knowledge: maybe you're already using version control, or you've encountered build pipelines before, or you're working alongside developers.
This guide is for the people who read that paragraph and wished it came with a glossary. This is docs like code for people who don't know what git is and have never installed VS Code.
This post explains terminology and concepts, to help you get a mental model of what's going on. If you prefer to dive in and pick up concepts as you go, skip straight to the tips in How to learn, and come back to the conceptual info as needed."
@ojs @vga256 for me #Markdown is essential. There are partly different standards but it makes conversion from one generator to another really simple. there are anough tools to quickly change some frontmatter etc. so a switch of content is more easy and also you might be able to test different machines with the same content.
I think I finally have this thing complete - the paper is live hosted on a little test node, also lives as README.md on the GitHub.
https://idens.net/iden://z1HRUsTNcYMkN5WPm9s1YjGaLUVs58RVRHPjBrV1kYwdAJ.642/pub
https://github.com/md-babel/swift-markdown-babel
v0.3.0 of #mdbabel supports rendering images from code.
I've tested this with Mermaid CLI, and it should also work with Graphviz and LaTeX.
I got tired of manually updating my CV across different formats, especially PDF.
So I built CVBuilder, a Swift package that keeps everything in code—typed, versioned, and exportable as Markdown, HTML (via Ignite), or plain text.
Here's more info about it:
https://aleahim.com/cvbuilder/
And a GitHub repo:
https://github.com/mihaelamj/cvbuilder
I've had a statuslog section on my now page (https://reillyspitzfaden.com/now/) for a while, and I added it to my homepage as well (https://reillyspitzfaden.com/#homepageStatus).
The especially nice part is that I now have a script (https://github.com/reillypascal/personalsite-ssg/blob/main/status) so I can simply type `./status` in the terminal, write the status text in the resulting .md file that pops open, and then commit/push!
I've seen some IndieWeb people (e.g., @binarydigit) do something similar via one of omg.lol's tools (https://home.omg.lol/info/statuslog) and liked it, but I wanted to see if I could DIY it just for the heck of it. Very happy with how easy the result is!
What is the simplest method you can recommend me to setup a blog using markup? I only need to be able to write some text, put some source codes and assembly with syntax highlighting, some images, and it can all be static content.
Any recommendation?
