3D
3D Room
A small procedural voxel room with a desk, a trophy shelf and a project wall, built from this site's own JSON feeds.

- Role
- Solo designer and developer
- Timeframe
- Oct 2026 - Nov 2026
- ~380Source lines
- 8Unit tests
- 4e2e tests
- 2Commits
- 1Runtime dependencies
- ~119 KBFonts (woff2)
Problem
I wanted a small 3D scene that shows this site's own trophies and projects without shipping 3D models or trusting feed content.
Approach
- Build the room, desk, shelf and wall procedurally with three.js, so there are no model files.
- Read the site's public JSON feeds, map them defensively, and fall back to sample data if a feed fails.
- Render feed text with textContent only, and cap rendering cost.
Result
A live v0 room with 8 unit tests and 4 e2e tests, including axe checks in dark and light. The JS bundle is over 500 KB because of three.js.
Problem
3D Room is a v0 project: a voxel room with a desk and monitor, a trophy shelf and a project wall, built from this siteโs /trophies.json and /projects.json feeds. It is a solo project.
Approach and decisions
three 0.186 is the only runtime dependency, with TypeScript and Vite. All geometry is procedural. src/main.ts fetches the two feeds; src/data.ts maps them defensively, accepts only https vwesley.dev project URLs, and supplies sample data when a feed fails. Feed text is rendered with textContent only, and the CSP limits connect-src to the one feed host. Fonts are self-hosted woff2, about 119 KB in total.
Performance and motion: OrbitControls has no auto-rotate, out of respect for reduced motion, a maximum distance of 16, devicePixelRatio capped at 1.5, and rendering pauses when the scene is offscreen or hidden.
Results and limits
About 380 lines of source and tests across 2 commits (2026-10-15 to 2026-11-05), with 8 unit tests and 4 e2e tests. The JS bundle is over 500 KB because of three.js. The repository is private and the project is still marked v0, under construction.
