fix: <p> tag formatting (empty line breaks) + ordered list

README.md

@@ -2,3 +2,5 @@
   
 This repository contains the blog we run under the iwakura.rip domain. It is made using [11ty](https://11ty.dev).   
 The main branch contains the production version of our blog running [here](https://blog.iwakura.rip). The review branch contains blog posts that need to be reviewed.
+
+TODO: cleanup code

src/global.css

@@ -6,7 +6,6 @@
 }
 
 body {
-/*    background-color: #0E0E0E;*/
     color: white;
 }
 a {
@@ -33,13 +32,5 @@ hr {
 .blogbox:hover {
     border-color: var(--color-gray-300);
     scale: 1.05;
+    rotate: 1deg;
 }
-
-/*
-#header h3, #links a {
-    display: inline;
-}
-
-#page {
-    padding: 10px 15%;
-}*/

src/post.css

@@ -9,7 +9,8 @@ pre {
     margin: 0.5vw 0;
 }
 
-blockquote {
+blockquote, ol, li, p {
+    list-style: revert;
     box-sizing: revert;
     margin: revert;
     padding: revert;

src/posts/micros.md

@@ -9,7 +9,7 @@ date: 2024-12-18
 
 ## Why? 
 TL;DR: Grew tired of Debian, wanted something immutable and low-maintenance.
-
+ 
 Every single server I have ever touched has always turned into a mess, because  random packages with no use to me that held back updates and/or bloated my system (For context, my main server, which hosts my arr stack and some other services, has ~1700 packages installed, which is a lot, as I mainly only use Docker to deploy services), or even packages that have completely broken all kinds of libraries and required me to spend a Saturday reinstalling. 
 
 Furthermore, I do not have a lot of time anymore to maintain everything, as my real life is starting to take up more and more space. The fact that I use most of the things I host on a daily basis ment that I had to start finding alternatives.
@@ -78,7 +78,8 @@ It's simple, really:
 
 And now we have caddy up and running... right?
 
-> WARNING: Do not use this on special system directories like /home or /bin. It WILL break your system (according to the docker manual).
+> [!WARNING]
+> Do not use this on special system directories like /home or /bin. It WILL break your system (according to the docker manual).
 
 Well, It's not that simple. You see, MicroOS uses SELinux. In short, SELinux defines policies for every application, file, directory etc, and it doesn't play well with container volumes by default. Using this in its current state, caddy wouldn't be able to read or write anything. Fortunately, this is just a simple fix. Add a single z to any lines that define a volume, like so: