$ cat ./web.md
Web
Static sites — fast, secure and cheap to run. And optimized from the first line not just for readers, but for language models too.
…because the web is no longer read by people alone.
// astro
Speed at the core
A static site is our default choice. It serves in a flash and gives attackers very little to work with — yet can be dynamic where needed.
Static at the core
The site pre-renders to clean HTML. The pages themselves rest on no database and no running backend that could fall over or be abused. Low server requirements and high resilience. If you want the site to draw on data from your own systems, just say so.
Dynamic architecture
Interactivity only where the page truly needs it — the rest stays light. A dynamic component that calls external data sources (an API) can be dropped into an otherwise static page. The static page then behaves like a dynamic one.
Speed as the default
Minimal JavaScript, optimized images and fonts. A fast site is better for users, for SEO and for the models crawling it.
Security and low maintenance
Without plugins and a server layer there is far less to maintain and to attack. Strict CSP and no trackers are the standard, not an extra.
// ai-ready
AI-ready from the first line
The web is no longer read by people alone. It is crawled by AI search, by assistants like ChatGPT, Claude or Perplexity, and increasingly by agents meant to act on it. So we build pages that both a human and a model can understand — not as an afterthought, but as the default.
Semantic HTML
Honest structure — headings, sections, lists — instead of a pile of divs. A model and a screen reader then grasp what is what and how it relates.
Structured data (JSON-LD)
Schema.org describes entities and their relationships in a machine-readable way. Models and search engines know what a page is about, without guessing.
llms.txt
A concise index of the site aimed straight at language models — what is on the site and where. Like robots.txt and sitemap, but for AI.
Content without needless JS
The essential content lives in the HTML, not glued on by JavaScript. A model sees the same thing a person does, not a blank page waiting for a script.
Accessibility (a11y)
What is good for a screen reader tends to be good for a model too: alt text, labels and a clear hierarchy. One effort, double the benefit.
Predictable URLs and metadata
Clean addresses, honest titles and descriptions, Open Graph, canonical links. Easy to cite and share — by people and by tools.
// why
Why it matters
The source of traffic is shifting. More and more people ask an AI directly and only click what it recommends. If models cannot understand your site, or read it inaccurately, a lot of people simply never reach you.
Discoverability via AI
For assistants and AI search to find and recommend you, they have to understand the content. A structured, legible site has the edge.
Accurate representation
When the facts about you are machine-readable and unambiguous, a model talks about you accurately — not from guesswork or stale fragments.
Ready for agents
Tools that get things done for a user need a predictable interface. A clean site and clear contracts make that easy.