ROE KAPARA.

What problem does the ROE KAPARA website solve?

1. For who

   Artists and fans who need an owned house — tour, merch, catalogue — not a link-in-bio.

2. What this made possible

   A singles-driven cadence breaks any site that hard-codes the current release, so the discography is data — a new drop takes the fold without a redesign, and fans route to streams, videos, merch and show alerts.

3. The problem

   His audience lives on platforms he does not control, and the release rhythm is singles rather than albums. People landing from socials needed a home base that can swap the featured drop, hold the catalogue behind it and still route to listen, watch, shop and tour — not a static link dump that goes stale between releases.

4. The approach

   Framed as a roadside screen: releases live in a typed data file so a new single can take the fold without touching the design. GSAP runs the intro curtain, the labelled page-wipe transitions and a pinned horizontal scroll through selected works, while streaming embeds and a video modal keep listening and watching on the site.

5. What shipped

   Live at roe-kapara.netlify.app on REACT + VITE · GSAP · PINNED SCROLL.

See this stack · Builds