People
Member accounts, profiles, friend requests, follows, direct messaging, notifications, and personal show histories.
FILE 01
Still On Tour
Design + build — a Dead North projectWhat we actually built
Not a content site. A purpose-built social network.
Still On Tour was designed and built as a real community product for people who follow live music — where the archive gives every interaction a meaningful place, date, band, and shared story.
Groups
Crews, show walls, conversations, member-made context, and a social graph that belongs to the community instead of an algorithm.
The road
Trips, rides, crash-space coordination, local connection, event planning, and bands managing dates, members, booking, EPKs, and fan notes.
Trust
Blocks, reports, moderation queues, appeals, consent checks, visibility boundaries, CSRF protection, write throttles, export, and erasure.
A full social platform for a live-music community — member accounts, profiles, friend requests, direct messages, crews, show walls, trips, ride and crash-space coordination, band workspaces, and a living concert archive giving every connection a shared place and time.
5,441shows · 1,997 venues · ~100k performances
Still On Tour is not a themed database or a brochure with a login. It is a custom social product built around the way music people actually move: mark the shows you attended, find friends, message directly, form a crew, plan a run, arrange a ride or crash space, talk on a show wall, and follow a band. The archive is the shared map beneath all of that. A decoupled Drupal 11 and Next.js application carries that public experience, authenticated social graph, private member activity, band portal, review workflow, and staff tools as one coherent system rather than a pile of plugins.
A social product, not a comments section
Accounts have profiles, friends, private messages, crews, notifications, and show-level conversation. The product makes real connection possible around a shared music life rather than chasing generic engagement metrics.
Safety is part of the feature set
Blocks, reports, moderation queues, appeals, consent checks, write throttles, and carefully scoped visibility rules are designed into the social surfaces. Private member activity is not accidentally exposed through a public archive page.
An archive that can admit uncertainty
Shows distinguish an incomplete record from no surviving tape, missing documentation, or conflicting sources. That is product design in service of historical honesty — not a blank state dressed up as certainty.
Community contribution without community chaos
Members can propose corrections and add context; review flows keep public claims source-tracked, rate-limited, and accountable. Verified bands get a workspace for dates, an EPK, member access, booking requests, and fan notes.
Production-grade boundaries underneath
The architecture separates the Next.js public experience from Drupal’s authenticated API and staff surface, applies CSRF protection and write throttles, keeps a consent gate ahead of member actions, and supports data export and erasure instead of treating privacy as a footer link.
- Drupal 11
- Next.js
- TypeScript
- MariaDB
- Cloudflare
- 2026
FILE 02
V.I.N.CENT
Design + buildA fleet-monitoring platform watching 327 production sites — statistical anomaly detection against each site’s own history, an archive of what the host discards, and one rule everywhere: an unchecked site must never look healthy.
327production sites watched
Most monitoring answers "is it up?" This answers "is it behaving like itself?" — each site is measured against its own history rather than a shared threshold, so a site that has always been slow does not cry wolf and a site that just got slow cannot hide. The hard rule underneath is that silence is never treated as health: a check that did not run reports as unknown, loudly, because a dashboard that goes quiet when the collector dies is worse than no dashboard.
- Drupal 11
- Next.js
- Pantheon
- 2026
FILE 03
The Migration
Sole technical leadA monolithic Drupal 7 application with millions of nodes, rebuilt as Drupal 10 while the site kept publishing — custom migration paths, counts reconciled every run, zero records lost.
Millionsof records moved · zero lost
The site could not stop publishing, so the migration ran incrementally against a moving target for months. Every run reconciled its own counts and refused to advance on a mismatch, which is the only reason "zero records lost" is a statement rather than a hope. Cutover was measured in minutes.
- Drupal 7→10
- Migrate API
- Behat
- 2023
FILE 04
Enhanced Taxonomy Manager
Open source — creator & maintainerA replacement for Drupal core’s taxonomy UI, built for vocabularies from a dozen terms to 100,000 — drag-and-drop, undo history, bulk merge and clone. Running on 90+ production sites by drupal.org’s own count.
90+sites running it in production
Core’s taxonomy screen was written for a short list and falls over on a long one. This handles vocabularies three orders of magnitude larger with drag-and-drop reordering, an undo history, and bulk merge and clone — and the install count is drupal.org’s own, not ours.
- Drupal 10/11
- Vanilla JS
- SortableJS
- 2025–
NEXTYour projectthe roster stays small on purpose
Every file above started as a conversation about something that had to keep working. If you have one of those, the station takes requests — or start with a $950 site health check and find out what you actually have.