<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Changelog — Verso</title>
    <link>https://verso.pub/changelog/</link>
    <description>Changelog — Verso</description>
    <atom:link href="https://verso.pub/changelog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>0.10: Every screen size — Verso</title>
      <link>https://verso.pub/changelog/0-10-every-screen-size/</link>
      <guid>https://verso.pub/changelog/0-10-every-screen-size/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>See, edit and style a site at any screen size, and set the sizes themselves.</description>
      <content:encoded><![CDATA[<p>A layout that works on a laptop and falls apart on a phone isn't finished. Until now, the builder offered four sizes and drew every one of them at the window's width, and changing where a size starts meant editing Elevate's settings by hand. This release makes screen sizes visual from end to end.</p>
<h3>In the editor</h3>
<ul>
<li><strong>Screen sizes in the bar:</strong> see the whole page at a phone's width, a tablet's or any of the site's sizes, scaled to fit, and keep editing there.</li>
<li><strong>Build a block at a size:</strong> every size the site has is in the switch, and picking one narrows the preview to where it starts.</li>
<li><strong>What comes from where:</strong> a dashed choice is one the element gets from a smaller size, and a dot on a size means the element changes there.</li>
</ul>
<h3>In Design</h3>
<ul>
<li><strong>A Screens tab:</strong> name, move, add and remove the site's sizes. Removing one in use asks first and takes its styles with it.</li>
</ul>
<h3>In Elevate 1.3</h3>
<ul>
<li><strong>Breakpoints from your settings:</strong> Elevate now reads every breakpoint from <code>config/design.ts</code>, keeps them in width order, and accepts names up to twelve characters, so a project can change them in one place.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Design</category>
    </item>
    <item>
      <title>0.11: The site, rebuilt — Verso</title>
      <link>https://verso.pub/changelog/0-11-the-site-rebuilt/</link>
      <guid>https://verso.pub/changelog/0-11-the-site-rebuilt/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>The Verso website, started over and rebuilt in the editor, and the eleven fixes that came out of it.</description>
      <content:encoded><![CDATA[<p>The old site was written before Verso could build a site by clicking. This one began as an empty starter and was made the way the docs now describe: design first, then blocks, then pages. The <a href="https://verso.pub/field-notes/">field notes</a> have the whole account, including what's still rough.</p>
<h3>Fonts</h3>
<ul>
<li><strong>Fonts name themselves:</strong> drop a font file and Verso reads its family, weight and style, and whether it's a serif, a sans or a monospace.</li>
<li><strong>Variable fonts:</strong> one file keeps every weight, so bold is the font's own bold.</li>
<li><strong>Removing a font</strong> removes its files and rules.</li>
<li><strong>Sub-folders:</strong> fonts are found when the site lives in a folder of its address.</li>
</ul>
<h3>Blocks</h3>
<ul>
<li><strong>Previews where they live:</strong> in the Blocks library and Build a block, a block is drawn inside the same elements as its block area, so a block that sits on a white panel is shown on one.</li>
<li><strong>The library stays open</strong> after Add, so several blocks can go on in a row.</li>
</ul>
<h3>Design and pages</h3>
<ul>
<li><strong>The Design panel stays open</strong> after a rename, and tidies names as you type them.</li>
<li><strong>Your colours first:</strong> picking a colour on a page shows the site's own before the built-in ones.</li>
<li><strong>New page</strong> starts on the type of the page you're on.</li>
<li><strong>Same-day sorting:</strong> titles sort the way people read numbers, so 0.10 comes after 0.9.</li>
<li><strong>Your own CSS:</strong> the error for a class Elevate doesn't know now says how to mark it as yours.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Design</category>
      <category>Building</category>
    </item>
    <item>
      <title>0.12: Deleting, moving and a blank start — Verso</title>
      <link>https://verso.pub/changelog/0-12-deleting-moving-and-a-blank-start/</link>
      <guid>https://verso.pub/changelog/0-12-deleting-moving-and-a-blank-start/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>Delete a page or a block, change a page's address, use parts inside blocks, say what changed when you publish, and start from a blank site.</description>
      <content:encoded><![CDATA[<p>Rebuilding this site left a list of things the editor couldn't do. This release is that list. The <a href="https://verso.pub/field-notes/">field notes</a> say how each one came up.</p>
<h3>Pages</h3>
<ul>
<li><strong>Delete a page</strong> from <a href="https://verso.pub/docs/editor/page-settings/">Page settings</a>. Pages inside it go with it, and Verso names anything that still links there.</li>
<li><strong>Change a page's address.</strong> The page's folder moves, and the site's links, menus and lists follow it.</li>
</ul>
<h3>Blocks and parts</h3>
<ul>
<li><strong>Delete a block</strong> in <a href="https://verso.pub/docs/blocks/builder/">Build a block</a>. A block that's in use asks first, then comes off every page.</li>
<li><strong>Parts inside blocks:</strong> a <a href="https://verso.pub/docs/templates/parts/">part</a> can be used by a block, so a card shared by two blocks is written once.</li>
</ul>
<h3>Publishing and starting</h3>
<ul>
<li><strong>Say what changed:</strong> Publish asks for a few words, and History shows them beside the date.</li>
<li><strong>A blank start:</strong> <code>npx verso-cms new my-site --blank</code> makes a home page, a 404 page and three plain blocks, with no starter design to clear away.</li>
</ul>
<h3>Screen sizes</h3>
<ul>
<li><strong>Sizes out of order:</strong> a class list with its size markers backwards, or one written twice, gets a note in the editor with the file and line. Elevate's other notes show there too. None of them stop Publish.</li>
</ul>
<h3>Elevate</h3>
<ul>
<li><strong>Scripts:</strong> a script's own value inside class quotes no longer stops the build.</li>
<li><strong><code>line-clamp</code></strong> works from one class.</li>
<li><strong><code>visually-hidden</code></strong> is a new class for text that only screen readers get.</li>
<li><strong>Grids that share classes:</strong> several elements with most of their classes in common, changing at different screen sizes, are always told apart. The “Responsive ambiguity” note is left for two elements with exactly the same classes.</li>
</ul>
<h3>This site</h3>
<ul>
<li>The stand-in editor bar and the demos on the home page are built from Elevate classes. The site has no stylesheet of its own beyond its font files.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Building</category>
      <category>Language</category>
    </item>
    <item>
      <title>0.13: A site in a box — Verso</title>
      <link>https://verso.pub/changelog/0-13-a-site-in-a-box/</link>
      <guid>https://verso.pub/changelog/0-13-a-site-in-a-box/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>Run a site as one program that serves the pages and the editor at the same address. People sign in on the site, several can edit at once, and Publish is live in a second.</description>
      <content:encoded><![CDATA[<p>Until now, editing a Verso site meant running it on your own computer. That suits the person who builds a site and nobody else. This release is for everyone else: <a href="https://verso.pub/docs/start/a-site-in-a-box/">host the site once</a>, and the people it belongs to edit it where it lives.</p>
<h3>The box</h3>
<ul>
<li><strong><code>npm start</code></strong> runs the site and its editor as one program, at one address. Visitors get the published pages as plain files; anyone signed in gets the editor.</li>
<li><strong>Publish is live at once.</strong> A restore point is saved under the publisher's name and the pages are rebuilt, usually in under a second.</li>
<li><strong>Drafts stay private.</strong> Visitors only ever see what was published, even after a restart.</li>
<li><strong>No repository needed.</strong> The history lives in the box. A git remote, if there is one, gets a copy of every publish.</li>
<li><strong>A kept disk:</strong> point <code>VERSO_DATA</code> at a disk that lasts and the site moves onto it. Each start says how many restarts its files have been kept through. New sites come with a <code>Dockerfile</code> that does this.</li>
</ul>
<h3>People</h3>
<ul>
<li><strong>Signing in</strong> at <code>/edit</code>, with pages for setting up the first owner, joining from an invite and choosing a new password.</li>
<li><strong>Invites</strong> are links you send yourself. Each works once and lasts seven days.</li>
<li><strong>Owners and editors:</strong> editors change words, pictures, blocks and pages, and publish. Owners can also change the design, build blocks and manage <a href="https://verso.pub/docs/editor/people/">people</a>. Editors aren't shown the tools they can't use.</li>
<li><strong>Several people at once:</strong> you see who else is on your page, their saved changes appear on yours without interrupting your typing, and everyone hears when someone publishes.</li>
</ul>
<h3>Safety</h3>
<ul>
<li>Passwords are kept as salted hashes, in a folder that never goes into the site's history.</li>
<li>Every editor request is checked for a signed session, the person's role and where it came from.</li>
<li>Wrong passwords lock an address for fifteen minutes after five tries.</li>
<li><code>verso owner</code> makes a new owner's link from the server, for when everyone is locked out.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Hosting</category>
    </item>
    <item>
      <title>0.8: The language grows — Verso</title>
      <link>https://verso.pub/changelog/0-8-the-language-grows/</link>
      <guid>https://verso.pub/changelog/0-8-the-language-grows/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>The template language grows up: else, comparisons, filters, tags and tag pages, pages of a list, repeaters, site fields, parts with values, feeds and sub-folder hosting.</description>
      <content:encoded><![CDATA[<p>Until now the template language did four things and stopped. Building real sites showed where that hurt: no way to say “otherwise”, no tags, no second page of a journal, a header copied into every template. This release fills those gaps, with tags that still read as plain HTML.</p>
<h3>Conditions and lists</h3>
<ul>
<li><code>{{ else }}</code> in conditions, and in lists for when there's nothing to show.</li>
<li>Conditions can ask for empty with <code>{{ if:!cover }}</code>, and compare with <code>{{ if:kind=essay }}</code> and <code>{{ if:kind!=essay }}</code>.</li>
<li>Lists filter: <code>tagged-design</code>, <code>has-cover</code>, <code>no-cover</code>, <code>kind=essay</code> and <code>kind!=essay</code>.</li>
<li>A new sort, <code>most</code>, puts the most used tags first.</li>
<li>Any list can sit inside another, three deep.</li>
<li><code>{{ count:journal }}</code> counts, with the same filters as a list.</li>
<li>References take formats: dates as <code>long</code>, <code>short</code>, <code>numeric</code>, <code>month</code>, <code>year</code> or <code>iso</code>, and text cut to <code>words-25</code> or <code>chars-140</code>.</li>
</ul>
<pre><code data-lang="template">{{ each:journal:has-cover:6 }}
  &lt;a href="{{ item.url }}"&gt;{{ item.title }}&lt;/a&gt;
  &lt;time&gt;{{ item.date:short }}&lt;/time&gt;
{{ else }}
  &lt;p&gt;Nothing here yet.&lt;/p&gt;
{{ /each }}</code></pre>
<h3>Pages of a list</h3>
<ul>
<li><code>{{ each:journal:10:paged }}</code> splits a list into pages: <code>/journal/</code>, <code>/journal/page/2/</code> and on.</li>
<li><code>{{ paging.next }}</code>, <code>paging.previous</code>, <code>paging.number</code> and <code>paging.total</code> make the links between them.</li>
</ul>
<h3>Tags</h3>
<ul>
<li>Any page can have tags, set in Page settings and kept in <code>page.json</code>.</li>
<li><code>{{ each:tags }}</code> and <code>{{ each:item.tags }}</code> list a page's tags, each linking to its tag page.</li>
<li>A page with <code>"tags-of": "journal"</code> becomes the list of that folder's tags, and Verso makes a page for each tag beneath it. <code>{{ page.tag }}</code>, <code>{{ each:tagged }}</code> and <code>{{ each:all-tags }}</code> fill them in.</li>
</ul>
<h3>Repeaters, site fields and parts</h3>
<ul>
<li>Repeaters: <code>{{ list:team }}…{{ /list }}</code> is a list of items edited right on the page, each with fields of its own.</li>
<li>Site fields: <code>{{ site.footer:text }}</code> is the same on every page, edited once, and kept in <code>content/site.json</code>.</li>
<li>Parts: <code>{{ part:header }}</code> brings in <code>parts/header.html</code>, so templates share HTML. Errors point at the part's own file and line.</li>
<li>Parts take values, so they work like components: <code>{{ part:card title=item.title label="Read more" }}</code>, shown with <code>{{ part.title }}</code> and checked with <code>{{ if:part.title }}</code>.</li>
</ul>
<h3>Channels, feeds and hosting</h3>
<ul>
<li>Channels: list a folder of posts in <code>verso.json</code>, and the editor gets a panel to find, write, duplicate, draft and delete its posts.</li>
<li>Each channel gets an RSS feed at <code>/&lt;folder&gt;/feed.xml</code> once the site has a <code>"url"</code>, linked from its pages.</li>
<li><code>"base": "/blog"</code> builds a site that lives in a sub-folder. <code>&lt;html&gt;</code> carries <code>data-base</code> for scripts.</li>
<li>The editor shows the numbered pages of a split list and every tag page, each with the editor of the page it comes from.</li>
</ul>
<h3>Fixes</h3>
<ul>
<li>A <code>"pre code"</code> key in the rich class map styles code blocks apart from inline code.</li>
<li>Pages are named by their title, without a “ — Site name” tail, instead of their folder.</li>
<li>The editor stays above a site's sticky header.</li>
<li>Images shown with <code>{{ item.cover }}</code> bring their alt text.</li>
<li>An empty colour in a <code>style</code> attribute writes <code>initial</code>, so <code>var()</code> fallbacks work.</li>
<li><code>{{ parent.parent }}</code> explains that Verso only looks one level up, instead of showing nothing.</li>
<li>The editor serves <code>pages.json</code>, <code>sitemap.xml</code> and feeds, so scripts that read them work while editing.</li>
<li>The editor recompiles CSS when a script in one of Elevate's <code>Watch</code> folders changes.</li>
<li>Bar buttons appear in the page menu on phones.</li>
</ul>
<h3>Elevate 1.3</h3>
<ul>
<li>Attribute states: <code>@current</code>, <code>@expanded</code>, <code>@selected</code>, <code>@pressed</code> and <code>@open</code> style an element by its ARIA or open state, so a script sets an attribute instead of swapping classes.</li>
<li><code>font-numeric</code> sets tabular, oldstyle and other figures.</li>
<li>The <code>hidden</code> attribute always hides, even on an element with a display class like <code>row</code>.</li>
</ul>
<pre><code data-lang="html">&lt;a href="https://verso.pub/docs/" class="text:ink-3 @current:[text:ink]"&gt;Docs&lt;/a&gt;</code></pre>]]></content:encoded>
      <category>Templates</category>
      <category>Editor</category>
      <category>Building</category>
      <category>Elevate</category>
    </item>
    <item>
      <title>0.9: Build it in the browser — Verso</title>
      <link>https://verso.pub/changelog/0-9-build-it-in-the-browser/</link>
      <guid>https://verso.pub/changelog/0-9-build-it-in-the-browser/</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <description>A whole site can now be built in the editor, without opening a file.</description>
      <content:encoded><![CDATA[<p>Until now, writers could change a Verso site in the browser, but building one still meant writing templates. This release closes that gap. A first-time user built a portfolio from a new site to a published commit, nine steps, without touching a file.</p>
<h3>Site and design</h3>
<ul>
<li><strong>Site settings:</strong> the site's name, address, sub-folder, language and search, in one panel.</li>
<li><strong>Colours and sizes edited in place:</strong> click a colour to change, rename or trace it; give a size a phone value and a wide-screen value.</li>
<li><strong>Text styles:</strong> how headings, links, quotes, code and tables look in articles, chosen from the site's tokens, with a live sample.</li>
</ul>
<h3>Blocks</h3>
<ul>
<li><strong>Build a block, in words:</strong> lists of pages (sorted, filtered, split into pages, leaving out this page, with words for when there are none), lists of items, "show only when", counts, previous and next pages, this page's title, date and tags, and text shared by every page.</li>
<li><strong>Grid columns</strong> per screen size, readable names instead of tags, and the site's colours and article styles first.</li>
<li><strong>A shared header and footer</strong> built from blocks: <code>{{ site.header:blocks }}</code> keeps them in <code>site.json</code>, so a change on any page changes every page.</li>
<li><strong>Lists of items inside blocks</strong>, with the first item one click away.</li>
</ul>
<h3>Pages and channels</h3>
<ul>
<li><strong>Page types:</strong> make one from an existing type, and start new pages like the one you're on, with Undo.</li>
<li><strong>Channels set up visually:</strong> turn a folder into a channel, or make a new one whose page already lists its posts.</li>
<li><strong>Tag pages</strong> from Page settings, drafts that show while you're editing, and making a draft live from its own page.</li>
</ul>
<h3>The starter</h3>
<p>New sites are block-built: a shared header and footer, thirteen blocks, a journal channel, topics for its tags and starting layouts for new pages.</p>]]></content:encoded>
      <category>Editor</category>
      <category>Design</category>
      <category>Templates</category>
    </item>
    <item>
      <title>0.1: Elevate 1.2 — Verso</title>
      <link>https://verso.pub/changelog/0-1-elevate-1-2/</link>
      <guid>https://verso.pub/changelog/0-1-elevate-1-2/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Before Verso could start, Elevate needed a watcher that keeps up, restarts on design changes, and an API other tools can call.</description>
      <content:encoded><![CDATA[<p>Verso renders pages itself and asks Elevate for the CSS, so Elevate had to work as a library, not only as a command. These changes shipped as Elevate 1.2.0 and 1.2.1 on npm.</p>
<h3>A watcher that keeps up</h3>
<ul>
<li>Elevate compiles once on start, then again whenever a template is saved, added or deleted. CSS from deleted templates no longer lingers.</li>
<li><code>Watch</code> takes a list of folders, so templates, blocks and scripts can all be scanned.</li>
<li>Saving a file in <code>config/</code>, <code>design/</code> or <code>rules/</code> restarts the compiler, so new tokens apply at once. Saving an <code>Extend</code> file recompiles.</li>
</ul>
<h3>Commands and an API</h3>
<ul>
<li>New commands: <code>build</code> compiles once and fails loudly, <code>check</code> names every bad class in a list, and <code>describe</code> prints the design system as JSON.</li>
<li><code>core/api.ts</code> exports <code>build</code>, <code>validate</code>, <code>describe</code> and <code>scan</code>, with no side effects on import. Verso's checks, block builder and design editor all use it.</li>
</ul>
<pre><code data-lang="bash">$ npx elevate-framework check "font:bodoni:h3 text:proof"
$ npx elevate-framework describe --json</code></pre>
<pre><code data-lang="js">import { validate } from './elevate/core/api.ts';
const { problems } = validate('pd:d4 text:ink');</code></pre>
<h3>Safer upgrades</h3>
<ul>
<li>Running <code>prepare</code> again replaces only <code>elevate/core</code>, keeps the old core in <code>.elevate-backup/</code>, and leaves config, design, rules and templates alone (1.2.1).</li>
<li>A failed build no longer hides scan errors, and <code>elevate.css</code> is written in one step instead of being emptied first.</li>
<li>Earlier fixes along the way: breakpoint classes stay on their own elements, hex colours work inside pass-through values, and grid columns can't be stretched by long content.</li>
</ul>]]></content:encoded>
      <category>Elevate</category>
    </item>
    <item>
      <title>0.2: First page — Verso</title>
      <link>https://verso.pub/changelog/0-2-first-page/</link>
      <guid>https://verso.pub/changelog/0-2-first-page/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>A site from one command, click-to-edit, autosave and Publish.</description>
      <content:encoded><![CDATA[<p>The first working Verso: one command makes a site, and the site is the editor.</p>
<pre><code data-lang="bash">$ verso new my-site
$ cd my-site
$ verso</code></pre>
<ul>
<li><code>verso new</code> makes a styled two-page starter with Elevate set up and a first restore point.</li>
<li><code>verso</code> opens the editor: the real page, rendered from its templates and Elevate CSS. Click text to edit it; changes save as you type.</li>
<li>Page settings hold the search title and description, with a preview of how the page appears in results, and any field that isn't visible on the page.</li>
<li><strong>Publish</strong> commits with a message that says what changed, then pushes. It pulls in other people's changes first, explains a clash in plain words, and refuses anything the host's build would reject.</li>
<li><code>verso build</code> writes the static site to <code>dist/</code>.</li>
<li>Templates, classes and content are checked as you work. Every problem names its file and line, and the page recovers once the problem is fixed.</li>
<li>The editor's own interface is built with Elevate.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Templates</category>
      <category>Building</category>
    </item>
    <item>
      <title>0.3: Rich text and images — Verso</title>
      <link>https://verso.pub/changelog/0-3-rich-text-and-images/</link>
      <guid>https://verso.pub/changelog/0-3-rich-text-and-images/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Rich text edited in place, image fields, lists of pages, new pages from templates, and undo.</description>
      <content:encoded><![CDATA[<h3>Rich text</h3>
<ul>
<li>Rich text fields are edited on the page itself. The toolbar shows only the tools the template allows: headings, lists, links, images with captions, tables, quotes and callouts.</li>
<li>Each field is saved as clean HTML in its own file, and styled by the class map in <code>verso.json</code>, so the stored HTML carries no styling of its own.</li>
</ul>
<pre><code data-lang="json">{
  "rich": {
    "h2": "font:bodoni:h3:medium mg-t:d13",
    "a": "text:ink:underline @hover:[text:proof-2]"
  }
}</code></pre>
<h3>Images</h3>
<ul>
<li>Click an image field to choose or replace it, or drop a file on it. Alt text sits beside it.</li>
<li>Images live in the page's own folder. Uploads are checked by their bytes, not their names, and built pages get every image's width and height.</li>
</ul>
<h3>Templates</h3>
<ul>
<li><code>{{ each:journal:newest:10 }}</code> lists pages, <code>{{ if:image }}</code> shows a part only when a field is set, and <code>item.</code> and <code>page.</code> reach other fields. Every mistake is reported with a plain explanation and a line number.</li>
</ul>
<h3>Pages and undo</h3>
<ul>
<li>Make a new page from the editor by choosing a template from live previews.</li>
<li>Undo and redo work across the whole page, and every page has a date.</li>
<li>Publish messages name new pages and changed rich text.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Building</category>
    </item>
    <item>
      <title>0.4: Blocks, history and design — Verso</title>
      <link>https://verso.pub/changelog/0-4-blocks-history-and-design/</link>
      <guid>https://verso.pub/changelog/0-4-blocks-history-and-design/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Blocks you drag onto the page, a visual site tree, a timeline of every publish, a block builder and an editor for the design tokens.</description>
      <content:encoded><![CDATA[<p>This was the largest release, stages three to five of the original plan. Verso stopped being a text editor for fixed pages and became a way to arrange whole pages.</p>
<h3>Blocks</h3>
<ul>
<li>Templates and blocks mark slots with <code>{{ name:blocks:allowed }}</code>. Writers drag blocks from a live library into a slot, and a drop zone only appears where that block is allowed.</li>
<li>Blocks nest. Each one has handles to move, duplicate and remove it.</li>
</ul>
<pre><code data-lang="template">&lt;div&gt;{{ sections:blocks:hero:quote:gallery }}&lt;/div&gt;</code></pre>
<h3>The site view</h3>
<ul>
<li>A visual tree of every page. Drag a page to move its folder; its address follows and links to it are rewritten.</li>
<li>Drafts stay out of the build.</li>
</ul>
<h3>History</h3>
<ul>
<li>A timeline of publishes, each with a preview and a restore button.</li>
<li>If two people change the same page, Verso shows both versions side by side to choose from, instead of a merge conflict.</li>
</ul>
<h3>Build a block, and design</h3>
<ul>
<li>A block builder with pickers that only offer the site's tokens, per breakpoint. Edits are surgical: hand-written code is left byte for byte.</li>
<li>A design editor for colour ramps in OKLCH with contrast checks, fluid type sizes and fonts. Renaming or removing a token shows where it is used first. Elevate compiles the result.</li>
<li>Extensions: <code>src/extensions/</code> for the server, <code>editor/ext-*.js</code> for the editor. On phones their buttons move into the page menu.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
      <category>Design</category>
      <category>Templates</category>
    </item>
    <item>
      <title>0.5: Components and the palette — Verso</title>
      <link>https://verso.pub/changelog/0-5-components-and-the-palette/</link>
      <guid>https://verso.pub/changelog/0-5-components-and-the-palette/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Reusable components, a command palette, video embeds, responsive images and nesting pages on touch screens.</description>
      <content:encoded><![CDATA[<h3>Components</h3>
<ul>
<li>Save any arrangement of blocks as a component, kept in <code>components/&lt;name&gt;.json</code>. The structure is shared by every page that uses it. The content belongs to each page.</li>
<li>Lock a field to make it read the same everywhere, such as a legal line in a footer.</li>
<li><strong>Detach</strong> turns a component back into plain blocks on one page. Removing a block can be undone.</li>
</ul>
<h3>The command palette</h3>
<ul>
<li>Press <strong>⌘K</strong> or <strong>Ctrl K</strong> to jump to a page or to a field on this page, or to run an action or add a block. It has fuzzy search and remembers recent choices.</li>
</ul>
<h3>Media</h3>
<ul>
<li>Rich text can embed YouTube and Vimeo videos. Each one is stored as the exact player address, nothing else.</li>
<li>Images are resized at build to 640, 1024 and 1600 pixels wide, never upscaled, and served with <code>srcset</code>. The resizing is pure JavaScript and is cached in <code>.verso-cache/</code>.</li>
<li>Typing can no longer replace a figure by accident.</li>
</ul>
<h3>Small screens</h3>
<ul>
<li>The site view has <strong>Move into…</strong> for nesting pages without dragging.</li>
<li>The editor reloads when <code>blocks/</code> or <code>components/</code> change.</li>
<li>The site view closes with Escape and only reopens after a move.</li>
</ul>]]></content:encoded>
      <category>Editor</category>
    </item>
    <item>
      <title>0.6: Magazines — Verso</title>
      <link>https://verso.pub/changelog/0-6-magazines/</link>
      <guid>https://verso.pub/changelog/0-6-magazines/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Pages that list their own children, siblings and grandchildren, parent references, and colour fields, found while building a magazine with editions.</description>
      <content:encoded><![CDATA[<p>Halftone, a magazine with numbered editions and articles inside each one, needed things a flat folder list couldn't do. Every addition below came from a page of that magazine.</p>
<h3>Lists that follow the tree</h3>
<ul>
<li><code>{{ each:children }}</code> lists the pages inside this one, such as the articles in an edition.</li>
<li><code>{{ each:siblings }}</code> lists the pages beside this one, such as the other articles in the same edition.</li>
<li><code>{{ each:item }}</code> inside an outer list goes one level deeper, such as the articles of each edition on the archive page. Lists nest two levels at most.</li>
<li><code>skip-2</code> leaves out the first two items, for "earlier editions" after the latest one.</li>
</ul>
<pre><code data-lang="template">{{ each:editions:newest:skip-1 }}
  &lt;h3&gt;{{ item.title }}&lt;/h3&gt;
  {{ each:item:order }}&lt;a href="{{ item.url }}"&gt;{{ item.headline }}&lt;/a&gt;{{ /each }}
{{ /each }}</code></pre>
<h3>The page above</h3>
<ul>
<li><code>{{ parent.number }}</code> shows a field of the page above, such as an article's edition. It works in references and in conditions, like <code>{{ if:parent.cover }}</code>.</li>
</ul>
<h3>Colour fields</h3>
<ul>
<li>A <code>color</code> field lets writers pick one of the site's colour tokens and renders its value. Set it as a CSS variable to theme one page: each edition of Halftone chooses its own ink.</li>
</ul>
<pre><code data-lang="template">&lt;article style="--ink: {{ ink:color }}"&gt;</code></pre>]]></content:encoded>
      <category>Templates</category>
    </item>
    <item>
      <title>0.7: Docs and code — Verso</title>
      <link>https://verso.pub/changelog/0-7-docs-and-code/</link>
      <guid>https://verso.pub/changelog/0-7-docs-and-code/</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <description>Code blocks, a search index, a sitemap, 404 pages and a flag for page scripts, found while building this website.</description>
      <content:encoded><![CDATA[<p>Building Verso's own documentation meant writing about code, so rich text had to hold code properly. A docs site needs search, a sitemap and a real 404 page, and an interactive page needs to know when it is being edited.</p>
<h3>Code in rich text</h3>
<ul>
<li>A new rich text tool, <code>code</code>, adds code blocks and inline code. Type three backticks, a language and a space to start a block. Whitespace is kept exactly, and the language is saved as <code>data-lang</code>.</li>
<li>Inline code: press <strong>⌘E</strong> or wrap words in backticks. Inside a block, Tab inserts two spaces and ⌘Enter leaves the block.</li>
<li>Ordered lists come with the <code>lists</code> tool.</li>
</ul>
<pre><code data-lang="template">{{ body:rich:headings:lists:links:code }}</code></pre>
<h3>For page scripts</h3>
<ul>
<li>In the editor, <code>&lt;html&gt;</code> carries <code>data-verso-editing</code>. A script can check for it and leave editable fields alone, so highlighting or reflowing never fights the person typing.</li>
</ul>
<pre><code data-lang="js">const editing = document.documentElement.hasAttribute('data-verso-editing');
if (!editing) highlightCode();</code></pre>
<h3>Order, search and the rest</h3>
<ul>
<li><code>{{ each:docs:order }}</code> sorts pages by the order set in the site view. Pages without an order come last, by title.</li>
<li>With <code>"index": true</code> in <code>verso.json</code>, the build writes <code>pages.json</code>. It lists every live page with its title, description, headings and text, ready for search.</li>
<li>With <code>"url"</code> set, the build writes <code>sitemap.xml</code>.</li>
<li><code>content/404/</code> also becomes <code>dist/404.html</code>, which most hosts show for missing pages.</li>
</ul>]]></content:encoded>
      <category>Templates</category>
      <category>Editor</category>
      <category>Building</category>
    </item>
  </channel>
</rss>
