5-Minute Walkthrough

The Engineer.
The Architecture. The Plan.

Everything you need to evaluate this candidacy -- in five focused sections.

Self-Taught. Battle-Tested. 28 Years Deep.

Learned to type on a typewriter. Learned to code hacking computer labs. Bought books off Amazon before Amazon sold anything else. Spoke at DrupalCons around the world. Created the #3 theme in all of Drupal. Contracted 7 years before they finally said yes. Published author. Principal Engineer. Startup founder. This is the trajectory.

~1996
Typewriter to Terminal
Learned to type on a typewriter. Found a college computer lab and never came back out. Taught myself HTML and JavaScript hacking terminals after hours while everyone else was at parties. No bootcamp. No tutorial. Just a blinking cursor and the kind of obsession that doesn't sleep.
~2001
Amazon.com Was Still a Bookstore
Ordered every programming book Amazon carried -- back when that's all they sold. CSS, PHP, JavaScript, server administration. Earned mastery the hard way: reading covers to covers, building things that broke until they didn't, and doing it all over again on a dial-up connection in the mountains of Colorado.
2002-08
In the Trenches
Years of grinding across both hardware and software industries. Denver, Boulder, then east coast. Web agencies, marketing departments, internal tools teams. Took every project that would teach me something new. Learned that the gap between "knows how to code" and "ships production software" is measured in broken deployments and all-nighters. Built the calluses that make the rest of this timeline possible.
2009-21
Found Open Source & Hit the World Stage
Discovered Drupal, fell into the open source community, and everything changed. Created the Omega base theme -- it became the #3 most-used theme in all of Drupal. Started speaking at DrupalCons around the world -- London, Paris, San Francisco, Denver, Portland, Montreal, and too many camps and summits to count. Co-authored the Definitive Guide to Drupal 7. Spent over a decade contributing to Drupal core and contrib, building tools used by hundreds of thousands of sites worldwide. My final DrupalCon talk was on Web Components at Portland 2021 -- lovingly known as CovidCon. Our first time together in years -- karaoke bars, spreading handshakes, and hating masks like everybody else. Out of 50+ Phase2 employees, 30+ caught COVID in the fallout. I was the lone soul who tested positive and got stuck in Portland for 10 days. Still shipped the talk.
2011-18
Phase2: 7 Years Proving It as a Contractor
Began a 7-year contracting partnership with Phase2 Technology. Led frontend teams. Brought responsive design to every Drupal project in the organization. Shipped for major universities, state & federal government, major TV networks, and multi-brand platforms with dozens of themes and applications running on shared codebases. They asked me to come on full-time for seven straight years. I liked my independence. They kept asking. I kept delivering.
2018-24
I Finally Said Yes. Then Principal Engineer.
After seven years of saying "not yet," I finally took the full-time offer. Rose from Software Architect to Engineering Manager to Principal Engineer. Led the creation of Outline -- a Web Components design system that standardized frontend development across the entire organization. Onboarded teams, unified tooling, and shipped components consumed by Drupal, React, Angular, and .NET projects alike. In 2023, Dries Buytaert highlighted Omega at DrupalCon Portland as one of a select handful of pioneering low-code/no-code solutions -- over a decade after its creation.
2026
Clarity House Press -- The Startup
Founded Clarity House Press and built the entire technology platform from scratch. Next.js 16, TypeScript strict mode, Supabase backend, AI-orchestrated content pipelines with 280+ specialized agents, automated LaTeX book production, and a full publishing operations stack. Not a WordPress blog -- a next-generation content platform designed to scale, designed to license, and designed to prove that one engineer with the right architecture can outbuild a team of twenty. Currently exploring paths to either build out the platform commercially or bring investors to the table.
Now
WC-2026 -- The Late-Night Vibe Code
This project. A late-night vibe coding exercise that turned into a complete enterprise healthcare web component architecture. 28 years of design systems, Web Components, Drupal integration, and hard-won opinions -- distilled into one prototype. 10,000+ lines of planning. 5 immersive showcase pages. A full documentation hub. Built in a sprint because after doing this for three decades, the architecture just flows. This site is what happens when experience meets obsession at 2am.
0
Years Shipping Code
0
Years at Phase2
0
DrupalCons Spoken
#3
Theme in All of Drupal

The WC-2026 Architecture

A complete enterprise web component library designed for healthcare -- framework-agnostic, Drupal-integrated, fully typed, rigorously tested.

Lit 3 Components
TypeScript + JSDoc
Shadow DOM encapsulation
CEM Pipeline
Custom Elements Manifest
Single source of truth
4 Outputs
Automated generation
Zero manual sync
Storybook 10
Starlight Docs
IDE IntelliSense
Drupal Tooling
wc-content-card.ts -- Drupal-ready component
type CardVariant = 'default' | 'featured' | 'compact';

@customElement('wc-content-card')
export class WcContentCard extends LitElement {
  /** Card visual style -- maps to Drupal view mode */
  @property({ reflect: true })
  variant: CardVariant = 'default';

  /** Article heading -- from node.title */
  @property()
  heading = '';
}

This System Is the Proof

How I organize, delegate, and lead is not a talking point. It is the documentation site you are reading right now.

Structured Architecture
6 planning documents, 10,000+ lines, organized by domain. Architecture, components, tokens, documentation, Drupal integration -- each with its own owner and clear scope.
Multi-Stakeholder Design
Three audience tracks: component builders get code patterns, Drupal teams get TWIG examples, designers get token documentation. Every audience has a tailored path.
Execution Velocity
5 immersive showcase pages. 22 documentation pages. A complete monorepo with Turborepo orchestration. All built in a single sprint -- ready for production Day 1.

Every Tool Chosen for a Reason

No hype-driven decisions. Every technology was selected based on measurable advantages, ecosystem maturity, and long-term viability.

Technology Version Why
Lit 4.x 5KB runtime. Native web platform. No virtual DOM overhead. W3C standards-based.
Vite 7.x Instant HMR. Rolldown-powered production builds. 10-100x faster than Webpack.
Storybook 10.x Vitest integration. CEM-powered autodocs. Visual regression with Chromatic.
TypeScript 5.7+ Strict mode, zero any. CEM generates types. IDE autocomplete for TWIG authors.
W3C DTCG 2025.10 First stable spec. Three-tier tokens. Multi-brand theming. Figma sync.
Drupal 10/11 Zero coupling. CEM generates TWIG stubs and libraries.yml. SDC-compatible.

The Ask

I am looking for a tech lead role where I can architect, build, and ship an enterprise web component library for a healthcare organization. This documentation system is not a proposal -- it is a working prototype of how I lead and deliver.