I moved this site from WordPress to a static site built with Astro. The notes are now Markdown files in the repository, and a build produces the pages readers open.
In 2023, I wrote about moving from Jekyll and GitHub Pages to WordPress. WordPress gave me a browser-based publishing workflow. This move returns the content and layout to files that I can inspect, edit, and version together.
What changed
The published site no longer needs a WordPress application server or database. It still needs a hosting service to deliver its files; static hosting can be inexpensive, but being static does not guarantee zero cost.
Prebuilt pages also remove the need to generate article HTML for each request. Actual loading speed still depends on page size, images, scripts, caching, and the network.
Keeping content in Markdown makes it easier to move or process later. AI can assist with drafting, editing, code, and review because the relevant files are accessible together. I direct that work, and the History of Logic series carries its own AI authorship notice.
The tradeoffs
My current workflow involves editing files and rebuilding the site. Browser-based editing is still possible through repository tools, but I no longer use WordPress's integrated post editor and administration panel.
Layout changes usually involve code. Astro does have integrations and supports interactive components; it is inaccurate to say there are no plugins or that a static site cannot support comments, search, or interactive lessons. These features need an implementation appropriate to the site's architecture.
The migration also requires preserving old links, media, and content. Moving the files is only part of the work: the rebuilt pages have to render correctly and remain useful to readers arriving through older URLs.