Hi {{first_name|Oncer}},I missed Thursday's newsletter because I've been deep in building and running a series of experiments.Not with AI chat or content generation specifically, but with a question that keeps coming back to me:What happens when a website stops being a collection of pages and starts becoming a system?
Most of us still think of websites the way we did a decade ago. You design some pages, write content, publish it, update it occasionally, and hope people find it.Lately, that model feels increasingly outdated.One of the first experiments I set up was around our own documentation.The Aveiro blog, documentation, and API reference now live as separate sites. Together they contain more than 200 pages, all indexable and available in markdown format for AI systems.More interestingly, they are continuously monitored by an automation connected to our development workflow. Whenever code changes are merged, the system checks whether documentation needs updating and can publish revisions automatically.The surprising part wasn't that it worked.The surprising part was how quickly I stopped thinking about documentation as something I needed to remember to maintain.It started feeling more like infrastructure.Around the same time, I published Social by Aveiro, a practical guide for people who want to start building a presence online after exchanging words with Shubham, a builder from our community who wants to start social media.The entire site was produced using Composer 2.5. I wasn't trying to create a demo or showcase AI-generated content. I wanted to see whether it could produce something genuinely useful. Something that a real person could read and apply.The result was much better than I expected. Not perfect, but coherent, actionable, and surprisingly thoughtful. It felt less like generating content and more like collaborating with someone who understands structure and information architecture.
That experiment led to another.I set up an automation that creates entirely new sites every day around different topics of modern life: health, creativity, communities, work, balance, entertainment. The goal isn't to flood the internet with content. It's to explore whether focused knowledge sites can be created, expanded, and maintained at a scale that simply wasn't practical before.
At the same time, I've been using many of these same workflows for something completely different.
Some of you know that I've been building Journal of the Universe, a science-fiction project I've been working on in the background. Characters, locations, timelines, visual concepts, stories, and worldbuilding.
Almost all of it now involves highly guided AI workflows. Not random prompts or one-click generations. Careful iteration, direction, editing, and refinement.
What's fascinating is that the role feels different from traditional writing. Less typing every word yourself and more shaping a world, making decisions, and steering the process. The output has become increasingly consistent, and honestly, some of the scenes and visuals we're producing now would have felt impossible for a small independent creator just a few years ago.
Looking across all of these experiments, I keep arriving at the same conclusion:
In a weird way, website are becoming programmable, and it honestly feels more alive than social media.
Visitors can read content, subscribe to updates, talk to AI systems trained on that content, or reach the person behind it directly. Agents can update documentation, publish articles, manage knowledge bases, and perform maintenance tasks. Content can be transformed, translated, syndicated, and distributed automatically.
The website stops being a destination and starts becoming a node.
Something people, software, agents, and other systems can all interact with.
Over the last few weeks, we've been quietly moving Aveiro in that direction.
Sites can now provide:\
AI-powered conversations based on their content.\
Human chat support can be enabled directly on sites.\
Content is available in markdown format for AI crawlers and systems.\
We launched an API, an MCP server, and integrations that allow tools like Cursor to create automations around websites.
We've also added email APIs that make it possible to subscribe visitors from external applications and workflows.
And we're only getting started.
Next up are AI-powered translations and support for selling digital products directly through sites.
A few years ago, building a website meant creating pages.
Today, it increasingly feels like creating a system.
You still provide the vision.
You still make the important decisions.
But more and more of the repetitive work can be delegated.
That's the transition I've been observing through these experiments, and it's becoming harder and harder to imagine going back.
— Lorant
P.S. If you or your friend would like to give Aveiro a try, just reply to this email and I'll send you an invite code.
