This page is for the true fans of Project DISCard. Those in the mosh pit, those queueing outside the Enmore since 9am and those getting drenched by the rain are Taylor Swift’s Olympic Park concert. Read on for all the behind the scenes goss and details on Project DISCard.

Exclusive Gift

Are you a fan of Project DISCard? Then we are fans of you! To show our appreciation (and the fact that you clicked on the About page) you can receive a special exclusive Project DISCard gift! This gift is only valid for the first 20 fans. All you need to do to redeem your gift is email projectdiscard@aerowalsh.com and tell us why you love Project DISCard and provide us with your address where you want your special gift delivered.

Site Development

This website is running WordPress with a self-developed custom theme (called discard-sealion). The theme can be found at https://github.com/dekmeister/discard-sealion.

Fun Fact: This website was originally called CD Sealion, but that name did not resonate with the single user and single audience member. The sealion lives on in the logo and in the theme name (discard-sealion).

The theme was developed using Claude Code (a large language model or “AI”) in January 2026 in one afternoon. The bulk of the work was done in two hours with an additional two hours of getting deployment and integration setup (and accommodating a late name change request…). Claude Opus 4.5 was used to generate and document the high level approach (including readme.md, implementation-plan.md and claude.md files) from some provided prompts about the intended audience, high-level layout (instagram like was the request from the user) and architecture decisions. These files were provided to Claude Code (Claude Sonnet 4.5) through VSCodium (open source Visual Studio Code). Claude and myself stepped through the Opus developed nine-phase implementation plan. It essentially one-shotted each phase of the plan. I checked each phase with a local Docker deployment of WordPress to validate it was as expected (the Claude Opus plan was clear on what each phase should provide) and some tweaks (mostly minor improvements outside of original spec) were done at times. I don’t believe Claude was meaningfully reviewing the Docker local WordPress instance to validate its work. Claude did the entire project in a single session without exceeding the token limit (~80% used by the end) or the basic plan limits. The logo was separately generated with Gemini Nano Banana Pro and vectorised with some minor edits in Inkscape.

Fun Fact: Claude wouldn’t add the GPLv2 license to the repo and the Claude API returned an error trying to do this based on content filtering. I had to do it manually. From some research this could be due to Anthropic putting explicit guardrails on Claude Code to avoid it licensing an entire repo to an unintended license.

Some minor updates were made the day after also using Claude. These are captured as Github issues in the repo. Claude mostly one-shotted these as well with some minor tweaks. The repo was made public after this was all completed.