From 693562648091d9dc8757f985f2b833188fb2930f Mon Sep 17 00:00:00 2001 From: legoraft Date: Sat, 6 Jun 2026 11:25:27 +0200 Subject: [PATCH] post: fixed weird styling on linked code blocks --- content/posts/everything-git-no-way.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/posts/everything-git-no-way.md b/content/posts/everything-git-no-way.md index a4028b7..ddf6142 100644 --- a/content/posts/everything-git-no-way.md +++ b/content/posts/everything-git-no-way.md @@ -24,7 +24,7 @@ This got even more unhinged when I started self-hosting my own git forge. This w After making everything I own a git repo, I realized that a lot of that was unnecessary. I still use git, _a lot_, but I've become a bit more intentional about using it. Coding projects always go into git immediately, as version controlling different versions is very handy to check out some old experiments or branches. My personal life, however, has become somewhat of a mixed bag. -I mentioned plain text accounting, which is awesome, but a _lot_ of work to set up. You also kind of need to know how you want to structure everything and these tools have a lot of crazy functions that can be awesome or just a time sink. I want to get back into plain text accounting, but create a plan at the start and try some more things. Then it maybe could become my 'true' accounting strategy. My recipes are still a mix between markdown, my brain and cooklang. I've recently started using [`cook report`](https://cooklang.org/docs/use-cases/reports/) to generate zola-ready markdown files and am looking to create a simple cookbook theme I can use to browse my recipes everywhere and anywhere. +I mentioned plain text accounting, which is awesome, but a _lot_ of work to set up. You also kind of need to know how you want to structure everything and these tools have a lot of crazy functions that can be awesome or just a time sink. I want to get back into plain text accounting, but create a plan at the start and try some more things. Then it maybe could become my 'true' accounting strategy. My recipes are still a mix between markdown, my brain and cooklang. I've recently started using `cook report`[^3] to generate zola-ready markdown files and am looking to create a simple cookbook theme I can use to browse my recipes everywhere and anywhere. My notes and todos have taken a whole other turn. I've been an avid [obsidian](https://obsidian.md) user, but this second brain idea really breaks down when you just want to write something down quickly. I've moved back to paper for notes, planning and my agenda. This is something that works better for me, especially since I'm not next to a computer during work and still need to write things down. @@ -34,3 +34,4 @@ Understanding git was truly a "No way!?" moment for me, but it took me about two [^1]: Hidden files in Linux, often used for configuration. Check out my [dots](https://codeberg.org/legoraft/dots)! [^2]: As programmers do, there is [discussion](https://sumnerevans.com/posts/software-engineering/stop-using-conventional-commits/) on the use of these. +[^3]: It's very early stages, but works like a charm, check out the [docs](https://cooklang.org/docs/use-cases/reports/). -- 2.51.2