← back to work
001 / Selected work · Volunteer · Nonprofit · 2025—present

Straight Path Athletics.

Took a youth sports nonprofit off paper and a pile of scattered apps, onto one platform the volunteers can run themselves.

View live site
Client
Straight Path Athletics · youth sports nonprofit
Serves
200+ athletes · Flag Football & Basketball · Howard County, MD
My role
Technical Lead · diagnose, choose tools, get buy-in, implement · 450+ hrs
Stack
TeamSnap · Stripe payments
Live
straightpathathletics.com
hero image — game day / the live site
0
young athletes
0
programs
0
volunteer hours
0→1
tools consolidated
A nonprofit running on paper and a dozen scattered apps

Straight Path runs Flag Football and Basketball for 200+ kids in Howard County, Maryland. When I started, the organization was held together by whatever tool was closest to hand. A separate website. WhatsApp for parent communication. Paper forms for registration. Checks for fees. None of it talked to anything else, and keeping it all in sync ate the volunteers' time. The limit on growth was never demand. It was coordination.

Website
WhatsApp
Paper forms
Checks
Find the problem, choose the fix, get it approved

I'm the technical lead here, not the hired developer. The job is to watch how the community actually operates, find where it loses time or loses trust, and match each problem to a solution. I don't decide alone — I bring a recommendation to the organization, they approve it, and then I implement it. That approval loop is the point: a volunteer-run nonprofit has to understand and own its tools long after I've stepped back.

Diagnose
Recommend
Community approves
Implement
Mobile-first, payment-first

Two realities shaped every decision. Parents sign their kids up on a phone during school pickup, not at a desktop, so every flow had to be fast and obvious on a phone. And the whole exercise was pointless if fees couldn't be collected online. Looking good came a distant third, behind working on a phone and taking a payment.

Mobile-first
Register a kid in under a minute, on a phone, in a school pickup line.
Payment-first
If it couldn't take a fee online, nothing else about it mattered.
One platform instead of ten

The recommendation was to stop stitching tools together and move everything onto TeamSnap. It runs registration across all 5+ programs, processes fees and donations through Stripe, and handles parent communication and notifications. One system, in place of the website, the WhatsApp threads, the paper, and the checkbook — and one that a non-technical volunteer can keep running without me.

Website
WhatsApp
Paper
Checks
TeamSnap
Registration
Payments · Stripe
Parent comms
hover the platform to see what it replaced

The right answer wasn't a custom site. It was one consolidated, maintainable platform the people there could actually run.

From scattered to consolidated

The organization went from paper-and-pieces to fully online in a single season. Registration and payments that used to live on printed forms and checks now run through one platform. For a nonprofit whose entire prior presence was a Facebook page, going from invisible to discoverable and payable is the whole win.

registration on mobile
a program page
What stuck with me

The most useful thing I did on this project was not build anything. The right answer wasn't a custom site. It was seeing that a volunteer organization needed one consolidated, maintainable platform more than it needed bespoke code, and choosing the tool the people there could actually run. Knowing when not to write software is its own engineering decision.

002 / SELECTED WORKCORPORATE2024 — PRESENT

Synack Solutions

A 20-year-old IT services firm's first modern digital presence. 15+ pages, 6 service lines, built from scratch.

A 20-year-old firm with no online presence

Synack Solutions has been delivering IT services from Baltimore since 2005. Twenty years of work, real clients, real outcomes — and a website that hadn't kept up. For a B2B firm whose buyers Google before they meet, that's a credibility problem. Procurement teams pattern-match on digital presence, and an outdated site signals an outdated company.

The brief was to build a modern, professional site that showcased the firm's 6 service lines and supported new business development.

Editorial, not promotional

Most IT services sites read like marketing brochures — vague claims, stock photography, hero videos of generic office workers. I wanted Synack's site to read more like a publication: clean typography, structured content, scroll-driven pacing.

Decisions that shaped the build:

  • A 15+ page architecture with a clear hierarchy — service lines on top, supporting content below
  • Modular CSS organized into a maintainable folder structure so the firm could update content without me
  • AOS (Animate On Scroll) for restrained motion that gives the page life without being a distraction
  • Smooth scroll navigation that turns the site into one continuous narrative instead of a click-driven gallery
  • A client testimonials section grounded in real quotes, not stock language
Twenty years of business deserves a site that doesn't apologize for itself.

Vanilla stack, premium feel

I built the site in HTML5, CSS3, Tailwind, and vanilla JavaScript (ES6+). No React. No build step. The deliberate constraint: the firm should be able to hire any frontend developer in five years and have them edit the site without learning a custom stack.

Tailwind let me move fast on layout while keeping the bundle tiny. AOS handled animation declaratively, so adding motion to a new section was a single attribute, not a JavaScript file. The whole site loads fast, looks current, and will keep working long after I move on.

A digital presence that matches the company

For a firm that had been in business for 20 years with no modern web presence, the launch wasn't a redesign — it was a debut. The site now anchors the firm's business development across all 6 service lines, giving potential clients a credible artifact to evaluate before any sales conversation begins.

WHAT STUCK WITH ME

The hardest part of this project wasn't code — it was understanding what a 20-year-old company actually does and translating that into 15+ pages that don't repeat themselves. Senior engineers have a saying that the best feature you can ship is the one you don't ship. Mature businesses are full of features (services, programs, history) that newer companies haven't earned yet. Designing for that took more interviewing than coding.

003 / SELECTED WORKSMALL BUSINESS2025 — PRESENT

HKM Engineers

A construction engineering firm in Illinois. 3 service lines, 4-step client workflow, documentation-first design.

An engineering firm that did high-stakes work, invisibly

HKM Engineers does infrastructure work in Illinois — Construction Inspection, Construction Management, and Program Oversight across Transportation, Structures, and Facilities. Work that matters. Bridges, roads, public buildings. But for a firm bidding on public-sector infrastructure projects, an invisible online presence is a credibility ceiling. Procurement officers and partner firms expect to verify you before they call.

The brief: a documentation-first website that communicates technical credibility, not marketing flash.

Documentation-first, multi-page

Engineering firms aren't sold like consumer products. Their clients read carefully, compare specs, and look for evidence of capability before reaching out. I designed the site as a structured multi-page document:

  • One dedicated page per service line — no smushing three offerings onto a single brochure page
  • A 4-step client workflow diagram showing how a project actually moves through HKM — the kind of process detail procurement officers screen for
  • A project portfolio section grounded in real verticals (transportation, structures, facilities), not aspirational language
  • A consultation request flow that gives potential clients a clear path from “interested” to “in touch”
Procurement teams scan for evidence, not adjectives. The whole site is built around that.

Vanilla and durable

HTML, CSS, and JavaScript — no framework. A small firm shouldn't have to depend on a Node version or a build pipeline to maintain its website. The whole site is a folder of files that any developer can read, edit, and redeploy in an afternoon.

A web presence that matches the work

HKM now has a credible, structured online presence covering its 3 service lines across Illinois infrastructure verticals. The site supports business development the way the firm actually wins work — by demonstrating process, not by selling.

WHAT STUCK WITH ME

Different industries read websites differently. A nonprofit's parents skim for trust signals on a phone. An IT firm's clients pattern-match on professionalism. An engineering firm's procurement officers read for evidence of process. Same medium, three completely different rhetorics. Designing well means knowing which rhetoric you're writing in — and that's something I want to study formally, not just pick up by repetition.