Stable Summit

Product: Stable Summit
Timeline: 2024 to 2026
Project Type: Conference website
Stack: React, TypeScript, Vite, GSAP, Lenis, Tailwind CSS, TanStack Query

Project Overview

Stable Summit is a global conference about stablecoins, held in cities like New York, Cannes and London.

I joined the project in 2024 and became its main developer. Over two years I rebuilt most of its pages, added motion throughout, and moved its content from hard coded files to live data from the Party Action People admin platform, which I also built.

Key Features

• A home page with an animated opening sequence and scroll driven sections
• Speakers with a detail page for each one, and the sessions they speak in
• An agenda grouped by track, with filters, including workshops
• Pages for sponsors, becoming a sponsor, applying to speak and the venue
• An archive of past talks, filtered by city
• Speakers, sponsors and the agenda loaded live from the admin platform
• A preview version of the site where the team checks pending changes before they go live

Tech Stack

• React, TypeScript and Vite: The site
• GSAP and ScrollTrigger: Timelines and scroll driven animation
• Lenis: Smooth scrolling
• TanStack Query: Loading and caching the live content
• Tailwind CSS: Styling

Key Technical Challenges

1. Smooth scroll that agrees with scroll animations

Smooth scrolling moves the page on its own clock, so scroll animations fired at the wrong moment. I ran both on one animation loop, and every smooth scroll step tells the scroll triggers to update. Now the effects line up with the scroll, frame by frame.

2. A video archive with no runtime cost

The archive lists hundreds of past talks from YouTube. Calling the YouTube API on every visit would be slow and could hit its limits. I wrote a script that pulls each event's playlist once, adds talks that were uploaded outside the playlist in the right place, and saves it all to a data file. The archive loads instantly.

3. From hard coded content to live data

Speakers and sponsors used to live in files inside the code, so every change needed a developer. I moved the site onto the admin platform's API, with separate live and preview modes, so the team now updates the site themselves.

Conclusion

Stable Summit is the site I have spent the longest on in this family. It is where I worked out the motion and data patterns that the other summit sites now share.