nextDash 1.3.3 rebuilds the page you land on. The overview used to answer “what is new?” in different places at once, none of them well, while the news from the project itself sat below the fold on most screens. It is one list now, newest first. The form for adding a bookmark got the same treatment for the same reason — it had grown taller than a laptop screen, so the Save button was out of sight on the machine most people use. Behind those two visible changes sits something less glamorous and more important: an audit of the whole codebase. It turned up three separate ways you could lose bookmarks, a folder of your private data that was readable by anyone who could reach the app, and outage alerts that never left the building for an entire category of users. All of that is fixed here, and none of […]
A hover card that printed the address twice, hid the one state worth acting on, and slid away when you reached for it. This release rebuilds it into three bands that answer three questions — and gives it everything the rest of the app already knew about the link. Hover a bookmark on the old dashboard and a card appeared. It showed you the title, the full URL in mono, the hostname on the next line, a picture, and the description the page had advertised about itself. Seven stacked divs, two of them saying the same thing. The row underneath it was already showing more. The status dot knew whether the site had answered this morning. The Fresh count knew whether it had published anything. The shortcut letter knew how to reach it without a mouse. The card explaining the row knew less than the row. v1.3.2 rebuilds it. The […]
The other smart collections all answer questions about what you did. Fresh answers the one none of them could: which of these links is worth opening right now. Open your dashboard and look at a category. Every row is identical in the only way that matters — none of them tells you whether anything happened behind it. A blog you follow, a project’s changelog, a forum thread, a status page: they keep publishing, and the row keeps looking exactly the same as the login screen two lines down. So you do one of two things. You open them on the off-chance, which is mostly wasted clicks. Or you stop opening them at all, which is how a bookmark quietly becomes dead weight. Fresh is the answer to that, and it is smaller than you would expect. When a page you have saved advertises an RSS or Atom feed, nextDash notes […]
nextDash 1.3.0 is out with two dozen changes with one subject running through nearly all of them — the life of a link. How it gets in when you are nowhere near the machine with the extension. How you find out it has rotted, and how long it has been rotting. How the tidying becomes something you can actually finish instead of a number you learn to ignore. And how a page you saved a year ago can tell you it has published something since. Running alongside all of that is a fourth strand: the dashboard’s first load is about five times lighter than it was. It also contains an apology. The change to how bookmark shortcuts open, which shipped in 1.2.0 and which this blog described approvingly at the time, was a mistake. It is reverted, and the reasoning is below. 1.3.0 bumps the release marker, so the What’s […]
nextDash 1.2.0 is already out! It is the keyboard release — typing on the dashboard now does only what you meant it to — and it is the release where three views stop claiming to know more than they do: the inbox was counting links it was not showing you, and a failed health check worked out exactly why it had failed and then threw that away. And this morning, 1.2.1 followed with a single fix in Health, which is covered at the end. Source and downloads: github.com/jordibrouwer/nextdash — release notes: CHANGELOG.md nextDash 1.2.0 — 16 August 2026 What you type arrives whole This is the fix that matters most, and it is worth explaining properly, because the old behaviour was subtly worse than it looked. Bookmark shortcuts fired the moment the typed text matched one exactly. Type github with a shortcut on git and the bookmark opened after three […]
Categories across columns The grid has always been a set of columns, and a category has always lived in exactly one of them. That works until one category is much longer than the rest — your dev links, or whatever your equivalent is — at which point you either accept a page with one very tall block and a lot of white space beside it, or you accept that most of that category lives behind a “+ N more” link. Spreading is the third answer: the bookmarks run across the grid instead of down it. Go straight to Github: github.com/jordibrouwer/nextdash — release notes: v1.1.0 on GitHub A long category can spread across columns. Right-click a category header and pick Spread across columns, or press Shift + W while you are on it. Its bookmarks flow across the columns it is allowed and the block stays the height of its neighbours. […]
nextDash 1.0.3 is out, and it closes a gap that had been sitting in the app for a long time: nextDash has always recorded when you added a bookmark, when you last opened it, how often you open it and what you tagged it — and almost none of that ever reached the parts of the app you actually drive. This release hands it over. It arrives on the back of two smaller releases, 1.0.1 and 1.0.2, which went out quietly over the two days before it; all three are covered below. If you have been running nextDash since the 1.0.0 milestone, this is the first release that will reopen the What’s new modal for you. Both 1.0.1 and 1.0.2 were deliberately muted so they would not push a second dialog in front of anyone who had just read the 1.0 notes. That mute has now been lifted on both, […]
Every release of nextDash up to now has carried a date instead of a version number: v2026.09.09, v2026.09.09.1, v2026.09.09.2, and so on, a new tag almost every day through a long stretch of active development. v1.0.0, released today, breaks that pattern on purpose. It’s the first release under semantic versioning, and it’s a deliberate milestone rather than an incremental one: after a long run of bug fixing and consolidation, the app finally feels finished and stable rather than in flux. From here, 1.x.0 releases carry new features and 1.0.x releases carry fixes — a distinction the date-based scheme never made. The comparison logic for the new numbering actually shipped a few point releases earlier, under v2026.09.09.3, so v1.0.0 is really the moment the switch was made official. What’s inside is almost entirely correctness work, and it follows one recurring shape: an operation that reported success for something it hadn’t actually […]
