Project 02 / 13

Web Development

District Studio

The platform this site runs on. A public studio site, a customer portal where clients follow their orders and tickets, and a staff dashboard that runs the support desk, orders, portfolio and the Discord bot — one Next.js application on one PostgreSQL database.

Support is ticketed rather than lost in Discord threads: every request gets a reference, a tracked status and email notifications both ways, and internal staff notes are filtered out in the query layer so they can never reach a customer.

Security is structural. Authorisation is checked at the edge and again against the database on every protected request, customer isolation is part of every query, and there is no public path to an admin account.

Project
District Studio
Type
Web Development
Role
Design / Full-stack development
Stack
Next.js · React · TypeScript · PostgreSQL · Prisma · Tailwind
Status
Live
Year
2026
district.studio.platform
District Studio admin dashboard: customers, open tickets, orders and revenue

A What was built

  1. 01

    Ticketed support

    References, statuses, priorities, internal notes and email notifications in both directions.

  2. 02

    Customer portal

    Orders with a progress rail, tickets, notifications and profile — isolated per customer.

  3. 03

    Staff dashboard

    Live figures, a fourteen-day ticket chart, customer directory, orders and an audit log.

  4. 04

    Portfolio CMS

    The work on this site is published from the dashboard, with image upload and cached reads.

  5. 05

    Discord bot control

    Tickets, applications and welcome messages for the District Bot, over a signed API.

  6. 06

    Security by construction

    Two-layer authorisation, rate limiting, bcrypt, origin checks and a strict image allow-list.

B Screens & artwork

Sign-in page with a sliding sign-in / sign-up panel
Fig. 01One sign-in for customers and staff — each lands in their own area.
Customer portal dashboard with orders, tickets and activity
Fig. 02The customer portal. Everything is scoped to the signed-in account in the query itself.
Staff ticket inbox with filters, priorities and statuses
Fig. 03The staff ticket inbox — search, filters, priorities and SLA-friendly statuses.
Order management table
Fig. 04Order management with fulfilment progress the customer can see.
Customer portal on a phone
Fig. 05Designed for phones, not shrunk onto them.

C Under the hood

Architecture
Next.js App Router · Server Components
Data
PostgreSQL · Prisma · tagged cache
Auth
Signed sessions (jose) · bcrypt
Motion
CSS only — no animation library
District Studio — District Studio