Tend

Formerly Nudge: renamed in 2.9 to sit with Trellis and Sage. Same app; it installs alongside an old copy of Nudge rather than replacing it, with its own backups folder.

A small Mac app for adjusting self-contained HTML presentations and reports without coming back to Claude for every tweak.

Two modes, switched with ⌘E:

• Wording — click any text in the live preview and type, and set how those words look: size, alignment, weight and colour.
• Layout — click any element and adjust its size, spacing, position or order.

Version 2.9.

What changed in 2.8

• A new typeface. The interface is set in Atkinson Hyperlegible Next instead of Outfit, matching chriskeene.me. The Braille Institute designed it for legibility, particularly for low-vision readers, which suits an interface that is mostly small text. Nothing needed resizing: measured label by label it comes out within a few points of Outfit, and nothing that fitted before stops fitting.
• --fontcheck checks every weight, not just the family name, so a copy whose weights all collapse onto one face is caught too.
• The tests draw with the faces that ship. The interface harnesses used to pick the typeface up from whatever the Mac had installed, so a missing face would have been measured as the system font and passed. They now register the bundled faces, and a check fails if any weight falls back.

Why it doesn't just use a browser's copy of the page

Almost every "edit HTML visually" tool sets contenteditable and then reads back document.documentElement.outerHTML. That is unsafe for decks like these.

These files run their own JavaScript. A deck's navigation script does things like:

count.textContent = (i + 1) + ' / ' + slides.length;
where.innerHTML   = sect + ' &middot; <b>' + label + '</b>';
slides.forEach(function (s, x) { s.hidden = doc ? false : x !== i; });

Serialising the DOM after that has run bakes the current state into the file permanently: save while viewing slide 3 and every other slide gets a hidden attribute. The deck is destroyed. The slide counter freezes. Inline styles that the script set become part of the document.

So Tend never serialises a DOM. It:

1. Scans the original file with an offset-tracking tokeniser, recording the exact character range of every run of human-readable text (skipping <script>, <style>, comments and markup).
2. Renders the real, unmodified file in a WebKit view, and holds its text nodes in a plain JavaScript array — so mapping a click to a source offset costs no change to the document at all.
3. Aligns the two sequences, tolerating text the deck's own JavaScript invents.
4. On save, splices your new text into those byte ranges, back to front so earlier offsets stay valid.

Everything you did not edit is preserved byte for byte: CSS, JavaScript, indentation, comments, attribute order, entity spelling.

What it edits

Wording mode

• Body copy (headings, paragraphs, list items, table cells, buttons, captions)
• Accessibility and label attributes: alt, aria-label, title, aria-description, placeholder, data-label
• The <title> element and <meta name="description">
• Link destinations (href), under their own filter so they stay out of the way
• How the selected words look: size, alignment, weight and colour

Layout mode

• Width (as a percentage of the container, so it still responds) and height
• Space above, space below, padding, and the gap between a container's children
• Position: shift one item across or down without moving anything beside it
• Order: move an element before or after its sibling
• Duplicate and delete

Setting a height can hide content, but only where the element actually clips: overflow: visible lets it spill and stay readable, which is how plenty of these decks are built. Warning on scrollHeight > clientHeight alone cried wolf on untouched slides, so the warning needs both a height Tend has set and an element that really clips.

Layout changes are written as inline declarations on the specific element you selected. Nothing touches the stylesheet, so one adjustment can never quietly restyle the other fourteen slides.

Written for people who don't write HTML

The interface never says <dd>, aria-label or div.stat-card at anyone. Markup is translated into words a salesperson would use: Title, Paragraph, Value, Button, Image description, Screen-reader label. The precise markup is still there in a tooltip for whoever wants it.

Three things follow from that:

• The list is grouped by slide, slides first. Source order would open on the skip link and the navigation rail, which is a baffling first thing to meet. Everything that sits around the slides is gathered at the end under "Page furniture".
• A sentence stays a sentence. Inline markup splits Three pillars: a <b>lower engineering cost</b>, and … into seven separate runs. Correct for editing, nonsense to read, so the list shows the whole sentence as one row and says how many pieces it has. Clicking the slide, searching, and Tab still reach every individual piece.
• Nothing destructive happens silently. Deleting asks first and says what is inside the thing you are removing.

There is a short guide under Help, shown once the first time a file is opened.

The bar across the top

Title hard left, the Wording / Layout switch centred on the window, and the actions including Open on the right.

There is no app icon in it. The icon is already in the Dock, the app switcher and Mission Control; inside the app's own window it says nothing new and competes with the one thing that strip is for, which is telling you what file you are in. The CK mark in the bottom corner is the only mark in the window.

This is the beginning of the README. Read the rest at the original. Read the full README ↗