Katie
MonroePhotography.

01 / THE BUILDA portfolio with work happening behind it

Katie Monroe is a photographer character in a Los Santos roleplay community. The site pairs an image-led public portfolio with private tools for managing the work behind it: photo uploads, collections, commission enquiries, and shoot scheduling.

My contribution covered the public portfolio, Worker API, admin console, and deployment. This is a FiveM community project, not a claim about a commercial photography client's results.

The presentation here uses an illustrated contact sheet and system diagrams. A verified full-resolution gallery capture is not available in the supplied handoff, so the illustration is not presented as the finished application.

02 / THE BUILDTwo deployments, different responsibilities

The historical build uses vanilla JavaScript and Vite for the public front end, deployed on Vercel. Its gallery, lightbox, motion, and story routing are ES modules rather than a React application.

A separately deployed Cloudflare Worker handles the API. Turso provides libSQL storage, R2 holds images, and the account describes signed JWT authentication for protected operations.

This keeps the public-facing assets separate from the operations that need secrets. The private console manages content; it is not simply a second visual theme for the gallery.

03 / THE BUILDUseful without configuration—not a blanket outage promise

The supplied loader has a concrete fallback. With no Worker URL configured, it returns bundled sample photos and categories. With a Worker URL, it requests photos and collections from the API.

The original article made a broader “never blank” claim. Its excerpt does not show recovery from a failed configured API request. The request helper and calling code would need to be inspected to establish that behavior.

The commission flow has a different responsibility. The source describes an explicit failure when there is no way to deliver an enquiry, rather than a success message for a message that was not sent.

04 / THE BUILDThe private tools need clear boundaries

The Worker uses a hand-written method-and-path router. Protected routes call a gated() wrapper; the article's examples include private collection access, private photo access, and uploads.

That makes the intended boundary visible in the excerpt. It is not proof that every route is correctly protected. The account also describes a Turso-backed fixed-window rate limiter and 164 tests across the Worker, front end, and admin console. That test count belongs to the June 2026 source, not this portfolio pass.

05 / THE BUILDWhat I would improve next

The original account identifies three areas for further work: simplify the router as it grows beyond its reported 31 routes, add image derivatives rather than uploading only source-sized files, and share some rendering code between the public site and admin console.

Those remain next steps in this account. No image pipeline, routing refactor, or expanded test coverage is being claimed as newly delivered.

The technical article shows the loader and routing excerpts. The client-facing article explains why useful fallback content and truthful delivery feedback need different treatment.