# Now anyone can put up a site in an afternoon, and someone still has to mind it

> Assistants can build a site from a few sentences, which makes the web feel like a wild west again, and the owner's part is small but real

By Orla Finch. Published 2026-10-29.

History of building websites, 9 of 10.

Say it is 2025, and Priya, who once filled her site with borrowed parts, wants a page for the pottery evenings she has started teaching. [Last time](/blog/ai-arrives/) we watched Rosa learn that an assistant could write a page from a sentence. Priya tries it. She describes what she wants after lunch, and by evening the page is up, booking form and all.

She is far from the only one. By early 2025 this way of building had a name, [vibe coding](https://en.wikipedia.org/wiki/Vibe_coding). So the web feels a little like the [hand-typed days](/blog/web-pages-in-the-1990s/) again: new places going up everywhere, each one needing someone to mind the doors.

The good news is that minding them is a small job. Four parts still need a person, and none needs a toolbox.

First, keep the site up to date. People who make software call this [maintenance](https://en.wikipedia.org/wiki/Software_maintenance): changing a program after it is handed over, to fix what is wrong and keep it useful as things around it change. Nearly every program ships with some bugs, and Priya's class times will change too. When something on her page is wrong or out of date, she changes it.

Second, check the links. [Link rot](https://en.wikipedia.org/wiki/Link_rot) is the name for links that stop leading where they used to, because the page at the other end moved or was taken down. When [Pew Research](https://www.pewresearch.org/data-labs/2024/05/17/when-online-content-disappears/) looked in 2023, 38% of pages from 2013 had gone missing. Priya's page points to her clay supplier and a map of the car park, and either could move without telling her. Clicking through them now and then is the fix.

Third, ask who can see what. [Web application security](https://en.wikipedia.org/wiki/Application_security) is the work of finding weak spots in sites and web apps, and one of the most serious is [people getting at things they should not see](https://owasp.org/Top10/2025/A01_2025-Broken_Access_Control/). So Priya asks one question of her page: who can see the names on her booking list?

Fourth, and this one is new, keep the last yes for yourself. An assistant that reads a page can be fooled by what the page says. The trick is called [prompt injection](https://en.wikipedia.org/wiki/Prompt_injection): the assistant takes in its orders and the text it reads together, so [it cannot tell the two apart](https://www.ncsc.gov.uk/blog-post/prompt-injection-is-not-sql-injection), and orders hidden in a page can steer it. Two of the usual defences are giving a tool only the access it needs and having a person sign off on anything sensitive.

For Priya, that means her assistant can draft a change, but it does not send her students' details anywhere, or put a new page live, without her yes.

So the web is a bit wild again, and that is part of the fun: anyone can have a place of their own by teatime. Your part is small. Keep it current, click your links, ask who can see what, and say yes yourself before anything important changes.
