I've had a GitHub Pages repo sitting around for a while with placeholder text and good intentions. Time to actually use it.
What I'm trying to do here
This site is a place for me to vomit out my brainthoughts without having to worry about who gets stepped on. I want a place to:
- Write about my work in plain language, whether it be tech centered stuff, or perhaps more personal like game design or worldbuilding
- Point people at a few projects that show how I think
- Document what I'm learning while I explore career options
If you're evaluating me for a role, the about and projects pages are probably enough; the blog is for anyone who wants more depth.
If you're not, I'm not sure why you're here. But if you are, welcome!
Why keep the stack boring
Phase 1 is plain HTML and CSS — no build step, deploy on push via GitHub Actions. Ultimately, I am also using this page to mess around with this GenAI site building trend. I am using Cursor to generate the HTML and CSS, and then I am using the GitHub Actions to deploy the site. Without needing to rely on a proprietary CMS platform I want to see how far I can push things.
The deploy pipeline itself is the kind of infra work my AI actually enjoys. Here's the core of it:
on:
push:
branches: ["master"]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/configure-pages@v5
- uses: actions/upload-pages-artifact@v3
with:
path: '.'
- uses: actions/deploy-pages@v4Push to master, site updates. Custom domain via CNAME. Nothing clever — and that's the point.
What comes next
I'll add posts when I have something worth saying: a pipeline I wired up, a side project postmortem, notes from learning something new. Rough target is one post every month or so once things get moving.
When maintaining the blog index by hand gets old — probably around post three or four — I'll migrate to Eleventy and Markdown. Until then, this works.
Thanks for reading. If something here resonates, get in touch.