Content Collections
Projects and devlogs are typed Markdown collections validated at build time, so a missing field is a build error, not a broken page in production.
Project
The site you're reading — a systems lab, built in the open.
A portfolio should demonstrate how someone builds, not just claim it.
So rhygpu.dev is not a static brochure bolted on top of the real work. It is a small system in its own right, with the same values as everything else in the lab: typed structure, inspectable content, and a build you can read end to end. The site documents its own construction the same way it documents Mnemosyne — in the open, in a devlog.
Projects and devlogs are typed Markdown collections validated at build time, so a missing field is a build error, not a broken page in production.
Every project automatically gets its own devlog homepage. A new entry only needs a project name in its frontmatter to flow into the right journal.
One set of tokens, one sticky nav, one footer, applied across every page — so the whole site stays coherent instead of drifting page by page.
The entire site is prerendered to static files. No server, fast loads, and a deploy that is cheap and hard to break.
rhygpu.dev is live and actively evolving.
It started as an imported homepage design and grew into the full lab: project pages, per-project devlogs, a shared design system, and this meta thread. The active work is the same as any project — filling in real screenshots, writing more devlogs, and tightening the parts that still read as placeholder.
Technical highlights
Proof Notes
Links