diff --git a/_drafts/prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi b/_drafts/prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi
deleted file mode 100644
index 219122c..0000000
--- a/_drafts/prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: 'Prime Directive: Minimalism and Efficiency with Gemini Protocol'
----
-Just a couple of weeks ago I restarted my site with the idea of keep a minimalist approach, focused on content rather than flashy styles or colorful themes. Also for the first time I decided to do a dual hosting to make it available via HTTPS and Gemini (Protocol).
-
-An idea I've been floating on my head for a couple of days was that, since HTTPS site was already pretty basic in terms of styles and layout, why not just somehow serve the same content I have for Gemini. This morning, this idea materialized thanks to a small proxy tool called Kineto. This tool is a proxy that allows serving a single Gemini Capsule to regular web browsers. And, after making a few tweaks to my code and deployment I was able to remove Jekyll completely and just keep the minimal parts.
diff --git a/_posts/2025-01-08-prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi b/_posts/2025-01-08-prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi
new file mode 100644
index 0000000..5425d9b
--- /dev/null
+++ b/_posts/2025-01-08-prime-directive-minimalism-and-efficiency-with-gemini-protocol.gmi
@@ -0,0 +1,15 @@
+---
+date: 2025-01-08 11:01 +0000
+title: 'Prime Directive: Minimalism and Efficiency with Gemini Protocol'
+---
+Just a couple of weeks ago, I restarted my site (the one you are reading right now) with the goal of maintaining a minimalist approach—focusing on content rather than flashy styles or colorful themes. For the first time, I also decided to implement dual hosting, making the site available via HTTPS and the Gemini protocol.
+
+An idea that had been floating around in my mind for a few days was that, since the HTTPS version of the site was already quite basic in terms of styles and layout, why not serve the same content I use for Gemini? Yesterday morning, this idea came to life thanks to a small proxy tool called Kineto [1]. This tool acts as a proxy, allowing a single Gemini capsule to be served to regular web browsers.
+
+After making a few tweaks to my code and deployment, I was able to completely remove Jekyll and keep only the minimal components. Additionally, since the Gemtext [2] format is already simple and easy to write, there was no need to transform Markdown to Gemtext. I refactored all my content files from Markdown to Gemtext, which consisted only of changing their file extensions.
+
+The capsule generator is still quite basic (honestly, I'd even call it a pre-alpha version). I still need to decide whether to continue using my own code or switch to a more formal capsule generator. For those who are curious, the source code for both my site and the generator can be found in my Forgejo repo [3].
+
+=> https://sr.ht/~sircmpwn/kineto/ [1]: Kineto
+=> gemini://geminiprotocol.net/docs/gemtext.gmi [2]: A quick introduction to "gemtext" markup
+=> https://code.palmiers.xyz/erick/erick.is [3]: erick/erick.is