Crash Carts

Why I built it

I wanted to explore how procedural training can be made more memorable through focused, scenario-based web interactions.

What it does

• Sketches a training workflow for emergency cart readiness.
• Uses checklists, scenarios, and practice flows as the core interaction ideas.
• Frames simulation as a teaching aid rather than a generic dashboard.

Tech stack

Build / Deployment

App type

Standalone training/demo app

Code location

Separate project materials

Front end

Web app demo

Deployment

crashcarts.gavinnesom.com

Public URL

https://crashcarts.gavinnesom.com

Notes

Intended as a focused training demo rather than a general-purpose app.

Architecture / How it works

• This is a focused standalone web demo rather than a feature inside the portfolio app.
• The portfolio links out to the public demo while keeping the training app itself separate.
• The project stays separate from the portfolio so training scenarios and app logic can evolve independently.

What I built

• A project direction for emergency readiness training.
• Interaction ideas for checklists, procedural recall, and scenario practice.
• A demo structure that can become a standalone training app.

What I learned

• How training tools need to respect pressure, recall, and real-world constraints.
• Why simulations should teach decisions, not just display information.
• How procedural learning can benefit from small focused web tools.

Current status

Crash Carts has a public standalone demo at crashcarts.gavinnesom.com.

Next steps

• Define the first small training scenario.
• Prototype a focused check-flow before adding larger simulation features.
• Refine the live demo based on review and training-use feedback.

Links