A short list rather than a long one. Each of these is in use by somebody, and I can walk you through how any of them was built.
Python · python-docx · single-file HTML site
Price sheet generator for a Lorain fish market. Market prices move weekly, so the sheet is generated from one data file rather than retyped, and the page-fill logic keeps a full week of product from silently spilling onto a second page.
Result: a week of prices goes out in minutes instead of an afternoon of retyping, and the printed sheet and the website read the same numbers.
Next.js · Supabase · Postgres row-level security
Merchandise planning tool that tracks budget against receipts and sales by department, so buyers know what is actually left to spend before they commit at market.
Result: open-to-buy is a number on a screen at market rather than a guess reconciled a month later.
JavaScript · Firebase · Firestore security rules
Shift scheduling for an hourly staff whose availability changes every term. Managers publish the week, staff see their shifts on a phone, and nobody maintains a paper grid in the back office.
Result: the week is published once, and the "when do I work?" texts stop.
Built for myself or for family. Here as evidence of range and pace, not as client work.
React 19 · Vite · Firebase · offline PWA
Garden planner built for Zone 6b on the lakeshore, where the water holds the last frost about two weeks past what the state map claims. Tracks plantings, harvests, and variety notes, and works with no signal in the yard.
Result: two seasons of real planting dates and yields, recorded standing in the garden rather than remembered in March.
Ten years of work in higher-education retail, covering e-commerce merchandising, vendor reporting, and web analytics, is not shown here because it belongs to the client. Happy to walk through the approach in a conversation.
