Massive refactor: integrate Tailwind, use components, data-driven lists

This is the result of many, many hours sat at my keyboard trying
different things, most of which failing.

Figuring out how to install Tailwind in this setup was a real adventure
with all of the resources online pulling me in two different ways.
Documentation is hard.

I definitely do prefer having the codebase use the tools available more,
instead of the old simple web dev stuff I'm used to. We're using what's
available through Svelte a lot more now.

I think that these changes will make the codebase easier to work in,
with the architecture being more familiar to regular web developers, and
these changes should also reduce friction when adding new content, which
is the main goal.

I'll never get this time back though, and I'm still slightly
contemplating whether it was really worth it.
This commit is contained in:
2025-07-04 10:33:30 -07:00
parent a2058f08d4
commit be8716a6a0
24 changed files with 665 additions and 1048 deletions

View File

@ -1,6 +1,7 @@
import { sveltekit } from "@sveltejs/kit/vite";
import tailwindcss from "@tailwindcss/vite";
import { defineConfig } from "vite";
export default defineConfig({
plugins: [sveltekit()],
plugins: [sveltekit(), tailwindcss()],
});