Number 09

ElectroLights website

The website for my FTC team, ElectroLights 30686, with live match data from FTCScout, a 3D model of the robot, and a members-only portal.

ShippedDesignSoftware2026
Role
Sole developer. Designed and built the site, the live match data, the 3D robot viewer, the contact form and the team portal.
Built with
  • React
  • TypeScript
  • Vite
  • Tailwind
  • GSAP
  • Three.js
  • Supabase
Started
Apr 2026
Finished
Jun 2026

Story

The team’s first site was a single HTML page a teammate made. Most FTC team sites are a template with a photo and a sponsor list. I wanted ours to show the team the way we’d show it to a judge: the robot you can turn around, the matches we’ve played, and the outreach we’ve done.

It’s also our internal tool. Behind a login there’s a portal for the team.

How it works

  • Robot: an interactive Three.js model of Vectair, compressed with Draco, with CAD downloads.
  • Matches: live data from FTCScout, with an OPR dashboard, field diagrams and charts.
  • Outreach: a timeline and photo carousel of the workshops and FLL teams we’ve mentored.
  • Sponsors: a bento grid with each sponsor’s own colour on its card.
  • Contact: a form that sends through a Supabase Edge Function and Resend, rate-limited so it can’t be spammed.

Scrolling runs on Lenis and GSAP ScrollTrigger, and the whole site is a React and Vite app on Vercel.

What broke

The 3D model of the robot and the video of our autonomous were too big for Git, so I moved them to Git LFS. Then every Vercel deploy pulled them again and burned through the LFS bandwidth.

I took them back out of LFS and committed them as plain files, served straight from the site, and deploys went back to normal.

Devlog