Weather gets a page of its own, and the pages it touches say so The Weather page is a guide like the other modules': the page from top to bottom, adding a place and zip codes, units, the map, air quality and how it keeps current. Home lists it with Ctrl+0, Calendar describes the weather strip beside the date, and the shortcuts page is generated again, so Ctrl+0 and Add Location are on it. Hardening's list of what leaves the machine no longer calls the update check the only outbound feature that is not your mail: it says what the Weather module asks, of whom and with what, and what Work Offline does and does not stop.
A guide for each of the seven modules The wiki had four reference pages and no prose: somebody who had installed the application could look up a shortcut or read about the theme engine, and could not find out what the Journal module is for or how to make an appointment that is not half an hour long. Seven pages, one a module — what it is for, the views it offers, and the five things people actually go looking for — linked from Home above the reference pages. Written against the tree rather than from memory, and four claims were wrong before they were checked: the search grammar is `attachment:yes` and `received:thisweek`, not `has:attachment` and `after:`; the alphabet index is a switch rather than always on; and there is no Notes-and-Journal options page to send anybody to, because those two modules have nothing to configure. Each page says what its module does not do as well, where that is the thing a reader would otherwise spend an afternoon looking for: a contact's Activities cannot find their journal entries, and the Journal will never watch your documents the way the reference's did. Co-Authored-By: Claude <noreply@anthropic.com>
Every shortcut, generated rather than remembered The application has a ribbon, four themes, a rules wizard, a plugin host and a rebindable key for nearly every command, and nothing outside it said what any of those keys were. This is that list: by window, then by module, with each command's own chord and the extra ones a few of them carry. It is generated — tools/export-shortcuts.sh reads the same command catalogue the running application resolves keys through — because a transcribed shortcut list is wrong within a month and nothing tells a reader which half to trust. The last section is the part no catalogue can answer: the keys a surface takes for itself, which are not commands and cannot be rebound. The three calendar views are there in full, now that all three answer the arrows.
The plugin reference gets a page a reader can reach It was a file in the repository's docs directory, which is not where somebody looking for it would think to go, and that directory is no longer published at all. The API is versioned and refuses a mismatch at the door, so the reference belongs somewhere it can be read without a checkout.
The themes reference stops pointing into the repository
Hardening evidence re-pinned to v0.6.0
One sentence, not two
Animated themes animate
The Themes page: what the engine does, and the plain words about community themes
Re-pin code permalinks to the refreshed v0.5.0
The link's own label matches its anchor
Re-pin code permalinks to v0.5.0
The hardening evidence points at v0.0.5
The engine-profile anchor points where the code moved
The Hardening page: every layer, with the code that makes it true
Initial Home page