post: butterrobot 0.2.4

Makefile

@@ -10,7 +10,7 @@ new-post:
 	POST_DIR="content/blog/$$YEAR/$$MONTH/$$DAY/dummy"; \
 	mkdir -p "$$POST_DIR"; \
 	echo "+++" > "$$POST_DIR/index.md"; \
-	echo "title = Dummy Post" >> "$$POST_DIR/index.md"; \
+	echo "title = \"Dummy Post\"" >> "$$POST_DIR/index.md"; \
 	echo "date = $$(date +%Y-%m-%d)" >> "$$POST_DIR/index.md"; \
 	echo "draft = false" >> "$$POST_DIR/index.md"; \
 	echo "+++" >> "$$POST_DIR/index.md"; \

content/blog/2025/04/22/revisiting-butterrobot/index.md

@@ -0,0 +1,24 @@
++++
+title = "Butterrobot 0.2.4 released"
+date = 2025-04-22
+draft = false
+tags = ["butterrobot", "golang", "projects", "releases"]
++++
+
+I've decided to revive Butterrobot after a long hiatus.
+
+The project was originally written in Python and it was designed to be a simple way to have quality of life in Slack and Telegram channels. After I made [the initial implementation](https://github.com/fmartingr/butterrobot) I started going deeper into Golang and mostly abandoned it with a promise to come back and rewrite it in the future.
+
+That day is here.
+
+![Butterrobot Logo](butterrobot.png?width=320#center)
+
+<!--more-->
+
+I went ahead and rewrote the entire thing in Golang. All previous features are still available and working as they should before. What I have lost is the ability to easily create plugins without making changes to the original repository. The implementation in Python relied on pip packages that could create entrypoints in the plugin and were automatically discovered by the application. In Golang, we need to manually register plugins and their entrypoints in the code so all _plugins_ go into the main repository. I could have gone the RPC route but it added unnecessary complexity and overhead. Instead, I opted for a more straightforward approach that allows for easy plugin development and maintenance.
+
+The main repository is now available on [my git forge](https://git.nakama.town/fmartingr/butterrobot) and it can be used on Telegram bots easily, as I am already using it in my groups. Right now a small subset of plugins are available but I plan to add more in the future as I add more capabilities to the bot framework.
+
+![Plugin list in the web interface](plugins.png?width=640#center)
+
+[Go get it!](https://git.nakama.town/fmartingr/butterrobot)

content/blog/2025/04/27/i-read-feel-good-productivity/index.md

@@ -0,0 +1,24 @@
++++
+title = "I read Feel-Good Productivity"
+date = 2025-04-27
+tags = ["books", "I read"]
++++
+
+I've tried to read productivity books for a while, started with note-taking, time management, and goal-setting... but never managed to finish any of them. This is the first book that not only I finished, but also I found it enjoyable, insightful, and provides practical tips for improving productivity. And not only that, is the first one that I have used a marker on to highlight important passages.
+
+![Feel-Good Productivity](feel-good-productivity-cover.jpg?width=320#center)
+
+<!--more-->
+
+What did I like from this book that makes it different from other productivity books?
+
+- Productivity should be fun and enjoyable, not just a chore. That's just something basic but it didn't click for me until I stopped and thought about it for a moment. I have been doing some hobbies that just weren't fun for me, but I realized that I was doing them because I thought they were supposed to be fun, not because I actually enjoyed them. I replaced them with activities that I actually enjoy doing, or at least I'm trying to do so.
+- The book is organized in a way that makes it easy to follow and understand. Each block focuses on a specific aspect of productivity, such as motivation, focus, and time management, providing practical tips and **actionable advice**.
+- The writting style is easy going and enjoyable to read, relating to the author's personal experiences and insights and providing real-life examples to relate the content to the reader's own experiences.
+- It provides summaries of each chapter, making it easy to review the content and remember the key points.
+
+After reading it I bought the audiobook so I can focus on specific chapters that I want to deeply understand and apply into my daily life, there are some chapters that are very good for productivity nerds like me.
+
+I have already started to apply some of the tips from the book into my daily life, and I'm already seeing improvements in my productivity, habits, and overall well-being.
+
+If you are thinking into reading a book about productivity, I highly recommend this one. It's a great and easy read, and it's a book that I can recommend to anyone who wants to improve their productivity.

content/blog/2025/05/04/i-played-celeste-pico-8/index.md

@@ -0,0 +1,22 @@
++++
+title = "I played Celeste (PICO-8)"
+date = 2025-05-04
+tags = ["videogames", "I played"]
++++
+
+> I bought an Anbernic device mainly to play PICO-8 games on it, but after playing two games the screen broke and I had to return it so I still have a nice backlog of PICO-8 games to go through when I sit down and set up my Retroid Pocket.
+
+<figure>
+    <img src="/blog/2025/05/04/i-played-celeste-pico-8/cover.png" \>
+    <figcaption>The cartdridge for the game... or to better put it, <a href="https://pico-8.fandom.com/wiki/P8PNGFileFormat" target="_blank">this image <strong>is the actual game!</strong></a></figcaption>
+</figure>
+
+<!--more-->
+
+I must say this game was a lot of fun to play, even though I played the games in reverse since [I went through Celeste on the Switch a while ago](https://screenshots.fmartingr.com/Nintendo%20Switch/Celeste/), but this was something I had to experience for myself.
+
+Celeste left such an impression on me that I recalled some of the levels from the Switch game in their original gamejam version, and I must say that it was more difficult than I remembered (but also rewarding) and I made it through:
+
+![My first Celeste Pico-8 playthrough](https://screenshots.fmartingr.com/Pico-8/Celeste/muOS_20241114_2236_1.png)
+
+What an intense 17 minutes, I must say. Now I want to went through the Switch game again since I barely scratched its surface. Should I go on and try to complete all extra levels? Get all strawberries?

content/projects/butterrobot.md

@@ -0,0 +1,8 @@
++++
+title = "Butterrobot"
+description = "A chatbot helper for my Telegram groups"
+layout = "projects"
+repository = "https://git.nakama.town/fmartingr/butterrobot"
++++
+
+A chatbot I had [written in python](https://github.com/fmartingr/butterrobot) back in my Python days the moment I started learning Golang. I used it to help me manage some Slack/Telegram groups and I abandoned it the moment I had to make it to production with Python. I rewritted it in Golang so I can add some quality of life features to some Telegram groups I manage, and I probably expand it to Mattermost in the future as well.

themes/fmartingr/assets/sass/_blog.sass

@@ -2,6 +2,12 @@ div.article, main.blog, main.projects
   .title
     margin-bottom: 0.3em
 
+  &.future-post
+    border: 2px solid orange
+    border-radius: 8px
+    padding: 10px
+    margin-bottom: 15px
+
   .info
     *
       vertical-align: middle

themes/fmartingr/layouts/_default/home.html

@@ -2,7 +2,7 @@
 <div class="home center">
     <h1 class="title">Latest blog posts</h1>
     {{ range where site.RegularPages "Section" "blog" | first 10 }}
-    <div class="article">
+    <div class="article{{ if gt .Date.Unix now.Unix }} future-post{{ end }}">
         <h2 class="text-size-normal"><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
         <div class="info">
             {{ partial "svg/calendar-event.svg" (dict "size" 24) }}

themes/fmartingr/layouts/_default/list.html

@@ -2,7 +2,7 @@
   {{ if ne .Title "Blogs" }}<h1>{{ .Title }}</h1>{{ end }}
   {{ .Content }}
   {{ range (.Paginate .Pages 7).Pages }}
-  <div class="artitle {{ $.Param "site_style.container_class" }}">
+  <div class="article {{ $.Param "site_style.container_class" }}{{ if gt .Date.Unix now.Unix }} future-post{{ end }}">
     <h2 class="title"><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
     <div class="info">
       {{ partial "svg/calendar-event.svg" (dict "size" 24) }}