why a blog
For my game design course I need a place to document progress, reflect on decisions, and show my individual contributions to the project. This blog is that place.
tech stack
The blog is built with:
- Next.js — React framework with file-based routing and static generation
- Tailwind CSS — utility-first styling
- Markdown — posts are written as
.mdfiles with frontmatter metadata - Vercel — deployment and hosting on crispigt.com
The design matches the aesthetic of enfix.dev — a project I also worked on. Same minimalist approach: clean typography, subtle animations, lowercase text, and a muted color palette.
what's next
In the upcoming posts I'll be documenting:
- My role and responsibilities in the game design project
- Design decisions and the reasoning behind them
- Technical challenges and how they were solved
- References and sources that informed the work
Each post will focus on what I've done, what I've learned, and how it fits into the larger project.
This is the first entry. More to come as the project progresses.