Tyreil
tyreil.comBuild log1 min read

Choosing the stack

Why this site runs on Astro and Keystatic, with content in GitHub and hosting on Vercel, instead of WordPress or Kirby.

Build log 2 of 4 fortyreil.comMy work was split between a UX portfolio and side projects with no home, so this site gives every project a page and a public build log.
Status: Shipped

The structure of this site set the requirements. Build logs nest inside their project, so a log’s address reads /projects/<project>/<post>, and every project gets its own RSS feed.

I looked at three options:

  • WordPress stores posts flat. Nesting them under projects means a custom post type, a relationship plugin, and permalink rewrites, plus ongoing plugin updates.
  • Kirby handles nesting naturally because folders are pages. But it’s a PHP app, and my stack is GitHub, Vercel, and Supabase, which are built around JavaScript.
  • Astro with Keystatic keeps every post as a file in my GitHub repo, gives me an editor to write in, and deploys to Vercel on every save.

I went with Astro and Keystatic. Content stays in Git, so every change has history and a preview. And since Ghost Writer exports Markdown, it can eventually draft build logs straight into this site.

Previous log

Designer, developer, writer, and product owner used to be separate jobs. This site is built around projects instead of job titles, and every post belongs to the work it documents.

Previous log1 min
Next log

Cut over from static HTML to Astro and Keystatic, restored career case studies with images, and gave every project a cover and a place to log work in public.

Next log1 min