A contact form, and too much Git LFS
The site got a working contact form, and the robot model came back out of Git LFS after it ate the bandwidth.
Number 09
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.
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.
Scrolling runs on Lenis and GSAP ScrollTrigger, and the whole site is a React and Vite app on Vercel.
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.
The site got a working contact form, and the robot model came back out of Git LFS after it ate the bandwidth.