From 83af8f7fc342b25ed8c8b477ec65b905de58021f Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 8 Sep 2026 20:43:18 +0000
Subject: [PATCH] feat(post): draft 'Rebuilding this site on Astro'\n\nAdd a
 draft post describing the migration from static HTML to Astro, automated
 deployment, and agentic workflows.\n\nCloses #6\n\nCo-authored-by: Copilot
 <223556219+Copilot@users.noreply.github.com>

---
 src/content/posts/rebuilding-this-site-on-astro.md | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 src/content/posts/rebuilding-this-site-on-astro.md

diff --git a/src/content/posts/rebuilding-this-site-on-astro.md b/src/content/posts/rebuilding-this-site-on-astro.md
new file mode 100644
index 0000000..2745884
--- /dev/null
+++ b/src/content/posts/rebuilding-this-site-on-astro.md
@@ -0,0 +1,11 @@
+---
+title: Rebuilding this site on Astro
+date: 2026-09-08
+draft: true
+description: This post details the process of rebuilding my personal site from static HTML to Astro, automating deployment with GitHub Actions, and integrating AI agent workflows for content management and site maintenance.
+tags: [meta, astro]
+---
+
+Just rebuilt my personal site from scratch. I migrated from a hand-written static HTML site to an Astro-based generator, leveraging content collections, drafts, RSS, and a sitemap. Deployment is now fully automated via GitHub Actions to GitHub Pages. I also set up AI agent workflows (gh-aw) to draft new posts by filing GitHub issues from my phone and to run weekly automated checks for dead links.
+
+The architecture is split into two layers: a deterministic layer (the generator and deploy pipeline, with no AI at runtime) and an agentic layer (the gh-aw workflows, which can only open PRs or issues, never deploy anything themselves).