Views
Content Platform
2025-2026Live
A platform where each strand of an art studio's programme — courses, events, games, shop — is a module on one shared core, plus the admin the studio runs it all from. Next.js + Supabase. Live.
Move the mouse: Puppet followsTap the picture: Puppet walks over
Views is the platform for an Italian art studio that does not run one business but several: a course school, a public events programme, interactive games and a shop. Each strand needed its own front end and its own logic, and each would have been a separate quote to a separate agency. What it actually needed was one system where a new strand is a configuration, not a project.
Underneath it is a monorepo with a shared core — auth, data access, design tokens and a common admin shell — with the experiences as modules on top. Courses carry booking with a waitlist and participant export; the events programme has mixed photo and video galleries that take both uploaded files and external links behind one player; the shop carries product management.
The business side is the admin the studio runs day to day: dashboard, analytics and a newsletter channel, over a Postgres schema designed and migrated alongside it. Built solo — schema, back end, front end, admin UX and deploys — and live in production, with the owner publishing the whole programme without a developer.
- 01Shared core layer — auth, data access, design tokens, common admin shell
- 02Per-experience modules on that core: courses, events, games, shop
- 03Course booking with waitlist and participant export
- 04Events media — mixed photo/video galleries, uploads and external links in one player
- 05Admin CMS the studio runs day to day: dashboard, analytics, newsletter
- 06System architecture and schema design (Supabase/PostgreSQL) with RLS
- 07Next.js App Router — server components and server actions
- 08Vercel deployment with ISR and cache invalidation