This system was used for the 2026 Taiwan Comprehensive University System New Faculty Professional Development Camp. I built the backend that connected QR check-in, attendee lookup, live metrics, seating state, walk-ins, and CSV export into a field-ready workflow.
Production use: August 28, 2026, at National Cheng Kung University International Conference Hall. official event page ↗. The production repository and database remain private; the public demo uses synthetic data and exposes no persistent write access.
Role
Full-stack operations tool development
Scope
QR check-in · live metrics · filters · seating
Status
Production system + privacy-safe public demo
Stack
Next.js · Cloudflare D1 · Drizzle
Year
2026
00 / Project framing
Project framing and engineering decisions
ProblemOn-site operations need fast check-in, search, filtering, seating confirmation and exception handling with immediate feedback.DecisionUse Next.js API → D1 → Drizzle for the data path, with QR workflows, 30-second metric refreshes and multi-dimensional filters.EvidenceVerified behavior includes 30-second refreshes, 5 filter dimensions, preregistration/onsite sources and CSV export; the public demo uses only 24 synthetic records.NextMulti-event support, real accounts/RBAC, audit logs, idempotency, multi-device conflict handling and an offline queue remain explicitly future work.
01 / Verified scope
A production backend, not only a concept demo.
The backend carries the operational data path between attendee and admin experiences so check-in, attendee records, seating state, and on-site exceptions stay consistent through the API and database. The portfolio exposes only a synthetic, non-production version.
30sautomatic admin dashboard refresh
5search, school, department, check-in and seating filters
2registered and on-site attendee sources
CSVexport of the currently filtered operations view
The public demo contains 24 fully synthetic records. That number describes the demo only, not the production event.
02 / User flow
From a QR token to an operations dashboard.
AttendeeQR token, identity and assigned seat
Check-in UIscan, confirmation and status response
Next.js APIattendee routes, admin actions and authorization
D1 + Drizzleattendance, seating and timestamp records
03 / Operations
Live DashboardTotal, checked-in, seated, walk-in and latest check-in metrics.Field FiltersLocate people by name, ID, institution, department and operational status.On-site HandlingThe private admin supports walk-in creation, seat changes and seating-state updates.Operational ExportExport the current filtered view as UTF-8 CSV for handoff and reporting.
04 / Privacy design
Public presentation is separated from production operations.
The production repository stays private; attendee tokens, names, institutions, seats and admin credentials are never published.
The public demo removes the original event logo, phone number and institutional identity.
The public admin view is read-only; scan simulation changes browser memory only and resets on refresh.
The portfolio does not connect to the production database or expose writable administration endpoints.
05 / Public demo
An interactive product surface, not only a static screenshot.
Captured during the site build by opening the public demo in Chromium. Every person, organization, seat and token is synthetic.
The strongest evidence is that the backend entered a real event workflow.
This project goes beyond a QR component or portfolio demo. The backend I built supported a real event and connected attendee/admin flows with APIs, storage, filtering, exception handling and export.
