WordPress to Astro: Git Is the Undo Button

Why this month

A site still on WordPress is a program. It has a login, plugins, and a database. A visitor hits that program on every page. A site we have already moved is a folder of files. There is no admin page to guess, and no plugin to chain.

Greg Brockman wrote about this on 17 August 2026. He calls it the defender’s window. The same new models that let an attacker chain old flaws also let a defender find and fix those flaws first. That head start is short. He says it is open now.

He pointed one of those models at his own site. In about fifteen minutes it found thirteen problems. Mail settings were not locked down. Old code was still there. One hop sent traffic onward without encryption. He fixed them in about an hour. He dropped the old code. He moved the site onto plain files.

That is the same move for our fleet. Dennis wrote the team on 19 August 2026, the week that essay came out. The articles about AI being able to hack are the reason to build the defense now, before the models get stronger. Start with the sites we run. Then offer the same hardening to clients. Getting off WordPress is the part that removes the login from the public path.

On the 20 August 2026 office hours, about eight minutes in, Dennis said it in his own words. Greg Brockman wrote the essay. The gist is the defender’s window. “You need to get your shit together in the next couple months, if not less than that. We need to protect our stuff now, and we have a window now to protect.” Later in that same call, at about 47 minutes, he said we are moving the WordPress sites onto Astro. The 24 September office hours transcript does not cover this. The essay is also on his own site.

Who can edit

Only these people may change a fleet site:

• Dennis Yu
• Dylan Haugen
• Daniel Goodrich
• Leith
• Muzamil

On GitHub that list is the closed team Website Fleet Editors. The active editor logins are dennisyu, dylanhaugen23, Goodrich-Dev, muzamil-babar, and leith08 (Leith Uwaydah). Leith has accepted the invite and is an active member of Website Fleet Editors. Each person uses their own account. There is no shared password, and this page does not contain one.

How you change a page

1. Sign in to GitHub as yourself. Open the site’s private repo.
2. Open a pull request with the sentence you changed. Do not push straight onto the live files.
3. A second named editor accepts it. You do not accept your own request.
4. The release puts that build on the live site. Then you open the public URL and read the sentence you changed.

As of 30 September 2026, that GitHub team can write five repos: the platform guide, the Amplify canary, adentrano.com, personal-brand-in-a-box, and highriseinfluence.net. Most older personal-brand sites are still a saved folder of pages, not their own repo yet. For those, put the exact public URL and the exact sentence on the team thread. A named editor ships it. A WordPress password will not.

How we left WordPress

A visitor on a moved site gets HTML files. WordPress is not in that public path. That is why /wp-admin and /wp-json come back as a short “Page not found.” The login page is closed on purpose.

1. We saved what visitors already saw. Every URL, the words, and where a lead goes. That crawl is the test.
2. Astro builds the new files. Markdown, a little YAML, and images go in. HTML comes out. Astro does not have to run in the visitor’s browser. A missing required field fails the build.
3. We compare the new files to the crawl before the domain points at them. Leads still have to arrive. Last night’s files have to be restorable.
4. The domain then serves the folder. Undo is the previous folder, not a WordPress revision.

Sites that have not been rebuilt in Astro yet are still that saved folder. They look the same in a browser. They are not edited in wp-admin. The old WordPress publishing guide is for a site that is still on WordPress. It does not open a site that has already moved.

Questions the team actually asks

Can I log in to WordPress? On a moved site, no. The login page is gone so a password cannot change what visitors see.

Where is the key? Your own GitHub login. We do not pass a shared password around, and we do not print keys on a public page.

I merged the request. Why is the site the same? Merge and release are two steps. Open the public URL after the release and read the new sentence.

The site has no repo yet. What do I send? The public URL, the sentence that is there now, and the sentence you want. A named editor ships that.

The rest of this page is the factory story: git as the undo button, and how the notes let the next person pick up the job.

Put the work in git. Put the diary in git. Preview before it is live. That is how a team of models ships like a team of people.

Git is the undo button because the site is a folder of files. Agent notes are how Claude, Cursor, Codex, Gemini, and Grok see the last job and pick up the next one. That is Learn, Do, Teach on a multi-model desk: we run the method, we keep the receipts, we publish the working copy.

