rhygpu.dev

Problem

A GitHub repo alone does not explain project intent.

Source code can show what exists, but it rarely explains why the project exists, what changed over time, which tradeoffs mattered, or what is still unfinished. Raw chat logs and dense devlogs have the opposite problem: they preserve too much texture for a first impression.

A useful portfolio needs layered access. Someone should be able to scan a project summary, open a case study, inspect real proof media, follow the devlog if they want the history, and only then reach for raw/archive material when provenance matters.

That is the job of rhygpu.dev: make the path from messy build history to public project narrative readable without sanding off the engineering reality.

Solution

rhygpu.dev organizes RhyGPU work into a public system:

A portfolio homepage for the current project set.
Project pages for technical case studies.
A shared devlog archive for project history.
Proof/media sections for screenshots, diagrams, and honest planned slots.
About, Resume, and Contact pages for the human/profile layer.
Tracked build/archive logs where they are useful as source material.

The site-building notes and project devlogs live in the shared development journal. Raw chat/build logs are archive material, not the main route a reader is expected to take.

Core Systems

Project Collection

Projects are modeled as Markdown content entries with status, stack, proof notes, media, architecture, and long-form body content.

Devlog Collection

Development entries are structured content, so the archive, project links, metadata, and individual pages stay generated from one source.

Case-Study Pages

Each project gets a reusable page shell for problem, solution, systems, proof, current status, and skills demonstrated.

Proof / Media Layer

Project pages can show real screenshots, diagrams, demo links, and planned slots without pretending unfinished assets already exist.

Metadata / SEO Layer

Shared layout metadata handles titles, descriptions, canonical URLs, Open Graph, and Twitter summary tags.

Build / Archive Logs

Raw site-building material can be retained as archive/source evidence while the public surface stays curated and readable.

Static Generation

The site builds into static pages, keeping hosting simple and making route generation easy to validate before deploy.

Architecture / System Shape

The site is intentionally small and inspectable:

Markdown content becomes typed Astro collections, collections generate project and devlog routes, shared components provide the frame, and the static build becomes the public portfolio.

Current Status

rhygpu.dev is an active portfolio site.

The homepage, project index, individual project pages, devlog archive, About, Resume, and Contact pages exist. Mnemosyne, OmniPlanner, and Pythagorean Harmony now have distinct public surfaces, and this page makes the site itself visible as the fourth meta-project.

The meta-build archive exists, but it should remain behind the scenes unless a future page intentionally explains it. The next cleanup pass should focus on site-specific devlogs, stronger live deployment QA, and replacing planned site screenshots with real captures once the layout stabilizes.

What This Demonstrates

Portfolio information architecture Astro / static site development Content modeling Technical writing Project framing Source-to-public narrative transformation Build / repo hygiene