Work we gave away.

Started during the first lockdown. The idea was simple: people had appliances, clothes, furniture they didn't need, and other people needed those exact things. The hard part wasn't the matching, it was the communication. Most platforms that tried to do this made both sides hand over a phone number or an email address, which put a lot of people off.

We built the whole thing around real-time messaging. Donors and recipients can talk directly without either side giving up any personal contact detail. SignalR handles the chat, a lean Blazor front-end handles the catalogue, and MariaDB keeps the record.

No tracking. No ads. No upsells.

A community centre covers a lot of ground: scheduled events, walk-in classes, venue hire, public noticeboards. Coleman's existing site had been patched together over the years and staff avoided editing it because edits broke things.

We rebuilt from scratch with Blazor WebAssembly and an ASP.NET Core API backend. The centre's coordinator now edits content through a small admin panel without touching code. Events update in real time. Forms route to the right person depending on the query.

Hosted on modest Linux kit with Caddy, backed by MariaDB. Small enough to run cheaply, robust enough that it hasn't needed attention in six months.

Amal Quaryaty works directly in remote villages. Solar panel installations, borewell water projects, food distribution during lean months, and a women's empowerment programme supporting seventy women and growing.

Our job was a site that did what it needed to do quietly: explain the work, show the projects in progress, and make donations straightforward. Newsletter signup, project showcase pages, small impact metrics running at the top.

Built on the same Blazor and ASP.NET stack we tend to use for pro bono work, because it runs cheaply on modest infrastructure and survives traffic spikes when the charity gets press coverage.

Built as a single-page application with no framework overhead, no build step, and no tracking. Pure HTML, CSS, and JavaScript. The codebase is a few hundred lines and can be read end to end in an afternoon.

We focused on three things: speed, simplicity, and accessibility. The audience is broad, the hardware varies, and the network conditions cannot be assumed. A question should load instantly whether you're on gigabit fibre or a patchy 3G signal in a school corridor.

Hosted behind Caddy on a small Linux box. Serves the whole site statically. Fast, cheap, nothing to break.

Learning classical Arabic is a long project. The vocabulary is enormous, the grammar is intricate, and progress can feel invisible. Mithliha is a gentle nudge: short timed rounds that mix vocabulary recall with short-passage recognition, designed around retention rather than completion.

The content matters more than the engine. We spent a lot of time getting the text accuracy right, deciding the order in which concepts are introduced, and picking passages that hold up under repeated exposure. The code is standard Blazor; the curriculum is where the thought went.

A local educational charity needed two things at once: a clean public page that prospective families could trust, and a structured application pipeline that staff could actually run without calling us every week.

We built the front end for the parents and the admin panel for the staff. Form validation is strict but friendly. Submissions land in a simple review queue. Staff can approve, request more information, or reject, all without seeing a line of code.

The kind of tool that just needs to work, and keep working, without drawing attention to itself.