How an agent QAs and then writes the note: How Agents QA a Partner Local Audit (and Write It to GitHub). The memory layer under it: How I Built Shared AI Memory Without Lock-In. Execution: If You Can Do It, You Should.

What the four days look like

We stood the notes folder up on 17 Aug 2026. Counted on this Mac, 20 Aug:

By day: 28 on the 17th, 146 on the 18th, 47 on the 19th, then the 20th still writing. 217 of the 294 commits landed after the folder existed. The git author is often my name, because agents commit as me. The model lives in the filename on purpose: YYYY-MM-DD-cursor-grok-slug.md. That is how you ask “what did that model do last night?” and get an answer.

Those notes are not one kind of job. Audits, Gmail threads, WordPress publishes, Descript tapes, AWS host checks, speaker-kit pages, overnight queues. Same sections every time. Next agent reads the three newest files, then writes the fourth.

Astro is the factory. Git is the shelf.

Astro takes Markdown, YAML, images, and a few components and emits HTML. Nothing named Astro has to run in the browser. Content collections fail the build if a required field is missing. That is the contract a page-builder cannot give you.

Hosting can be Amplify, Cloudflare, or any shelf that serves a folder. The rollback package is the last good dist/ zip plus the commit that built it. One repo per site so a client can leave with a clone, not a paid extraction.

WordPress to Astro, in order

Do not cut DNS because the preview looks pretty. Cut DNS when the new site matches the crawl, the leads still arrive, and you can restore last night’s zip.

1. Owner and intent. Domain, registrar, DNS, Search Console, forms. Who signs cutover.
2. Baseline. Crawl every URL. Screenshot desktop and mobile. Write down where a lead goes. That crawl is the test.
3. Export as files. Pages and posts to Markdown. NAP and offers to YAML. Redirects to CSV. Map each plugin to an outcome. Do not copy PHP.
4. Pin the factory. Node, Astro, lockfile. Required fields in collections so a missing canonical fails CI.
5. Preview, then DNS. Technical signature and business signature. TTL and rollback command written. WordPress stays on the team network through the hold, not on the public internet.

A personal-brand homepage is the person’s canvas. New proof is new articles. That is how Dylan Haugen gets tapes onto URLs Google can quote without rebuilding the hero every night. Case: tapes to articles.

Same loop for work that is not a website

If two agents can see the last commit and the last note, they work in tandem. That is the team. Dennis Yu.

Sources, and the technical picture

Greg Brockman, 17 August 2026: The defender’s window on OpenAI, and the same essay at blog.gregbrockman.com/the-defenders-window. After an OpenAI and Hugging Face incident, he argued that attackers will soon chain old flaws at machine speed, and that the same models let defenders find and fix those flaws first. He says that head start is a few months, and that it is open now. A model run against gregbrockman.com found 13 issues in about 15 minutes (mail DNS not locked down, old jQuery, and a Cloudflare hop that forwarded to AWS over plain HTTP). He fixed them in about an hour, dropped jQuery, and moved that site onto Cloudflare Pages.

His four jobs for a defender: secure the code before it ships, let models sort alerts before a human does, keep probing the paths an attacker would use, and keep the old controls (isolation, least privilege, and patching). The ten “do this now” steps stay in the essay. This page does not copy them.

Dennis’s written ask, 19 August 2026, is the team instruction this page follows: co-defend now, harden the sites we run, then roll that across clients. A site still on WordPress keeps PHP, a login, plugins, and a database on the public path. A saved folder or an Astro build does not. On a moved site, /wp-admin and /wp-json are a short “Page not found” on purpose. Undo is the previous folder, or the previous git commit, not a WordPress revision.

WordPress published a security-only update on 22 September 2026, version 7.1.2. One flaw let a visitor who was not logged in, on some setups, make WordPress include a file it should not. WordPress told people to update the same day. This page does not say whether any fleet site is on that version, and it does not describe how the flaw works. The point is the shape of the risk: a program in the request path is a door a folder of files does not have. Patch what is still on WordPress. Do not point a domain at a new folder until the crawl matches, the leads still arrive, and last night’s files can be restored.

What is already an Astro repo is the factory below. What is not rebuilt yet is still the saved folder. It looks the same in a browser. It is not edited in wp-admin.

Working copy, 20 Aug 2026. Counts from the live notes clone that morning. Skill packs: github.com/dennisyu/local-service-spotlight-skills.

Originally published August 19, 2026.