Case studies / portfolio section #7

New issue

Open

opened 2026-05-05 12:04:12 +00:00 by frank · 0 comments

frank commented

2026-05-05 12:04:12 +00:00

Owner

Build dedicated case-study pages for each shipped product, going deeper than the homepage Field Notes blurbs.

Scope per case study:

Problem / context (what existed before, why it was inadequate)
Approach and key technical decisions (stack choices, tradeoffs)
Screenshots (more than the single hero shot on the homepage)
Outcomes / metrics where available (users, performance, cost savings, etc.)
Tech stack callout
Live link

Initial pages:

/work/cookslate — Cookslate (recipe manager)
/work/fleetwright — FleetWright (fleet repair tracker)
/work/architect-console — Architect Console (internal tooling — case study angle: building the studio''s own systems)

Routing:

Update masthead Work link to /work or anchor to first case study
Each page reuses the editorial design system (bone bg, mono chrome, hairline rules)

Future:

New case studies added as new client work ships.

Build dedicated case-study pages for each shipped product, going deeper than the homepage Field Notes blurbs. **Scope per case study:** - Problem / context (what existed before, why it was inadequate) - Approach and key technical decisions (stack choices, tradeoffs) - Screenshots (more than the single hero shot on the homepage) - Outcomes / metrics where available (users, performance, cost savings, etc.) - Tech stack callout - Live link **Initial pages:** - /work/cookslate — Cookslate (recipe manager) - /work/fleetwright — FleetWright (fleet repair tracker) - /work/architect-console — Architect Console (internal tooling — case study angle: building the studio''s own systems) **Routing:** - Update masthead Work link to /work or anchor to first case study - Each page reuses the editorial design system (bone bg, mono chrome, hairline rules) **Future:** - New case studies added as new client work ships.