I've got a pretty sweet system for journaling in Emacs using Org-journal. It's fast, free, plain text, and local first. I can export to a nice monthly two-column PDF using LaTeX and I'm happy with it. But once in a while I open Day One and my goodness that's a pleasant, easy app to use for Journaling. Plus, I can order cool printed books with just a few taps. I still use Tinderbox occasionally as a daybook, and I have a script there that cross-posts the current entry to Day One. Maybe I should recreate this for my Org journal. That way I don't have to decide 😁.

I use Markdown to write posts here in Kirby's panel. The resulting content files don't use YAML front matter like Hugo and others, but I'm fine with that, honestly. I'm sure there's a little Python or whatever script out there that would help convert them. What I'm concerned with today, though, is my use of KirbyText within content. For example, a link looks like this: ( link: https://baty.net text: My Blog ). (I added spaces so it wouldn't actually render as a link.) On one hand, KirbyText is actually easier to write than Markdown. On the other hand, it makes the content dependent on Kirby. Normally this would set me to twitching, but I used to use things like Hugo shortcodes without blinking, so what's the big deal? The regular expressions to find/replace KirbyText with normal Markdown shouldn't be difficult to write, either. Conclusion: I think using KirbyText will be fine.