Landing Experience Development

May 2026 - Jun 2026

Role: Full-Stack Developer

Landing Experience Development thumbnail
Tech Stack

Overview

This project covered the public-facing landing experience for Rides Collective. The work was not about building an isolated promotional page, but about translating discussions from multiple client stakeholders and the internal event team into one structured visitor flow with clearer menu logic, event information hierarchy, and responsive storytelling.

In Collaboration With: Internal Rides Collective Team and Multi-Client Stakeholders

Responsibilities

  • Mapped the landing menu structure from early stakeholder discussions
  • Translated multi-client direction into a cleaner public-facing visitor flow
  • Built responsive frontend sections for event storytelling and navigation clarity
  • Connected landing data flow with Supabase-backed content and utilities
  • Refined the page structure to support event-day usability across devices
  • Handled iterative revisions together with the internal team before launch

Outcome

The result was a more coherent public landing experience that could explain the event more clearly, organize the menu structure better, and support event visitors without feeling fragmented. It also created a stronger public foundation for the admin and post-event phases that followed.

Detailed Breakdown

The section above is optimized for fast recruiter review. If you want the full implementation context, open the details below.

Rides Collective needed a public entry point that could represent one shared event identity while still accommodating input from multiple client stakeholders. Without a deliberate landing structure, the result would likely become a crowded page with weak flow between sections, unclear menu priorities, and a less convincing event narrative.

The solution was to treat the landing page as a guided event experience instead of a simple information sheet. I helped shape the menu logic, page order, and responsive delivery, then implemented the frontend flow on a Supabase and Vercel stack so the public layer could stay clean, fast, and easier to iterate with the internal team.

Primary Flow

01

Stakeholder discussions are translated into a clearer menu structure so the landing page reflects the event priorities more cleanly.

02

Public-facing sections are arranged around event storytelling, practical information, and visitor navigation needs.

03

Responsive behaviors and section refinements are iterated with the internal team until the landing flow feels stable enough for launch.

The landing experience became the public layer of the Rides Collective event ecosystem. It had to look polished, but it also needed to support real visitor orientation, section hierarchy, and multi-party content alignment instead of acting as a decorative microsite only.

Implementation Flow

01

Menu and section priorities are shaped from collaborative discussion so the page structure supports the event narrative more intentionally.

02

Frontend delivery is implemented with responsive layouts and cleaner section transitions to keep the experience usable across devices.

03

Supabase-backed data and Vercel deployment are used to keep iteration lightweight while the content direction continues to evolve near launch.

Implementation Details

  • Public-facing event landing architecture
  • Collaborative flow planning with internal team and client stakeholders
  • Responsive frontend implementation for event storytelling
  • Supabase-backed content and utility support
  • Vercel deployment for faster iteration and delivery
  • Iteration loop focused on menu clarity, section hierarchy, and event-day usability

Some discussion details have been generalized because the planning phase involved internal collaboration across multiple parties.

Explore More Projects

A few more top picks that show adjacent product, platform, and operations work across the portfolio.

View All Work