Behind the gallery.Useful before
the API is configured.

01 / FIELD NOTESTwo halves, two deployments

The public site is vanilla JavaScript built with Vite and deployed on Vercel. ES modules handle the gallery, lightbox, motion, and story routing. It is not a React front end.

The API is a separate Cloudflare Worker with its own deployment. Turso provides libSQL data storage; R2 holds the photos. The account describes signed JWT authentication and a private console for managing the portfolio.

The separation puts the public assets on one side and operations that need secrets on the Worker side. It also means API configuration is a real condition the front end has to account for.

02 / FIELD NOTESRead the condition before naming the fallback

The loader checks whether a Worker URL exists:

export async function loadPortfolio({ workerUrl = DEFAULT_WORKER } = {}) {
  if (!workerUrl) return { shots: SHOTS, cats: CATS, collections: [], source: 'local' };
  const [{ photos }, { collections }] = await Promise.all([
    getJson(workerUrl + '/api/photos'),
    getJson(workerUrl + '/api/collections')
  ]);
  return { shots: photos.map(mapPhoto), cats: CATS, collections, source: 'remote' };
}

With no workerUrl, it returns SHOTS, CATS, an empty collections array, and source: 'local'. With a URL, it starts two getJson requests and returns mapped remote photos and collections after those results resolve.

That supports a precise claim: the gallery has a bundled-content path when the API is not configured.

The original title claimed the portfolio would never show a blank page even if the backend was down. The shown function contains no recovery branch for a configured request failure. The getJson implementation and its caller are not shown, so their behavior cannot be settled from this excerpt alone.

Useful during setup is a narrower claim than resilient during an outage. The shown condition supports the first; the second needs a separate check.

03 / FIELD NOTESAn enquiry cannot use the gallery's fallback

Showing bundled examples can make a gallery useful during setup. It does not make an undelivered enquiry useful to the person who wrote it.

The original account says the commission form fails explicitly when there is no backend, rather than pretending the message went through. The supplied loader does not contain the form implementation, so this remains a documented behavior to check against that code.

The two paths should not be collapsed into “hide the error.” One supplies sample content. The other needs to tell the user whether their action was completed.

04 / FIELD NOTESThe protected routes are visible in the router

The Worker matches method and path directly. In the excerpt, each protected operation is passed through gated():

if (path === '/api/admin/collections' && method === 'GET')
  return gated(request, env, listAdminCollections);
if (method === 'GET' && path === '/api/admin/photos')
  return gated(request, env, getAdminPhotos);
if (method === 'POST' && path === '/api/upload')
  return gated(request, env, upload);

The wrapper makes the intended access boundary visible in these examples. It does not prove that the entire router is correctly protected. The complete routes and the wrapper's behavior would need review for that claim.

The account also describes a Turso-backed fixed-window rate limiter. It is a rate-control mechanism in the documented design, not a claim that the application cannot be abused.

05 / FIELD NOTESTest coverage and the next maintenance work

The original write-up reports 164 tests across the Worker, front end, and admin console. Those tests were not rerun in this editorial update.

At that point, the router had a reported 31 routes and was getting long. A smaller matcher was one of the proposed improvements. Image uploads still went straight to R2 without resizing, and the admin console shared no rendering code with the public site.

Those observations give the next work a concrete shape: simplify route matching, add appropriate image derivatives, and reduce duplication where the two interfaces overlap. The source does not establish that those changes have since shipped.

06 / FIELD NOTESThe useful distinction

A missing setting, a failed request, and an undelivered message are three different conditions. The value in this example is making the known behaviors visible—and leaving the unproven behavior as a question for the actual code.

Explore the Katie Monroe project, or read the client-facing explanation of why those distinctions matter.