Here is a fun thing happening in web development right now. New content sites keep landing on the same framework: Astro. Nobody ran a big campaign for it. Builders just keep arriving there on their own, and the reason is worth understanding, because it is not really about Astro at all.
The editor is no longer a person
The new fact is simple. The thing editing your website is, more and more, an AI agent. And agents live in text. They read it, they write it, it is their water.
Every CMS ever built assumed the opposite: a human editor who could not write code. So we put the content in a database and built forms around it. Buttons, visual editors, permissions, the whole admin panel. Decades of machinery, all to let human hands safely touch data.
An agent does not need any of it. It just wants the text.
The stack gets simpler
Step back and ask what all that machinery was for. Humans are bad at text and make dumb mistakes. We typo the markup, we lose the file, we can hold about seven things in our heads at once, which is a lot for an animal and not a lot for a website. Every piece of the CMS is a guardrail against us: the editor that hides the code so we cannot break it, the review step that catches what we broke anyway, the undo button for whatever got past the review. It is not a content tool. It is a padded room.
An agent needs none of it. It holds the whole site in its head, never typos the markup, never forgets where the pricing page lives. Of course it is better at this than we are. Being better at this is why we built it.
So what is left is your site as plain text files in a folder. You say what you want changed. “Add a post about the new service, match the tone of the last few.” The agent edits the files, shows you the changes, you approve, the site updates. This site has run that way for over a year, and I wrote about it in Do You Actually Need a CMS Anymore. I have not missed the admin panel once.
Which is why everyone lands on Astro
Once your site is a folder of text files, you want the framework that treats files as the whole point, and that is exactly what Astro is. A folder of markdown becomes your pages. The routing is the file system. If a file is missing a field, the build fails instead of shipping something broken. And out the other end comes plain, fast HTML, which is mostly just files too.
Text in, text out, and an agent can hold the entire thing in its head. No API to learn, no database credentials, no interface to click through. Astro’s creators were chasing speed and simplicity, but they accidentally built the perfect home for an agent. That is why everyone keeps showing up at the same door.
The same shift is coming for the rest of your software
The database behind a form is not a website idea. It is the shape of almost all software from the last twenty years. Every admin screen and every internal tool exists because forms were the only safe way to connect a person to their data.
Websites are just where the change shows up first, because a site’s content is small and textual and fits neatly in a repo. Your scheduling tool and your inventory system are further down the same road. I wrote about half of this in Where Did the Interface Go: the interfaces collapsing into a prompt. This is the other half, the data underneath turning back into text.
So if you are starting a site this year, my advice is short. Put the content in files, put the files in a repo, and point Astro at them. You will spend your time on what the site says instead of on the machine that manages it. And when the next shift comes, whatever it is, your content moves with you. It is just text.