gamma-youtube

As a developer I want to audit and align all color tokens, theme variables, and component styles across the scaffold so that there is full visual consistency between the scaffold pages and the completed design pages before feature development begins.

As a viewer I want a channel page that displays a creator's profile, challenge video library, subscriber count, and a subscribe button so that I can follow creators whose parkour content I enjoy and access all their videos in one place. Implement based on the existing Channel (v2) JSX design.

As a visitor I want to see an engaging landing page with hero section, feature highlights, user testimonials, and clear call-to-action buttons so that I can understand the platform's value and choose to sign up as a creator, sponsor, or viewer. Implement based on the existing Landing (v2) JSX design.

As a content creator (Azan) I want a recording session page that displays the active parkour route, live checkpoint timer counting down from 20 minutes, run attempt counter, and session notes so that I can track my progress during a challenge recording session. Implement based on the existing Recording (v2) JSX design.

As a content creator (Azan) I want a video editor page where I can upload footage, trim clips, add checkpoint overlays, insert time-limit countdowns, apply transitions, and add captions so that I can produce polished parkour challenge videos ready for publishing. Implement based on the existing Editor (v2) JSX design.

As a viewer I want a video page where I can watch a parkour challenge video, see checkpoint timestamps, like the video, leave comments, and view run statistics so that I can engage with the challenge content and community. Implement based on the existing Video Page (v2) JSX design.

As a viewer I want a personalized feed page that surfaces recommended parkour challenge videos, trending routes, and content from subscribed creators so that I can discover new challenges and stay up to date with my favorite creators. Implement based on the existing Feed (v2) JSX design.

As a sponsor/brand I want a contact page with a structured inquiry form capturing brand name, campaign goals, budget range, and preferred creator so that I can initiate a sponsorship conversation directly through the platform. Implement based on the existing Contact (v2) JSX design.

As a content creator (Azan) I want a gear setup page where I can log and manage my cameras (GoPro, drone), mounts, accessories, and equipment configurations so that I can track what gear was used for each recording session and challenge. Implement based on the existing Gear Setup (v2) JSX design.

As a sponsor/brand I want a deal page that shows partnership terms, deliverables, compensation breakdown, and a confirmation action so that I can review and formally confirm a sponsorship deal with a content creator. Implement based on the existing Deal Page (v2) JSX design.

As a content creator (Azan) I want a publishing page where I can set video title, description, tags, thumbnail, scheduled publish time, and visibility settings so that I can distribute my parkour challenge videos to my audience efficiently. Implement based on the existing Publishing (v2) JSX design.

As a content creator (Azan) I want a dashboard overview that shows my active challenges, recent video stats, upcoming scheduled routes, and quick-access links to Route Planner, Recording, and Publishing so that I can manage my content workflow from a central hub. Implement based on the existing Dashboard (v2) JSX design.

As a sponsor/brand I want an analytics page showing channel performance metrics including views, watch time, audience demographics, engagement rates, and challenge completion stats so that I can evaluate a creator's reach before confirming a partnership. Implement based on the existing Analytics (v2) JSX design.

As a content creator (Azan) I want a route planner page where I can map parkour challenge routes, set checkpoints, define a 20-minute time limit per segment, and save route configurations so that I can plan structured challenge videos before recording. Implement based on the existing Route Planner (v2) JSX design.

As a user I want to use a backend API for the personalized feed that returns ranked video recommendations based on viewer watch history, subscriptions, trending challenges, and engagement signals so that viewers receive a relevant and engaging content feed.

As a user I want to use a backend API for managing a creator's gear inventory including adding, updating, and retrieving equipment records and linking gear configurations to specific recording sessions.

As a user I want to use a backend API for serving landing page dynamic content including featured challenges, creator spotlights, and platform stats so that the landing page displays real and up-to-date information.

As a user I want to use a backend API for the creator dashboard that aggregates active challenges, video performance summaries, and workflow status so that the dashboard reflects real-time creator activity.

As a user I want to use a backend API that aggregates and serves channel analytics data including views, watch time, audience demographics, and engagement rates so that sponsors and creators can access accurate performance data.

As a user I want to use a backend API for the sponsor contact form that validates and stores inquiry submissions and triggers notification emails to creators so that sponsorship conversations can be initiated and tracked.

As a user I want to use a backend API that manages recording sessions including session creation, checkpoint event logging, attempt tracking, and timer state persistence so that recording data is captured and stored reliably.

As a user I want to use a backend API for creating, reading, updating, and deleting parkour routes including checkpoint coordinates, time limits, and difficulty ratings so that creators can persist and retrieve their planned routes.

As a user I want to use a backend API for video editing operations including clip upload, trim metadata storage, overlay configuration persistence, and export job queuing so that the editor can process and store edited video projects.

As a user I want to use a backend API for video publishing that handles metadata submission, thumbnail upload, scheduled publish job creation, and visibility management so that creators can reliably release videos to their audience.

As a user I want to use a backend API for the video page that serves video stream URLs, challenge metadata, checkpoint timestamps, like/dislike actions, comment CRUD operations, and view count increments so that viewers can fully interact with challenge video content.

As a user I want to use a backend API for sponsorship deal management including deal creation, terms retrieval, deliverable tracking, status updates, and deal confirmation workflow so that sponsors and creators can formalize partnership agreements on the platform.

As a user I want to use a backend API for creator channel pages that serves profile data, video library listings, subscriber counts, subscription toggle actions, and channel analytics summaries so that viewers can browse and subscribe to creator channels.