Case study · 06
Open Source
Ship in public when it helps someone else.
Open source here ranges from small WordPress/JS utilities to full products like 3D Box Studio (MIT). The through-line: solve a real problem, document the stack, and leave the repo in a state a stranger can run.
The problem
Too many portfolio repos are unfinished demos. Useful OSS needs a clear README, runnable scripts, and honest scope.
The approach
Publish when the tool is useful — packaging simulator, plugins, experiments — with licenses, env examples, and contribution-friendly structure.
What it does
Capabilities worth calling out.
01
Production OSS products
3D Box Studio as a full MIT product with studio UX, cloud shares, and docs — not a toy sandbox.
02
Practical utilities
WordPress plugins, Chrome helpers, and frontend experiments that came from real client or personal needs.
03
Readable repos
READMEs with stack, setup, and env contracts so clones aren’t guesswork.
04
Learning in public
TypeScript/Next.js projects that double as teaching artifacts for WebGL, maps, and commerce patterns.
Tech stack
What powers it.
Concrete tools a developer should list on a showcase card — not vague “full stack” labels.
Languages & frameworks
Domains
Hygiene
Architecture notes
How it fits together.
- Prefer monorepo-simple Next apps with clear /app or /src boundaries
- Document env vars in .env.example before publishing secrets-shaped config
- License early (MIT) when the intent is reuse
Build highlights
Details that matter.
- Flagship OSS: 3D Box Studio with real hosting costs and a Buy Me a Coffee support path.
- RoadPlan Studio source available for stack study (Next.js + Neon + Better Auth + Maps).
- Mixed portfolio of product OSS and smaller utilities shows breadth without noise.
Outcomes
What shipped.
Result 01
Public proof of craft beyond closed client work
Result 02
Reusable teaching material for WebGL and full-stack Next.js
Result 03
Community-facing credibility for hiring and collaboration
Portfolio checklist
What a developer should include.
Use this project as a showcase template — every case study on this site is written so another engineer can mirror the same depth.
- Pin 2–3 best repos; hide unfinished noise.
- For each pin: one-line problem, stack badges, live demo link.
- Mention stars/forks only if meaningful; prefer clarity over vanity metrics.
- Link OSS detail page from product case studies that are open.