Portfolio Website

Case Study · In Progress

Overview

I’m building my portfolio as a product: a place where the work is clear, evidence is easy to find, and the story is honest about work in progress. This case study follows an ambiguous positioning question through a clearer strategy and into a locally implemented site.

I built the portfolio around stage-aware case studies, so a working product, a planning project, and this site can sit together without sounding equally finished. The goal is to show the reasoning, constraints, and proof that exist now.

Context & Problem

The project began with a positioning problem. I needed a portfolio that communicated more than tools or screenshots: how I clarify messy work and turn an early idea or manual workflow into something people can understand and use.

That changed the brief. The site needed to make my work legible across product, code, AI-assisted development, and data; give each case study an honest stage; and lead from a concise overview into the decisions behind it. The portfolio became a strategy for organizing evidence, not a decorative container.

Katey’s Role

I set the product direction and remain the final approver for the case-study structure, evidence hierarchy, project stages, privacy boundaries, and public-facing interaction. Research and AI-assisted planning help examine options; they do not replace decisions about what belongs in the work or how it is represented.

Evidence has to be accurate, readable, and safe to share. Private methods and prompts stay private; representative material is labeled honestly; and project-specific limits remain visible. The portfolio makes the difference between proof, context, and future work clear.

Process & Key Decisions

I started with reference research and comparison work rather than treating visual direction as a shortcut to a finished identity. Agence Foudre was a reference for expressive composition and movement, not a template to copy. I synthesized those lessons with the portfolio’s own needs: evidence-first case studies, readable long-form content, clear stage language, and privacy-aware media.

The selected direction uses expressive color in defined roles, sharp display type alongside readable long-form typography, and compositions where human context meets project proof. Motion is reserved for meaningful chapter shifts rather than added everywhere. Together, those choices give the site an energetic point of view while keeping evidence readable.

The most focused expression of that approach is the Decision Trail. It gives three recurring devices distinct jobs. Proof Marks add concise context directly to everyday evidence. Systems Thread appears when a genuine workflow or sequence needs structure. Builder Notes appear sparingly at a consequential decision, where a short first-person explanation adds meaning. They are not stacked around one object, because the evidence—not the visual device—should remain the thing a visitor notices first.

Optional detail — How the Decision Trail took shape

The signature layer began as three separate directions. I kept the strongest role from each instead of averaging them into an always-on style: a compact vocabulary for showing a decision, a process, or a useful note without turning every page into an annotation exercise.

Solution or Current State

The current local site includes a stage-aware case-study system, three accepted case-study routes, major-section navigation, inline proof, supporting disclosures, and a project-to-project loop. It remains In Progress—implementation progress, not a public launch—and will not become a Working Product until launch is independently verified.

The next work is to carry the system into more real content and refine how its typography, media, evidence, and movement work together across the site.

Evidence & Outcomes

The strongest current implementation evidence is local and bounded: repeatable build, content-contract, accessibility/parity, and headless-browser verification. Those checks inspect defined states and profiles; they do not establish deployment, publication, visitor response, user outcomes, or business impact.

Evidence is tiered. Essential reasoning and the strongest available proof stay in the main story. Supporting technical context, additional comparisons, and deeper decision history can be opened when useful. Representative, recreated, generated, or redacted material must say what it is and remain understandable with its disclosures intact.

Optional detail — What local verification means here

Local verification is a way to examine whether the site builds and whether its content and interaction contracts hold across the defined browser profiles. It is not a substitute for public release evidence. A private preview does not create a public URL, prove public readiness, or change the project’s stage.

Reflection & Next Steps

This work makes the portfolio’s standards visible: a case study should be clear about its decisions, evidence, and claims it is not ready to make. An in-progress project can show something real without borrowing credibility from a future launch.

The next chapter is evidence-led: carrying the system into more real content, refining the relationship between typography, media, and proof, and continuing to test whether the site makes complex work easier to follow. This is a record of work in progress—not a finished-story substitute.

Optional detail — Reference synthesis

The reference archive documents the comparisons, refinements, and selected directions behind the system. It shows what informed the work, what was set aside, and what remains validation work—not copied inspiration or a completed public experience.