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

how was made update
Some checks failed
Deploy Blog / deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
jawhng
2025-12-22 21:37:49 +00:00
parent d17f01e13b
commit 6a249b9ec0
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/routes/posts/how-this-site-was-made.md
View File

@@ -1,10 +1,11 @@
---
title: "How This Site Was Made (And Why You Probably Don't Care)"
title: "How It's Made - The Blog (please validate my questionable choices)"
date: "2025-12-22"
excerpt: "A cynical walkthrough of building a blog with SvelteKit, particles.js that doesn't work, and enough utility classes to make you question your life choices."
---
Everybody's dying. Some people are just doing it faster than others by choosing the wrong JavaScript framework.
Me as an Angular developer I'm here for a good time, not a long time. Now Svelte - that's something else. Long before I became a developer I used to have a blog. That blog was made using Jekyll and lives as a GitHub page. This blog is an almost exact visual copy of the old one. Here's some info for nerds, colleagues or prospective colleagues. If you're neither of these - pay me more.
## The Tech Stack
@@ -71,4 +72,4 @@ It runs in a background thread because build times are longer than webhook timeo
This site was built in a couple hours with SvelteKit, some questionable design choices, and the crushing realization that web development in 2025 is somehow both easier and more complicated than it was 5 years ago.
Will I maintain it? Probably not. Will I write actual content? Maybe. Will I spend more time tweaking the particle configuration than writing posts? Absolutely.
Will I maintain it? Probably not. Will I write actual content? Maybe. Will I spend more time tweaking the particle configuration than writing posts? Absolutely.