blog: fixes.

fezcode · fezcode · commit 6007ad2ae22d · 2025-11-30T02:29:24.000+03:00
diff --git a/public/posts/demystifying-tailwind-css.txt b/public/posts/demystifying-tailwind-css.txt
@@ -1,4 +1,3 @@
-
 # Demystifying Tailwind CSS in `fezcodex`: A Utility-First Approach
 
 In the `fezcodex` project, you'll notice that our components are styled **cool**(!). Instead of writing custom CSS for every element, **Tailwind CSS** is used. This post will explain what Tailwind CSS is, how it's configured in my project,
diff --git a/public/posts/do-i-need-to-create-a-lib-for-that.txt b/public/posts/do-i-need-to-create-a-lib-for-that.txt
@@ -1,5 +1,3 @@
-# Do I Need to Create a Lib For That?
-
 ## My Journey into Go Libraries
 
 Creating my first Go library, [go-tournament-brackets](https://github.com/fezcode/go-tournament-brackets), has been a, _experience_...
@@ -71,4 +69,4 @@ So, you've built your awesome Go package, and now you want to share it with the
     *   **Want to nudge it?** If you're impatient (we get it!), you can explicitly ask a proxy to fetch your new version. For example, running `go get github.com/fezcode/go-tournament-brackets@v0.1.0` (or `go list -m ...`) from *any* Go project will make the proxy grab it if it hasn't already. This is more about *verifying* discovery than publishing.
 
 4.  **Patience, Young Padawan (Waiting for `pkg.go.dev`):**
-    After your module is tagged and the proxies know about it, `pkg.go.dev` (Go's official package discovery site) will eventually list it. Just a heads-up: this isn't instant. It can take anywhere from a few minutes to a few hours for it to show up. So, grab a coffee, and it'll be there!
+    After your module is tagged and the proxies know about it, `pkg.go.dev` (Go's official package discovery site) will eventually list it. Just a heads-up: this isn't instant. It can take anywhere from a few minutes to a few hours for it to show up. So, grab a coffee, and it'll be there!

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,3 @@`
`1`		`-`
`2`	`1`	# Demystifying Tailwind CSS in `fezcodex`: A Utility-First Approach
`3`	`2`
`4`	`3`	In the `fezcodex` project, you'll notice that our components are styled cool(!). Instead of writing custom CSS for every element, Tailwind CSS is used. This post will explain what Tailwind CSS is, how it's configured in my project,