NASCAR · Next League, 2026
Reusable systems for a changing race season.
Shared frontend systems behind live NASCAR team websites, including Hyak Motorsports, 23XI Racing and Trackhouse.
- Role
- Frontend engineering within a shared platform team.
- Stack
- Astro, React, TypeScript, vanilla-extract, Contentstack
- Status
- Live team sites · Ongoing platform development
Hyak Motorsports: team identity and editorial content on the live NASCAR platform.
Context
Each racing team has its own identity, drivers, partners and editorial priorities. The shared NASCAR platform brings those distinct brands together through reusable content, schedules, standings and series-aware interfaces. Hyak Motorsports, 23XI Racing and Trackhouse are three live examples of the platform Danny contributes to at Next League.
What I did
- Developed reusable content and driver interfaces, responsive styling and design-token integration.
- Built schedule and results components covering upcoming races, completed results, weekend sessions, winners and broadcast information.
- Extracted shared series-selection behavior, developed power-rankings cards and maintained repository conventions and engineering guidance.
Engineering decisions
A schedule changes as a weekend unfolds. My frontend work connects upcoming races, weekend sessions and completed results while preserving the supplied series, season and content identity.
- Shared contractsUse the existing content types and supplied schedule groups.
- Reusable viewsCompose series selection, race cards, sessions, winners and broadcast details.
- Team interfacesApply shared design tokens and responsive layouts within each team site.
- Tradeoff
- Shared components need to handle more than one populated design. Broadcast providers can wrap, sponsor images can be absent, and results need to stay readable at narrow widths. I worked through those states rather than creating a separate layout for every team.
- Result
- Reusable schedule and results components within the Next League platform. Hyak Motorsports, 23XI Racing and Trackhouse show the wider team product in production; my contribution is its frontend systems and interfaces.
Find the existing component first.
The repository’s guidance makes reuse a deliberate discovery task: inspect the nearest component, its types, styles and callers before adding a new abstraction.
Keep interactivity proportional.
Astro supports server-rendered content, with React where the interaction needs it. Shared styling and types keep feature work aligned with the platform.
Review the edge states.
Schedule work includes missing content, provider wrapping, accessible sponsor identity and responsive results. The implementation must make sense beyond a populated design example.
Scope
Frontend contribution within the Next League platform team. The live sites show the shared team product; branding, editorial content and platform delivery involve other contributors.
Reviewed contribution history and shared-component changes, and visited the live Hyak Motorsports, 23XI Racing and Trackhouse sites. The gallery shows their actual public interfaces, including the Hyak schedule and Trackhouse standings.