03 / 04
Case study

Foundry

Homepage hero, search-first lost and found
Fig. 03.1Homepage hero, search-first lost and found
Role
FBLA Website Coding
Context
Next.js, TypeScript, Prisma
Years
2025–2026
Stack
Next.js, TypeScript, Prisma, SQLite, WCAG AA

03.1
Overview

A school lost-and-found platform built around Search, Submit, and Claim — smart search, item submission, authentication, claim verification, admin dashboard.

03.2
Detail

Stack: Next.js, TypeScript, Prisma, SQLite.

Rebuilt the frontend in April 2026 as Foundry with a fully custom Figma UI (not template-generated), keeping the working backend, built to WCAG AA accessibility.

03.3
History

It started as an FBLA Website Coding project, built with Prithvi Konduru, under the name Where'd it go? The 2026 rebuild shipped as FINDR before it became Foundry. Everything on the page has been redrawn since; the two doors, submit and search, never moved.

  1. 01First heroWhere'd it go?
    The first Foundry homepage: “Lost something?” in black on tan, with submit and search buttons

    One question on a tan field, a box for a mark, and the two ways in. The wordmark read LOST N FOUND.

  2. 02Submit flow
    The original submit-an-item modal, wireframed with category, date and location fields

    Name, category, date, location, a description and one photo — everything a claim gets matched against later, asked for once, in a single modal.

The homepage end to end, hero through the three-step explainer
Fig. 03.2
Full homepage, 1440px
Presentation
Figma Slides
Open↗