Portfolio platform · Previous version

I designed and built my previous portfolio around two ways to explore the same work: browse the pages or ask an assistant.

One collection of content

Projects, career entries, and photographs were available through server-rendered pages. The assistant used the same content for retrieval and navigation. Common lookups resolved without a model call, and browsing remained available when generation was unavailable.

Built for failure states

The architecture addressed interrupted streams, finite generation budgets, accessibility preferences, and controlled image delivery.

This case study describes the earlier Astro and Cloudflare implementation. The current portfolio is a separate Next.js and Railway rebuild.