All projects

06 / Full-stack web application

StudentEvents

A ticketing-system prototype developed in connection with After State Events. It was previously deployed and used by real users; the project is now paused, and current production availability is not claimed.

Status
Paused prototype
Scope
Public, admin, worker, and API flows
Context
After State Events

Verified source scope

A real prototype with an uneven implementation history.

The repository contains a public event interface, event-detail and checkout pages, administrative and worker interfaces, and Node/Express code for database-backed event and authentication flows. It also contains ticket/QR and payment-related implementations alongside mock paths, fallback code, and conflicting completion reports.

  1. 01Implemented source: public event browsing, management interfaces, API and authentication code
  2. 02Partially implemented or inconsistent: ticket purchase, payment, email, and deployment paths
  3. 03Specified and explored: QR-code tickets, validation, and broader administration workflows
  4. 04Not published here: participant records, credentials, payment details, or private operational data

Lessons & disclosure boundary

Completion labels need evidence, not optimistic documentation.

The useful lesson is broader than a feature list: interfaces, server code, third-party services, operational processes, and real-world testing have to agree before a system can be called complete. This case study therefore distinguishes inspected source from original specifications and historical deployment claims.

A repository link is intentionally withheld until legacy credentials, demo accounts, test data, and deployment material receive a separate security review.

Next project

AI Assistant / Kingdom System

A personal system for organising information, work, and AI-assisted routines.

View the Kingdom System