WORKSHOP

PROBLEM

Everything I make lived in five different places, none of which I owned, and none of which talked to each other.

APPROACH

Design the language first in Figma, then build a static Astro shell against it, with a token layer strict enough that the design cannot drift silently. Five sync scripts pull the sources in and commit what they find, so no page waits on someone else's API to render.

RESULT

This site — 480-odd pages off five feeds, a dark ground and a light one, and a drift report that says when code and design have stopped agreeing.

PROBLEM

A guild of about ninety players ran on a Google Sheet that published itself as encrypted files, with the decryption key shipped in the browser bundle, so the private roster was readable by anyone who looked. Events, match footage and player stats lived in three other places on top of that.

APPROACH

Three parts, and one of them owns the data. An Angular site on GitHub Pages and a Discord bot both talk to a .NET 10 Minimal API over Postgres. The bot answers Discord over HTTP instead of holding a gateway connection open. Azure Functions sync live player stats from the game's own gateway, but only write when something has changed. Permissions are checked at the API, never in the client, and every design choice answers to one bill: how many hours the database is awake.

RESULT

Three repositories and about 500 commits in fifteen weeks, all on free-tier hosting. The guild gets Discord sign-in with three nested roles, GvG match history with footage, self-run PvP tournaments, scouting across some 6,500 opponent players, and a Discord bot with 41 commands.

PROBLEM

I wanted the shape of a reading year, not a feed of other people's reviews.

APPROACH

Pull my own shelf data, reduce it to finish dates and a single personal note per book, and render it as one line.

RESULT

A year of reading readable at a glance.