Web Platform Scaffold
One browser app for the store, the studio, the admin surface, and the player runtime.
This first scaffold is focused on the PC-first web shell: a clean Next.js app, Supabase wiring hooks, and a playable runtime surface we can evolve into canonical story playback and Ren'Py import preview.
Catalog
Catalog
Storefront rails, episode merchandising, and release positioning.
Player
Player
Browser-native runtime shell with a playable sample episode flow.
Studio
Studio
Importer-first authoring surface with Ren'Py fixture awareness.
Admin
Admin
Vendor operations, content review, and entitlement control points.
Immediate Build Focus
- Apply the first Supabase migration and confirm the admin readiness checks turn green.
- Wire Supabase auth and the first vendor/project CRUD flows.
- Define the canonical story format the importer will emit.
- Start the Ren'Py import pipeline against the local public fixtures.
- Replace the demo runtime data with canonical project playback.
Why this shell matters
Shared browser surface
Storefront, creator tooling, admin operations, and runtime all live in one deployment model instead of diverging into separate executables too early.
Importer-ready runtime path
The player route gives us a concrete place to swap in canonical imported story data as soon as the Ren'Py converter starts producing fixtures.
Supabase-first backend seam
Public env detection and Supabase client helpers are already in place, so auth, projects, saves, and import jobs have a clean landing zone.
PC browser assumptions
This shell is tuned around desktop keyboard and mouse use, which keeps the first runtime loop tighter while you handle platform setup outside the repo.