Tally to GitHub PR without a backend
How a Tally submission goes through a Cloudflare Worker and GitHub Actions to become an issue and draft PR, and where the pipeline broke.
How a Tally submission goes through a Cloudflare Worker and GitHub Actions to become an issue and draft PR, and where the pipeline broke.

An Astro component library where docs and the live render are one page, served to agents through a local MCP server.

From an abandoned tatars.kz to a catalogue of 424 centres in 53 countries: two attempts, a two-year pause, and a full shift in approach.
I went through my bookmarks: 417 links collected over years. Forty-odd survived, each with a description and a fact worth opening it for.

Why a reader wants an instant version of a post, how per-domain templates work, and three traps I walked into while writing one for this blog.

What the starter does well, what it does not contain at all, and where it tripped me up while building this site. With numbers from the repository.

A look inside: the stack, MDX content, a design system across seven accents, client scripts, hooks, the agent layer and real bugs.

A local Android organiser: Tauri 2, a Rust core, SQLite with FTS5, alarms through AlarmManager and spoken-phrase parsing. Not a line of network code.

An offline Android player: three layers with hard boundaries, Media3 in Kotlin, data in Rust, SolidJS on top, and the bugs that shaped it.

388 gradients where the catalogue is a stylesheet and the copy-ready code is derived from it at build time. Architecture, search, Tailwind.