adumh00man/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Blog “2026-09-22-how-this-works”

Browse Source
This commit is contained in:
adumh00man
2026-09-25 18:36:10 +00:00
parent 78fdeb5433
commit 6f2802a38c
1 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
content/blog/2026-09-22-how-this-works.md
View File

@@ -1,7 +1,7 @@
---
title: How this works
date: 2026-09-22T19:36:00
draft: true
date: 2026-09-25T19:36:00
draft: false
description: How does the blog even blog?? Who knows...
---
@@ -11,7 +11,7 @@ Is just for me ranting. But, because I don't have a life, I obviously needed to
## CMS (Content management sucks)
Before, on my previous garbage blog that I never uploaded to, I didn't bother with a content management system. I would just write in neovim and then push it to git so that the blog updated. This is a shit system, because it means that there's extra setup for writing for the blog. As soon as neorg (the markdown superset I was using) stopped working after 0.12, the blog was no more. I didn't realise at the time, but the site generator I was using literally just flattened the neorg structure into markdown before converting it to HTML, which kind of defeated the purpose of using neorg in the first place.
Before, on my previous garbage blog that I never uploaded to, I didn't bother with a content management system. I would just write in neovim and then push it to git so that the blog updated. This was a shit system, because it meant that there was extra setup for writing for the blog. As soon as neorg (the markdown superset I was using) stopped working after 0.12, the blog was no more. I didn't realise at the time, but the site generator I was using literally just flattened the neorg structure into markdown before converting it to HTML, which kind of defeated the purpose of using neorg in the first place.
Therefore, I switched to markdown. Markdown, being markdown, is more widely supported and therefore better. That's just how the internet goes. Also, there's literally no neorg feature other than indenting (which it did through lies and deceit anyway) that isn't just in markdown anyway. Not that I was using any of them anyway, I literally only use titles and code blocks. lol.
@@ -25,7 +25,7 @@ The concept is simple. Provide it with some kind of git api, and a repo to commi
### CMS but better
Sveltia, probably written in svelte (not that I checked) is exactly the same project but better. It looks better, it performs better, but it's actually fully opensource with a GPLv3 license and actual documentation. It's the sway to Decap's i3, and in the same way, is supposed to be a drop in replacement. Replace one line in the html file and you've installed it. Did I mention that these kind of CMSs are built from javascript files instead of being actual webpages? Weird.
Sveltia, probably written in svelte (not that I checked), is exactly the same project but better. It looks better, it performs better, but it's actually fully opensource with a GPLv3 license and actual documentation. It's the sway to Decap's i3, and in the same way, is supposed to be a drop in replacement. Replace one line in the html file and you've installed it. Did I mention that these kind of CMSs are built from javascript files instead of being actual webpages? Weird.
Sveltia DEFAULTS to dark mode, which means that's the one I'm using forever. I could theme it to be all catppuccin like everything else in my life, but I'm too lazy. There are limits to my joblessness, ok? The way that sveltia works is through a simple config file, defining the frontmatter of different "collections" of markdown files. Collections are just folders, like if you had a blog folder and a project folder. Frontmatter is where you can define stuff like the description and publish date of an article, and whether its a draft or not. If you want to see what I'm on about, look at the source for this site [here]([https://git.voidarc.co.uk/adumh00man/blog]\(https://git.voidarc.co.uk/adumh00man/blog\)).
@@ -37,4 +37,12 @@ There are two halves to a good blog setup. The generator and the theme. The gene
### Hu-goes there??
Bad pun I know. Hugo is written in go and under the Apache 2 license. Open source, good shit. It also has a massive and very active community, having about 90k stars on github. That means there are lots and lots of themes available, but we'll get there. Hugo requires you to run a command in order to rebuild the site, which means
Bad pun I know. Hugo is written in go and under the Apache 2 license. Open source, good shit. It also has a massive and very active community, having about 90k stars on github. That means there are lots and lots of themes available, but we'll get there. Hugo requires you to run a command in order to rebuild the site, which means that the actual "site layer" is seperate from the CMS. Why they wouldn't just merge the two functions into one, I didn't get at first, but then realised there isn't a backend to the CMS at all. Figures.
My solution was my glorious saviour n8n. By making gitea trigger a webhook every time that the repo is pushed to, I can run a command on my server that rebuilds the site. Nginx doesn't care if the files are updated, so, as long as cloudflare doesn't do any stupid css caching nonsense, the site updates basically in real time. Pretty cool, huh? But hugo doesn't know what to do with any of my files if I don't provide a template, or a theme, that dictates how things are laid out.
### Hugo theming and such
Hugo is not a blog framework. It's more of a multipurpose site generator, for sites that aren't big or complicated enough to need javascript. That means that there are too many hugo themes to count, and that if you put one next to another, you would hardly be able to tell that they were both made by the same generator. Of course, there are ways to implement javascript functionality into hugo sites, like implementing comments, but I don't care what people have to say about my work, so I chose the most minimal one I could find.
The blog you are reading right now, as it so kindly says in the footer, is using the papermod theme, which is regarded as the most minimal blog template you can get while still looking good. I changed the colors to match the rest of my life, but other than that, the rest of the site's features are configured purely through markdown and toml alone. Pretty cool, right? There are more features I could be using, sure, but like, I don't care. This is good enough for ranting at least. Now back to editing Youtube videos. Bye!