Skip to main content

Client project

Legal Confetti 2026

Livestream microsite and operations dashboard for Swire Coca-Cola Vietnam

01

Project overview

CompletedAug 2026 – Sep 2026· Client: Swire Coca-Cola Việt Nam

An event microsite with a livestream, an admin page for the operations team and a read-only report for the brand. The system was designed for about 2,000 people, and the event has finished.

02

Context and problem

A brand event needed three things that share one API: a page for the audience to watch the livestream, a control page for the operations team, and a report page for the brand. The timeline was short, and the agency had already provided the design.

03

Scope and requirements

  • Three user groups, one flow each: the audience watches the livestream, the operations team runs the event, the brand reads the report.
  • The audience registers and signs in to enter the live room; the room has video, a chat, a quiz minigame and a leaderboard.
  • The brand may only view and not control, so the report page is a read-only version kept separate from the admin page.
  • Built exactly to the design supplied by the agency; with a tight timeline the scope was fixed early.

04

My role and responsibility

I delivered it on my own: analysed the usage flow of each user group, clarified requirements, wrote documents, coordinated AI tools in implementation, then reviewed and accepted the result.

Where AI helped. AI tools wrote most of the code from a plan I approved. I am responsible for the requirements, access control, review, testing, acceptance and handover.

05

System analysis

Roles and permissions

  • Microsite

    Audience

    Register, sign in, watch the livestream, chat, play the quiz minigame, see the leaderboard.

  • Admin page

    Operations team

    Start and stop sessions, pick the question set, open and close questions, moderate the chat, see the ranking.

  • Read-only report page

    Brand

    See registration, score and player figures; cannot control the event.

  • Next.js exported as static files on Cloudflare Pages; the API runs on Cloudflare Workers with data in Cloudflare D1; the livestream is delivered by Cloudflare Stream.
  • One dashboard codebase produces two products, the admin page and the brand’s read-only report page, depending on an environment variable.
  • There is an architecture document for developers, an overview document for the brand, and a page that records the project status and deadlines.

06

Decisions and trade-offs

  • Keep the read-only report separate from the admin page, and enforce access at the API

    Why
    The brand only needs to see figures and must not control the event. Read-only access is blocked on the API side (it returns a 403 error), which is stronger than only hiding buttons in the interface.

07

Testing and acceptance

  • Automated tests cover the server side (the API).
  • A checklist follows the milestones of the event (registration, rehearsal, live) so each item can be checked before going on air.

08

Verified outcomes

  • Completed and used in the event.
  • The system was designed for an expected audience of about 2,000 people; I do not have actual attendance figures to publish.

09

Technology

  • Next.js
  • Cloudflare Workers
  • Cloudflare D1
  • Cloudflare Stream
  • Cloudflare Pages