Welcome to the new Star Computers
Why we rebuilt the site on Astro, how the new blog works, and what to expect from upcoming posts on cloud and systems engineering.
Star Computers
Why rebuild
The previous site was four hand-coded HTML files. That approach is fine for a brochure site — but a blog needs more than copy-paste. Every post required duplicating a template, re-implementing meta tags, and hoping the tag markup matched what the last post used. The result: weak SEO, inconsistent cards, and a tag system that existed in name only.
What changed
- Astro generates static HTML at build time. Pages ship near-zero JavaScript.
- Markdown posts live in
src/content/posts/. One file per post, frontmatter on top. - Typed tags are validated against an allowlist.
tags: ['awz']is a build error. - Generated SEO: every page has canonical URLs, Open Graph tags, and JSON-LD.
- RSS, sitemap, and an
llms.txtare generated automatically from the post list. - Tag pages (e.g.
/tags/kubernetes) list every post in a topic with a post count. - Raw markdown is served at
/blog/<slug>.mdso answer engines can ingest clean text.
How writing works
npm run new-post "How we cut our EKS bill by 40%"
# → src/content/posts/how-we-cut-our-eks-bill-by-40.md
# Edit frontmatter + body in your editor
npm run dev # preview at http://localhost:4321
git push # CI builds and publishes
What to expect
Short posts from real production experience — AWS, Kubernetes, DNS, networking, identity.
Benchmarks and runnable examples where they help, no SEO-filler. If something is wrong,
the /contact page is open.
Frequently asked questions
- Why rebuild the site?
- Hand-edited HTML made adding posts painful and left SEO and tag taxonomy broken. Rebuilding on Astro fixes both at the source.
- How do I add a new post?
- Run npm run new-post "Your title", fill in the frontmatter, write markdown, and push. The build validates frontmatter and fails loudly on typos.