What a CTXR site is
To a visitor, a CTXR site is a website like any other: pages, images, a contact form, fast to load, found by search engines. Behind it there is no admin panel, no database and no build step. There is a folder.
A folder that renders
Your content is small structured files, one per thing on your site: a page, a team member, a product. Each says what it is and what it contains, in Schema.org — the public vocabulary search engines and AI assistants already understand. Next to the content sit your templates, images and files.
When someone opens a page, the engine renders it from those files right then. No stored copy can go stale: publish a change and the site has changed at once; a file edited any other way shows within seconds.
The engine sits next to it
The engine — the part that renders, checks, keeps history and talks to your agent — is a separate folder, the same for every CTXR site. It knows nothing about your site in particular, and your site nothing about its insides. That is why an update never touches your content, and why your content is yours to take with you. See Your content is yours.
You change it by asking
You say what you want in your own words; the agent finds the right file, makes the change and stages it as a draft for you to preview and publish. There is no editor to learn. See How you manage your site.
What comes for free
| Property | What it means |
|---|---|
| Machine-readable view | Sitemap, feed, a plain-text map and a searchable index of every entity — each entity at its own address, as data or as readable text — from the same files as the pages, always in step, in every language. See Discovery. |
| Installable as an app | Works on a phone and offline, with nothing to build. See An app by default. |
| Complete history | Every change is recorded: who made it, what was touched, and — when your agent passes it along — what you asked; every earlier version is kept. See History and undo. |
| Quiet | No tracking, no accounts, no cookies for visitors. See Trust. |