why i built this
I work on public tools and private apps, but the work used to be scattered across repos and session notes. This site gives it a home: what the project does, what changed, and what I learned while building it.
It’s separate from Traversy Media’s course site. The focus here is the projects and the engineering behind them.
what’s here
- Projects: current descriptions, screenshots, and links where they’re public.
- Devlogs: edited accounts of real work, including problems and limitations.
- Articles: longer explanations of workflows and decisions.
- Tools: smaller utilities with their own detail pages.
- Now: what I’m working on and the setup I’m actually using.
Private projects can have build logs without pretending they’re available to download. The status and wording should make that distinction clear.
how it’s built
Astro and MDX provide the pages, Tailwind handles styling, and Vercel hosts the site. Content lives in the repository with validated frontmatter. There is no CMS or content database.
The editor-style layout gives the site its visual identity. Project images and details come from the content entries, so the catalog and individual pages can share the same assets.
how it ships
Changes go onto a dedicated branch, then through a pull request.
After review and merge, Vercel deploys main. Pushing a feature branch alone
does not publish it to the production site.
Devlogs start from recent work and session evidence. I choose what belongs here before it is published; the site is not an automatic dump of private logs.
current work
The ongoing job is keeping the pages honest as the projects change. That means refreshing screenshots, distinguishing shipped work from plans, and removing descriptions that no longer match the product.