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

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

Browse Source
This commit is contained in:
adumh00man
2026-09-22 18:36:08 +00:00
parent ae92ba0eb2
commit 936d89398c
1 changed files with 30 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
content/blog/2026-09-22-how-this-works.md Normal file
View File

@@ -0,0 +1,30 @@
---
title: How this works
date: 2026-09-22T19:36:00
draft: true
description: How does the blog even blog?? Who knows...
---
# This blog
Is just for me ranting. But, because I don't have a life, I obviously needed to overengineer it. The concept is simple. Type into a box, press publish, and have whatever you typed show up somewhere else with nice formatting. Come on, wordpress had this down like 15 years ago. The implementation, however, is far from simple.
## 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.
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.
In order to remove the friction of having to use nvim for anything other than programming, you know, the thing it's made for, I decided that, like every service ever, I needed a web interface. There are plenty of those, take Wordpress or any of its forks for instance. You can log in and write articles on the same site that you read them on, it's a perfect system. There's no limitation on being on a computer with a specific version of a niche cli text editor in order to write something (I'm still salty about neorg ok), which, in theory, means that writing articles should be less of a hassle. Of course, I wasn't about to use Wordpress, because fuck the Wordpress foundation. Who do you think I am? That's right, a loser. Enter Decap.
### Decap what?
Decap, or Netlify CMS, is adware garbage in my opinion. The parent company, Netlify, hence the name, is one of those predatory server hosting companies that hide their bad practices and awful business in general behind pretending to contribute to open source. Think Linode and Hetzner. Or the Wordpress foundation. Fuck the Wordpress foundation. Anyway, Decap CMS.
The concept is simple. Provide it with some kind of git api, and a repo to commit to, and it'll manage all the markdown and media files within. This would allow someone to, theoretically, write articles on a web interface and publish them to a blog, or something. Crazy concept, I know. The only reason I'm not using it right now is because there wasn't a dark mode. I'm not joking. Sure, Netlify didn't document half of the install process because their server hosting platform just so happens to do it automatically, but I'm not writing a whole ass article on a shit looking web interface with an `#FFFFFF` background. That and Netlify is a scummy company, whatever.
### 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 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))