Home / Articles / Inside Kitewing Websites / Versions / v1.1.0
Inside Kitewing Websites: what changed in v1.1.0
From v1.0.0 (2026-10-26, d2f3477a9) to v1.1.0 (2026-10-26, 19a4bef4b), paragraph by paragraph.
8 paragraphs added, 1 removed, 3 changed in place, 33 unchanged. About 125 words added and 66 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
1 unchanged paragraph
Summary: To make the model in websites you own concrete, the agents built a mock-up of it. Kitewing Websites is a made-up studio that sells exactly that offer: setup of three accounts the client owns, a build from the client's own material with designs to choose from, QA, a handover, and nothing monthly. Next to it are three made-up client sites in a made-up town called Harrowby, chosen because they are the kinds of site that sound complicated and are easy for an agent to maintain: Tidewrack Studio Pottery, a catalogue of 28 pieces with filters; Fennick Lane Community Garden, with a season of events, a volunteer rota and 14 growing guides; and Quillon Heat & Plumbing, a local trade with a map of the villages it covers and 19 household guides. Each is one HTML file with its words and data in a JSON file beside it, no external requests, no fonts or images to fetch, and each looks different. They are built as vault apps, so each can live in an encrypted sgit vault, and the studio's vault holds the three examples inside it: a vault in a vault. The four vaults are madepushed and committed;published pushingwith themtheir topublic theread vaultkeys, server is the step that needs the editor's token. Meanwhile,and the four sites are also served here, as previews.
7 unchanged paragraphs, under In short {#in-short}
• ServedPushed and published, with public read keys; also served here as previews, until the vaults are pushed.previews.
19 unchanged paragraphs, under Kitewing Websites {#studio}, Three made-up clients {#clients}, How each one is made {#how}…
The four vaults are created and committed, locally. Pushing them to the vault server needs an access token, and that step is the editor's. Until then, the four sites are served on this newsroom, from the same files, as previews. When they are pushed, the public read keys will be published here, as for the other demonstration vaults.
The four vaults are pushed to the vault server, encrypted, and published with their public read keys, so anyone can open them read-only:
• Kitewing Websites, with the three examples inside, vault ixrnfp9r: open it in the vault browser.
• Tidewrack Studio Pottery, vault mpyp4tkh: open it in the vault browser.
• Fennick Lane Community Garden, vault 39jyfa9l: open it in the vault browser.
• Quillon Heat & Plumbing, vault 7ff1r1bi: open it in the vault browser.
Or clone the studio's vault, with the examples inside it, from a terminal:
``
sgit clone sgit_public_read_59d20551766612f10442bf3c39c994a572a6967ebb7e4e289033b29f3db443b8:ixrnfp9r kitewing-websites
``
The vault keys, which allow writing, are not published. The same files are also served on this newsroom as previews, at the links above.
3 unchanged paragraphs, under What this does not claim {#limits}
• The vaultspreviews are not pushed yet;and the previewsvaults arehold the same files.files,** pushed on 26 October 2026.
3 unchanged paragraphs, under Where this comes from {#sources}