A closer look at the work.

Problem: Event information needs to stay consistent across a main website, individual brands, festivals, and app experiences.

Build: A WordPress content model and APIs feeding the public frontends, themed brand sites, festival microsites with an installable PWA shell, and an Appmiral event feed.

Current state: These components are implemented across related repositories. Release status varies by frontend; not every part is presented as live.

Problem: Ticketing, talent booking, and staff onboarding are connected operations with different workflows and responsibilities.

Build: Rosie handles ticketing and event reporting. Judy manages talent-booking opportunities, holds, offers, and festival planning. Elroy focuses on mobile onboarding and HR review.

Current state: Rosie documents a reporting beta; Judy documents a booking application with beta authentication. Elroy is an onboarding prototype with a working backend slice and mocked vendor integrations. These are not a uniformly production-ready suite.

Problem: A restaurant needs a public presence that can grow beyond a splash page without rebuilding its content foundation.

Build: A Next.js frontend over Payload and Postgres, with reusable page blocks and an event-publishing experience.

Current state: The READMEs describe the splash as deployed and frozen while the full frontend awaits cutover. The full site still has launch prerequisites; it is not presented here as launched.

Problem: An events business needs a clear way to explain its service disciplines and show the work behind them.

Build: A Next.js and Payload website with editable pages, service disciplines, case studies, and media.

Current state: The website implementation is present. A current launch or operating status is not established by the available documentation.

Problem: Related applications need a consistent way to request AI assistance with the right context and model boundaries.

Build: A first server slice for task routing, approved-model selection, fallback handling, and transcript references, with a shared client and synthetic demo.

Current state: The README explicitly describes a working first slice, not a deployed production service. Tool execution, streaming, and a frontend remain later work.

Problem: Fan questions need useful answers and a clear handoff when self-service cannot resolve them.

Build: A persistent support inbox, searchable help center, knowledge-gap tracking, and an assistant workflow with human handoff.

Current state: The README documents a locally working MVP. Provider adapters exist, but live provider accounts have not been connected or exercised in that checkout.

Problem: Even a small personal event can benefit from a coherent invitation and RSVP experience.

Build: A themed event page with RSVP handling and ticket-email generation, backed by a lightweight application and database.

Current state: A documented personal project. It is shown here for the interaction and workflow design, without publishing event details or guest information. Current hosting status is not verified.

Problem: A themed quiz needs both an easy way to write questions and a board that is practical to run with a group.

Build: A game library and clue editor, duplication and import/export, a playable board, team scoring, Daily Doubles, and Final Jeopardy wagers. Game progress survives a browser refresh.

Current state: The README documents the implemented game and hosting workflow. This is a personal game experiment; the portfolio image uses neutral demo questions and team names.