An app by default

Every CTXR site is installable: a visitor adds it to a phone or a laptop from the browser, it opens with its own icon, and it keeps working without a connection. Nothing is built for this and nothing is maintained — the engine derives the three files a browser needs from what the site already says about itself. That is a choice, made because a site that is already an app costs nothing to keep and asks nothing of the owner.

Three claimed paths

An installable site needs a manifest (name, icon, colours), a service worker (what to keep on the device), and an offline page. In CTXR these are engine paths, claimed like the sitemap is claimed:

Path What it is Where it comes from
/manifest.json the app’s identity for the device the organisation’s name, the site icon, the theme colours
/sw.js the service worker: what is kept and how it is refreshed the engine; it sits at the root because a worker only controls paths under its own
/offline the page shown when a page is not on the device the engine’s fallback; self-contained, so it renders when everything else is gone

/install explains per browser how to add the site; /favicon.ico is claimed too. The two pages (/offline, /install) are cornerstones: a theme file of the same name takes the path over. The two files are not: /manifest.json and /sw.js are claimed by CTXR with no theme tier, because one wrong line in either breaks the install on every device, and nobody should have to think about them — what a site shapes is the data they are made from. A site that never touches any of this is a complete app already. A physical sw.js in the web root shadows the engine’s — and pins its version; the audit warns. The one list: What your site serves.

What the device keeps

The worker keeps what the visitor opened and, once a day, walks the site’s sitemap (the default language’s) to keep the rest — the sitemap is the list of what exists, so there is nothing to maintain here either. Pages are fetched from the network first and fall back to the copy; stamped assets are kept until the stamp changes; forms are never touched. With a connection the live page always wins. Nothing flows the other way: reading needs no account, and the copy on a device is a reading copy. See Discovery › Your site as an app.

What it buys

A site on the home screen, with an icon, that opens without a loading bar and works in a tunnel — for every visitor, without a store, a review, a second codebase or an update cycle. The app is the site; change the site and the app follows. For the owner it is one less thing that exists.

What it costs

The worker is a real program the browser runs for your site, so it has to be right, and it is the engine’s — not the theme’s — for that reason. It caches, so a visitor may see a page a moment older than the live one before the refresh lands. And it is a web app, not a native one: no push notifications, no camera, no app store. That trade is deliberate — see Discovery › What it is not.