Skip to content

v1.32.0 is out small homelab tools in search and cleaner feed titles

nextDash

News · Changelog

Changelog

Every nextDash release since v1.0.0, newest first. Open a line to see what is new and what got fixed, or pick the version you run to see everything since.

November 2026

v1.32.0 Small homelab tools in the search panel, clean titles for the RSS widget and Watch feeds, and a round of Compose, widget and reminder fixes. +5 8 fix Read the post

Small homelab tools in the search panel, clean titles for the RSS widget and Watch feeds, and a round of Compose, widget and reminder fixes.

Search

  • New
    Small homelab tools in the search panel

    Typing one of these answers as the first row, and Enter copies the answer: sha256 <text>, sha1 <text> and md5 <text> (written out in the page, since crypto.subtle is missing on a plain-http address and has no md5); base64 <text> and base64 decode <text>; urlencode <text> and urldecode <text>; uuid; pass <length> (8 to 128, drawn without bias from crypto.getRandomValues); timestamp for the time now and a lone Unix time of ten digits (seconds) or thirteen (milliseconds) between 2001 and 2100; 192.168.1.0/24 for the range, the number of addresses, the usable hosts and the mask; 255.255.255.0 for /24 and mask 22 for the mask; 8096 or port 8096 for the service that uses a port (74 are known); chmod 755 and rwxr-xr-x, with setuid, setgid and sticky; and cron 0 9 * * 1-5, which says what the schedule means and when it runs next, with @daily and day and month names. Enter copies the schedule itself, not the sentence about it. Each has its own word or shape, so a plain word, a name or an unknown number is never an answer (pass is still a bookmark; pass 20 is a password). The calculator keeps priority when both fit.

  • New
    Suggestions while you type a tool's command

    The first letters of a tool's word (cr, sha) put a hint under the bookmarks with the shape of the command. The word and a space, or a command that does not work yet, puts working examples on top; picking one fills it in and the answer follows. A whole IPv4 address offers /24. A bare word such as pass or port is only offered under the list, so Enter still opens a bookmark of that name (SearchTools.suggest).

  • Fix
    A / after an IPv4 address is a slash

    In the open panel / is the mode switch and put itself in front of the query, so 192.168.1.0/24 could not be typed. After a whole IPv4 address, or mask , it is now a character; everywhere else it still switches.

  • New
    Paste into the open search panel

    On a computer the panel is not a text field, so Cmd+V had nowhere to land. A paste while it is open now goes in as if typed, on one line and with only the characters typing takes. With the panel closed a pasted link still goes to quick-add.

  • Fix
    A failed copy says so, and long answers wrap

    If an answer cannot be put on the clipboard, a message shows the text so it can be taken by hand, where it used to do nothing. The fallback focuses and selects its field the way Safari wants. A row with an answer wraps over lines instead of ending in dots.

Widgets

  • New
    Clean up titles in the RSS widget

    Config → Widgets → RSS gets Title: remove or find and Replace with (empty removes), with a before and after of the feed's first title that changes. Suggest reads the feed's own titles and proposes a pattern for a shared beginning (an advisory number, brackets) or a shared | Site name ending, and only when most titles agree and none would be emptied; it never applies one by itself. The pattern is an RE2 regular expression of at most 200 characters, checked by the server on save and in the preview, since a lookahead that a browser accepts is refused here. A pattern that would empty a title keeps the original.

  • Fix
    A tab with an old copy of an every-page widget no longer undoes a change from another page

    Each copy now carries a revision (everywhereRev) that the server bumps on every change pushed into it. A save with a lower one keeps the stored title and shared settings and takes only the page's own keys; a save without a revision is taken as it is.

Watch feeds

  • New
    Clean up titles per feed

    The settings of a watched feed get the same Title: remove or find and Replace with, with Suggest and a preview, and its own Save. The titles are changed when shown (the list, new items, the bell, push and webhook notices); the stored items keep the feed's own titles, and the include and exclude word filters still match the original. A pattern that does not compile is refused with bad-title-pattern.

Bookmarks

  • Fix
    This weekend means the coming Saturday or Sunday

    The reminder preset took the next Saturday, so on a Saturday morning it skipped to a week later and on a Sunday it did not use the day it was. It is now the first Saturday or Sunday at 09:00 still ahead.

Containers

  • Fix
    Apply waits for a save already running

    Ctrl+S followed at once by Apply read the save in flight as a failure. Apply now waits for it, then saves whatever was typed since.

  • Fix
    An override file adds ports instead of replacing them

    The compose preview now merges the ports: of a later file into those before it, as compose does; only a list tagged !override replaces them.

  • Fix
    An empty env value does not take a secret's mask

    DB= above DB=secret handed the secret's mask to the empty line when an edited env file was merged back. An empty value is never masked, so it never stands for a mask.

  • Fix
    The restart baseline comes from the first poll that answers

    A failed first poll left the restart counts out, so every restart a container ever had read as a restart loop.

Docs

  • Docs
    Translations for the new strings

    The search tools' words come from a new searchTools group (32 keys: the words around an answer, the cron sentence in pieces, and one line per tool for the hints), the title cleanup from config.titleRewrite* (14 keys) and the failed copy from dashboard.calcCopyFailed, in all six languages. Day and month names in a cron answer come from Intl in the dashboard's language, so they need no keys; the commands and the answers themselves stay as typed.

  • Docs
    Config → Help

    The search paragraph gets Small tools (the commands, what Enter copies, the hints, paste), the RSS widget's entry names the title settings, and the Watch feeds paragraph adds cutting a pattern out of a feed's titles, in six languages. A new tip, tipFindTools, sits in the Finding group after the sums.

  • Docs
    Config → Overview and About → News & features

    Two entries with since: "v1.32.0" in overview-features.json: Search answers subnets, hashes and cron lines and Clean titles in the RSS widget and Watch feeds, ten keys each language.

  • Docs
    What's new

    v1.32.0.json, first in index.json, with both tokens in whats-new-stub.js (DASHBOARD_RELEASE, whats-new-v381) and the constants spec moved.

  • Docs
    README.md and MANUAL.md

    The README's Bookmarks line names the quick answers. The manual's search chapter gains the table of tools, the hints and paste; the RSS widget's paragraph and §14.4 describe the title settings. Four new screenshots from tests/manual-screenshots-v1-32.spec.js: 08-search-tools.jpg, 08-search-tools-help.jpg, 16-rss-title-cleanup.jpg and 12-watch-feeds-title-cleanup.jpg.

Only docs and tests changed in this release.

v1.31.0 Compose stacks you can read, edit, check and run from the Containers view, reminders on bookmarks, related links on the preview card, and a bell that rings less and shakes more. +38 15 fix Read the post

Compose stacks you can read, edit, check and run from the Containers view, reminders on bookmarks, related links on the preview card, and a bell that rings less and shakes more.

Bookmarks

  • New
    Reminders on bookmarks

    Set a time on a bookmark from its context menu (a drawn clock), with Z, with :remind <when> or :remind <name> <when> in the palette, or in the edit form; :remind clear removes it. A clock on the row shows that one is set, and a due reminder becomes a row in the bell that stays until you answer it. While the dashboard is closed the server looks once a minute for due reminders and pushes them once, as one combined push when several come due together; a reminder more than a week late is marked handled without a push, and the bell still shows it. A setting in Config turns the push off.

  • New
    Related links on the preview card

    The card of a bookmark gets a row with up to three links that belong with it, ranked on shared tags, the site, and bookmarks opened together. A tag or site counts for less the more of the library carries it, so a common site or a tag on a third of the library relates nothing by itself, and the same page under http and https or with and without www. is the bookmark itself, not a relation. The row has a checklist entry in the preview settings, a context menu item, and :related in the palette (Enter opens a link, Alt+Enter opens it in a new tab). GET /api/related?url= answers read-only.

  • New
    Shift+V opens What's new

    Listed in the keyboard help and the legends.

Search

  • Fix
    A tag typed in full is a best match

    Typing a bookmark's whole tag now ranks that bookmark first instead of among the fuzzy hits.

Config

  • Fix
    The key legend sits at the foot of Bookmarks and Data & backups

    , and there is no rule under the Config header.

Containers

  • New
    Compose stacks work in the demo

    The demo's five stacks (media, photos, security, infra, home) have a compose.yml and a .env in a folder of their own, written again at every reset, and their containers carry the labels a real compose project has. NEXTDASH_COMPOSE_MAP is set for the demo (/srv/stacks on its imaginary host). The demo's daemon plays the helper container: it reads the arguments of docker compose, checks the files (a YAML error with its line, a service without an image, a variable nothing sets), and changes the demo's own containers for Up (a missing service is made, a stopped one started, one whose image changed made again), Down (which stops the containers and keeps them, because a stack with none would leave the list and could not be brought up again until the reset), Pull and Restart, with the dry run the preview needs and compose version. Nothing runs a docker binary or reaches a registry. The compose routes moved from the demo's denied writes to its allowed ones.

  • Fix
    The stack panel stays open after a compose run

    Pressing Close on the progress window of a run that failed (Up, Down, Pull) counted as a press outside the panel and closed it, so the exit code and last lines were lost together with the panel. The drawer now ignores presses in that window.

  • New
    Find a stack's compose files from its labels (engine)

    NEXTDASH_COMPOSE_MAP (hostPrefix:containerPrefix, comma separated) says where a stack folder appears inside nextDash. A label path is mapped by the longest prefix, must still lie under that prefix after symlinks are followed, must be a regular file of at most 1 MiB, and compose files must end .yml or .yaml. The request names only the project; every path comes from the daemon's labels.

  • New
    Secrets masked in compose and env files (engine)

    Values under keys like password, secret, token, key, cred or private, in the map and the list form of environment, and every value in an env file, are replaced by •••••• in place, so comments and layout stay. A file that does not parse is masked line by line.

  • New
    See a stack's compose file

    GET /api/docker/compose/{project}/files answers the compose files and env files of a stack, masked, with a sha256 and the state of each (unmapped, missing, denied, outside, not YAML, too large), and what to add when the folder is not mapped. Not on other Docker hosts. Config → Containers' status gains the resolved map.

  • New
    Reveal one masked value

    GET /api/docker/compose/{project}/files/value gives back a single value the file view masked, behind the write token, never cached.

  • New
    Edit a stack's compose file

    The stack panel's Compose file and.env tabs get Edit: a plain text box on the file, an unsaved marker, Save and Reload. Save sends the version it loaded, so a file changed on disk since is refused and you choose Reload or Keep editing; a YAML error shows its line and column and puts the cursor there; a file on a read-only mount or without write permission says which, instead of a Save button. Only with NEXTDASH_DOCKER_CONTROL=1, and never for nextDash's own stack. The Backups tab lists the copies made before each save and restores one after asking.

  • New
    Up, Down and Pull for a stack

    The stack panel has Up, Down and Pull with the output as it runs, in the same progress list as an update; Down asks first and says that volumes and images stay. With control off, on nextDash's own stack or on another Docker host the buttons are disabled and say why.

  • New
    Save a stack's compose file (engine)

    PUT /api/docker/compose/{project}/files checks the YAML first (line and column on an error, 422), refuses a file changed on disk since it was opened (409, with the current sha256), keeps nextDash's own stack read-only, and copies the old file to data/compose-backups/ before every write. The file keeps its mode, owner and symlink; when the folder is not writable the answer says to set NEXTDASH_RUN_AS_ROOT=1 or fix ownership. GET …/files/raw hands over the unmasked file behind the write token.

  • New
    Compose file backups (engine)

    The last 20 copies per file are listed (GET …/backups) and can be put back (POST …/backups/{stamp}/restore); a restore first copies the current file. Backups stay out of the settings backup, since they can hold secrets.

  • New
    Run a stack's compose without a terminal (engine)

    POST /api/docker/compose/{project}/up|down|pull runs docker compose in a short-lived helper container (NEXTDASH_COMPOSE_IMAGE, default docker:29.7-cli; the socket's host path from nextDash's own mounts or NEXTDASH_COMPOSE_SOCKET) with the stack folder at its own host path, checks the file with compose config -q before Up, streams the output, and removes the helper whatever happens. Down never removes volumes. Not offered for nextDash's own stack or on other Docker hosts yet.

  • Fix
    nextDash's own helper containers stay out of sight

    The compose helper and the disk-size probe no longer show in the container list, the Glances and system views, or raise a crash notice when they exit non-zero.

  • New
    Check a stack's compose file without touching it (engine)

    POST /api/docker/compose/{project}/check runs compose config -q in a helper and answers {ok}, or 422 compose-invalid with the output and, when compose names one, the line and column. Same gates as Up, no container is locked. A body {file, content} checks that text in place of the file, fed to compose on stdin, so nothing is written.

  • New
    Edited, not applied (engine)

    Every successful whole-stack Up records the sha256 of the stack's files in data/compose-applied.json; the files answer carries appliedSha256 per file and pendingChange per file and for the stack. Only stacks nextDash itself brought up are flagged; Down forgets the record.

  • New
    Up, Pull and Restart for one service (engine)

    The run routes take ?service=, checked against the services in the stack's files and in its containers' labels (compose-unknown-service otherwise, compose-service-not-allowed for Down). Only that service's containers are locked.

  • New
    Restart and Pull and Up for a stack (engine)

    Run actions restart and update (validate, pull, up -d). An update writes the update history for every container whose image changed; nextDash's own stack stays refused.

  • New
    One log for the whole stack (engine)

    GET /api/docker/compose/{project}/logs/stream merges every container's log as NDJSON, each line tagged with its service and container; the history of all services comes out in time order first. Behind the write token like a container's log, no control needed.

  • New
    A Services tab in the stack panel

    The panel now opens on the stack's services: state, health, ports and the image, with round Up, Pull and Restart buttons per service that act on that service alone.

  • New
    Check, diff and Apply in the editor

    Check runs compose config on the text in the editor, saved or not, and marks the line it names, with a Go to line link. A Changes chip shows the diff of your edit against the file on disk before saving, and each backup has a Diff button that shows what restoring it would change. Apply checks, saves, then runs Up; a text that fails the check is never written, and if Up fails the file stays and the previous copy can be restored. Ctrl/⌘+S saves and Tab types two spaces (Esc then Tab leaves the field).

  • New
    Edited, not applied

    A chip on the stack heading, a dot on the Compose tab and a note on the Services tab appear when the file changed after the last Up nextDash ran.

  • New
    Stack Restart, Pull and Up, and a Logs tab

    Restart (asks first) and Pull and Up sit in the heading; the Logs tab follows every service in one stream, each line tagged, with a chip per service to filter.

  • Fix
    The stack panel no longer drops unsaved edits

    Going Back, opening another container or stack, pressing Escape or beside the panel, or restoring a backup now asks first and names the file whose text would be lost. Restore says so in its own question, and the page asks before a tab with an unsaved edit is closed.

  • Fix
    The Logs tab keeps following

    The end-of-stream markers no longer show as blank rows. When a service stops or is recreated (Up, Restart) the stream opens again from the last line, a dropped connection retries with a growing wait and says so instead of "Following", and after the last try a Reconnect button appears.

  • New
    The stack's Logs tab reads like a container's log

    Search with next match (Enter), Filter, All / stdout / stderr, Last N, Timestamps, Wrap, Copy, Download and Follow (f) now work on the whole stack, with a line count; the tab and the single-container logs window share one reader.

  • New
    Pause and Resume a stack's log

    A Pause button (key p) holds new lines back while the connection stays open; the status line says Live, Paused · N waiting, Reconnecting or Stream ended, and Resume brings in every waiting line.

  • New
    Open a stack's logs in the large window

    The Logs tab has an Open logs window button that shows every service of the stack in the same window as a container's log, with chips per service.

  • Fix
    The container panel keeps its image and stack link after Back

    Coming back from the stack panel with its back link left the chips under the tabs empty, because the container was reopened by name only; it is now looked up in the list first.

  • New
    The stack link says where it leads

    The chip in a container's panel reads "Compose stack {name} ›" with a tooltip naming the services, compose file,.env, logs and backups.

  • New
    Info buttons in the stack panel

    An ℹ above the tabs explains Reload, Up, Down, Pull and Restart (and that nextDash runs compose in a helper container); each tab has one for Services, Compose file and.env, Logs and Backups, in the same modal as the view headers.

  • New
    The stack Logs tab is narrow-friendly

    Search, Pause and a ⋯ menu (Follow, Filter, stdout/stderr, Last N, Timestamps, Wrap, Copy, Download) fit one row, the log area uses the panel's height, and a labelled Open logs window button sits above the service chips.

  • Fix
    The stack heading in the list shows "Edited, not applied"

    The chip sits next to Files on every stack nextDash started, without opening the panel.

  • New
    Apply shows its steps

    Check, Save and Up appear as one list under the editor, each with its state. A failed Check says nothing was written; a failed Save says nothing was started; a failed Up says the file stays and offers the previous copy. A text too long to check (over 96 KiB) goes straight on to Save, since Up checks it.

  • Fix
    Editing a.env file no longer ends in a generic error

    A.env file has no Check button; Apply saves it and runs Up. A file that cannot be checked says so in words.

  • New
    Up asks before it recreates

    Up, Pull and Up and Apply confirm once: services whose file or image changed are recreated, and variables that only exist in your shell or an env file you passed by hand are blank in the helper.

  • New
    Compose files in Config → Containers

    The Connection panel shows the folders NEXTDASH_COMPOSE_MAP resolved to, what it refused, or the variable to set when none is.

  • Fix
    Small faults in the stack panel

    Two masked values on one line each get their own Reveal, named by key; Go to line follows the error you pressed; a second Edit says why nothing happens; the log chips say which one is on; the editor text is 16 px on phones so iOS does not zoom; the services table becomes one block per service on a narrow screen; the panel no longer keeps the unmasked text after a save.

  • New
    Variable check before Up (engine)

    POST …/check answers varCheck: each ${VAR} the compose files use that no env file sets, with the services, files and lines that use it. Unset without a default is a warning (it becomes blank), set empty on purpose is fine, ${VAR:?msg} and a missing env_file block. The same data rides on the 409 compose-unset-vars and the 422 compose-invalid of an Up, and an unsaved .env or compose text is checked in place.

  • New
    Preview what Up would change (engine)

    POST …/preview runs compose up -d --dry-run in the helper and answers what would be recreated, created, started, left alone or is an orphan, each with its reason (image, ports, config, new service, not in file); an unsaved edit can be previewed. A Compose older than 2.20 answers compose-too-old. Up takes ?removeOrphans=1, off by default.

  • New
    A watch on the stack after Up (engine)

    For a minute (longer for a long health-check start period) nextDash follows the stack's containers and says watching, slow, healthy or problem (GET …/watch, GET …/watches). A restart loop, an unhealthy or a failed container raises a container notice that follows the usual mute list, and POST …/watch/restore puts back the copy taken before the last save and runs Up again.

  • New
    Setup check data for Config → Containers (engine)

    The Docker status gains compose.setup: six checks (mapping, mount read-write, user and file owner, helper image, socket path, container actions), each ok or failed with a one-line fix in the real setting names such as NEXTDASH_COMPOSE_MAP, NEXTDASH_COMPOSE_IMAGE and NEXTDASH_COMPOSE_SOCKET.

  • New
    One summary line per stack (engine)

    GET /api/docker/compose/summary gives each stack its pending-change flag, health count, restarts in 24 hours and, when nextDash already samples them, CPU and memory, without any new stats polling.

  • New
    Edit a.env in place without losing its secrets (engine)

    An env file saved with masked: true keeps every value that is still the mask exactly as it is on disk; the mask text is never written as a value, by any save of any file. A backup can be compared with the current file (GET …/backups/{stamp}/diff) without a secret value in the answer: a changed secret reads as changed, not as what it was.

Dashboard

  • Fix
    The bell rings at most once per five minutes

    Several sources arriving close together, a second tab or a reload could each play the tone; now one tone sounds per five minutes, and the time of the last one is shared between tabs in this browser.

  • New
    The bell calls for attention more often while something is unread

    The badges pulse every 20 seconds (was 60, and only until the panel had been opened) and the bell shakes every 90 seconds (was every hour), both until the rows are read or answered. The shake is wider and the bell swells while it swings, and the badge pulse is larger.

  • Fix
    Dropping text that is not a link no longer leaves the dashboard

    Words or a mailto: link dragged in from another window were taken at dragover but not at the drop, so Firefox loaded them in the dashboard's tab. The drop is now cancelled whenever it was taken.

  • Fix
    The bell drops Immich failures once they are cleared

    With status tiles on two pages for one server, the bell kept the largest failed count, so a tile on a page left behind held it after the jobs were cleared. It now follows the newest answer per server.

  • Fix
    Show what's new works again

    In Config → News & features the button opens the release it belongs to. In the What's new modal, rows wrap on narrow screens and pictures show in the rows and larger.

  • Fix
    The preview checklist keeps its upgrade markers

    Saving settings no longer drops the markers that tell which checklist rows are new.

Docs

  • Docs
    README.md, MANUAL.md and the feature pages

    The README feature list names Compose stacks, reminders and related links, and its variable table has the four NEXTDASH_COMPOSE_* settings; the manual has the Reminders and Related links sections, Shift + V, :remind, :related and chapter 15.12; five new pictures under screenshots/manual.md/ come from tests/manual-screenshots-v1-31.spec.js.

  • Docs
    Config → Help, Tips, News & features, cheat sheet

    The bell's and the notifications' help say the new rhythm (every 20 seconds, every 90, one tone in five minutes) in all six languages; Help gains a Compose stacks paragraph under Containers and Related links under Bookmarks, and a Reminders paragraph under the bell. Tips tipReminder, tipRelatedLinks and tipComposeStacks; three News & features cards with since: "v1.31.0"; cheat sheet rows for Z, Shift + V, :remind and :related, and the sheet and its PDF generated again.

  • Docs
    translations

    234 strings of the stack panel that existed only as English fallbacks behind its t() wrapper, and 50 for reminders, related links and the Compose lines, are in all six locale files.

  • Docs
    static/data/whats-new/v1.31.0.json, its index entry and one picture under media/

    ; whats-new-stub.js moved to 2026.11-dashboard-release-v1.31.0 and whats-new-v380.

  • Fix
    More secrets stay masked in a compose file

    Credentials inside a URL (DATABASE_URL, SENTRY_DSN), values in labels, command and x- lists, a secret passed through a YAML anchor and alias, the lines of a block value in a half-edited file, and every .env line that is not plain NAME=value are masked now; keys named auth, dsn, pwd, salt, jwt, cookie, session or webhook count too. When in doubt the value is masked.

  • Fix
    Up uses the variables the stack was started with

    The helper passes the stack's environment_file as --env-file and the profiles of its running services. Up, Apply and Pull and Up now stop with compose-unset-vars and the names when a variable is set nowhere (?allow-unset=1 goes on anyway); Check lists them as unsetVars.

  • Fix
    A slow Pull and Up no longer kills a running compose up

    Pull and Up each get their own limit (30 minutes for a pull, 10 for starting). A start that runs over is left to finish and answered compose-timeout with what to do; the next run is refused (compose-running) until it is done. A pull that runs over is stopped, and nothing was changed.

  • Fix
    A stack whose containers disagree on their files keeps the override order

    The run follows the newest container's compose files in their own order instead of a sorted list, where an override file could land before its base; the file list still shows every file.

  • Fix
    Check and Apply work on an edited.env

    Check feeds the edited text to compose as the stack's env file; the text of a service's own env_file entry is checked as saved and the answer says stagedIgnored.

  • Fix
    The helper's log follower ends before the run does

    No line is written after the run returned, and the output buffer is guarded against the race.

  • Fix
    nextDash's helpers are hidden at the source

    listContainers never returns a helper, so the update checker, MCP tools, discovery, the status page, auto-update and the disk views skip them too; finished compose helpers of any stack are removed once at start-up.

  • Fix
    Saving a compose file explains a mount it cannot replace, and copes with vfat and non-root

    A file mounted on its own answers compose-file-mount ("mount the folder instead"); a file system that keeps no mode or owner (Unraid /boot, some shares) saves with a note; running as non-root, a file owned by somebody else is written in place so its owner stays.

  • Fix
    Private images: the helper can use the host's registry logins

    NEXTDASH_COMPOSE_DOCKER_CONFIG names a folder with config.json, mounted read-only into the helper; a pull that fails on authorisation answers with that hint.

  • Fix
    compose-applied.json is in the data-file register

    It is never exported.

  • Fix
    A bare-metal or rootless daemon gets its own socket path

    Outside a container the helper binds NEXTDASH_DOCKER_SOCKET instead of /var/run/docker.sock.

  • Fix
    Every masked value gets its own Reveal

    Each masked value in a compose or env file now carries its name and an index, and the reveal route takes index (or line with key), so two secrets on one line, or the same variable twice in an .env, no longer share one button. The old key-only form still works; save and restore answer with the new sha256 only.

Only docs and tests changed in this release.

v1.30.0 Several Docker hosts in the Containers view, a widget you can put on every page, links dragged in from another window, a Watch feeds switch on the phone and three more Christmas themes. +8 Read the post

Several Docker hosts in the Containers view, a widget you can put on every page, links dragged in from another window, a Watch feeds switch on the phone and three more Christmas themes.

Containers

  • New
    Several Docker hosts in the Containers view

    Under Config → Containers → Connection → Other Docker hosts you can add up to four more hosts, each reached through a Docker socket proxy (tcp) or the daemon's own TLS with a CA and an optional client certificate. With a host added, a strip of tabs above Containers | Disk picks the host; the list, side panel, logs and live logs follow it. Test says why a host does not answer (refused, no answer, certificate not trusted, client certificate turned down). A host is read-only until its Allow actions switch is on, and then start, stop, restart, pause, unpause and remove work there; NEXTDASH_DOCKER_CONTROL and the own-container guard apply to this host only. Check for updates works on every host's tab, with an arrow on a container that is behind and the same schedule as the local check; each host keeps its own results in docker-updates-<id>.json, which a backup leaves out. Update, rollback, Disk, the timeline, notices, statistics, widgets, and the settings kept by container name (hidden, muted, automatic updates, web address, icon) stay with this host. Hosts live in docker-hosts.json, their certificates in docker-secrets.json; the Containers tour has a new step on other hosts (seven steps now); installs with one host change nothing.

Bookmarks

  • New
    Drag a link in from another window

    A link, tab or address dropped on a category opens the bookmark form with the address, title, page and category filled in. Dropped elsewhere on the dashboard it follows paste (the choice dialog, the form or the Inbox, as set), and several links at once go to the Inbox. Your own drags, files and fields are left alone, and turning off Paste a URL turns the drop off too.

Widgets

  • New
    A widget on every page

    The edit panel of a widget has a Show on pages switch: This page or Every page. On Every page the widget gets a copy on each other page, as an ordinary widget you move, resize, hide or limit to a screen per page; its name and settings are shared, so a change on one page carries to the others. Deleting a copy takes it off that page only. Switching back to This page removes the copies from the other pages, and a page created later starts with them. A stack stays on its page.

  • New
    Five Immich widgets

    Photos, Slideshow, Albums, People and Status read one Immich library. The API key goes in the X-Api-Key header and is set once in Config → Widgets; Connect lists your albums and people to pick from, and the same key works for all five. Photos and the slideshow can show the whole library, favorites, one album, one person, memories or On this day, in random, newest or oldest order, with or without videos, cover or contain, and a date caption; a tile can be drawn as a frame, grid, strip, hero or list. Status shows the library totals, the disk and the background jobs; a key that does not belong to an administrator gets neither totals nor jobs, and the panel says so. Pictures come through /api/widgets/<type>/image, so the key never reaches the browser.

  • New
    A bell row for failed Immich jobs

    When the Status widget sees failed background jobs, the bell gets a quiet row for them. It reads what the widget already fetched, so it makes no request of its own, and it stays until the jobs are cleared in Immich.

  • New
    A one-photo frame and a slideshow in the media tile

    A photo can fill the tile as one big picture with its date. The slideshow changes photo every 3 to 300 seconds (8 by default), loads the next one ahead, waits while the tab is hidden or the pointer or keyboard is on it, has Play and Pause, and starts paused with no fade for someone who asked their system for less motion.

Phone

  • New
    A Watch feeds switch in More

    On a phone, More → Quick settings has a Watch feeds switch. Off hides everything the watched feeds show on that phone: the feed icon and badge on rows, the hover card, the Watched feeds card on Status, the bell row and the tab count, and the phone stops fetching the watch list. The feeds stay watched and the server keeps polling them, so the desktop and push notices are unchanged. The choice is kept in this browser, not on the server.

Appearance

  • New
    Three more Christmas themes in Holidays, each with a dark and a light half

    Snow Globe (frost) puts the page inside a glass globe on a wooden base with a brass plate and a turning wind-up key, over a small town with a church, smoking chimneys, a string of lights and two skaters on a frozen pond. The snow lands: it piles up on the top edge of each category, and switching page shakes the globe so the caps come off and the snow swirls before it settles again. Paper Advent (paper) is a cut-paper village in four layers, lit from behind, that shifts in depth as the pointer moves, under a punched-out sky with a cut moon, a passing sleigh and a turning Moravian star; from 1 to 24 December one more window is lit each day and today's glows with its number, and paper snowflakes fall. Nutcracker Theatre (velvet) opens a red curtain once when the page loads, onto a stage under a gilt arch with swags, tassels and a crest, between tied-back drapes, with two nutcrackers who salute in turn, the Sugar Plum Fairy turning on a pedestal, footlights, sweeping beams, a spotlight that follows the pointer and falling sugar-plum glitter. Motion stops under reduced motion and with Effects off, leaving a still picture.

Docs

  • Docs
    README.md, MANUAL.md and Config → Help

    The manual gains the five Immich widgets (kinds, settings, key, a screenshot with public-domain photos), the six holiday themes and the new theme counts (223 families, 446 themes); the README counts 63 kinds and mentions Immich, other Docker hosts, a widget on every page and dragging a link in. Help gets paragraphs for a widget on every page, Immich, other Docker hosts, the Watch feeds switch on a phone, the Immich bell row and dragging a link in, and three new tips (tipAddDrag, tipWidgetEverywhere, tipHostOtherHosts).

  • Docs
    translations

    175 strings that existed only as English fallbacks in the code (Docker hosts, Immich, the slideshow, Show on pages, the link drop, the Watch feeds switch) are in all six locale files, and seven that validate:locale-referenced found missing; five tips nothing referenced any more are gone.

  • Docs
    static/data/whats-new/v1.30.0.json, its index entry and three pictures under media/

    ; whats-new-stub.js moved to 2026.11-dashboard-release-v1.30.0 and whats-new-v379, tests/whats-new-hidden-release.spec.js follows. Four cards in overview-features.json with since: "v1.30.0". go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.29.2 Response-time trends for network checks, cleaner page titles, a plain-language digest and a steadier Inbox and test suite — held back from the What's new window (hideFromModal) like v1.29.1, so v1.29.0 keeps leading it. +4 3 fix Read the post

Response-time trends for network checks, cleaner page titles, a plain-language digest and a steadier Inbox and test suite — held back from the What's new window (hideFromModal) like v1.29.1, so v1.29.0 keeps leading it.

Monitoring

  • New
    Response-time trends for network checks

    A check that measures milliseconds (TCP, ping, DNS, HTTP, JSON) now shows its last day as a sparkline in the Tests tab, in the Network tests widget and on the bookmark's preview card. Opening a check in the Tests tab draws its response time over 24 hours, 7 days or 30 days, with the slow limit as a dashed line and failed checks marked on the floor. Nothing new is stored: the chart reads the history the checks already keep, and from three days back one point per day. The pinned preview card has a Network checks button that opens the Tests tab.

  • Fix
    The Tests tab opens the first trend chart

    A check with a trend now shows its first chart straight away instead of a closed list.

Digest

  • New
    The digest opens with the week in plain sentences

    The digest window shows a short summary first, built from the same figures as the cards below it, and the notification body starts with it.

Bookmarks

  • New
    Page titles lose login words and the site's own name

    When the form suggests a name for a new bookmark, a leading Login - or Sign in | and the site's name at the end (- YouTube) are taken off. A small turned arrow at the end of the name field brings the page's own title back, and another press the cleaned one; it shows only for a name the app chose and you have not touched.

Watch feeds

  • Fix
    The news badge stays clickable until the news is read

    Once the news window has closed the row is quiet again, but its count badge, and the way to the headlines behind it, stay until you open the bookmark.

  • New
    The news window is one hour by default

    It was 30 minutes; a window you set yourself is not changed.

Inbox

  • Fix
    Inbox rows that load late still rise in

    When the list had not arrived at the click, the entrance animation closed after the header and the rows then appeared without it. The view now stays open while its "Loading…" line is on screen, up to the existing five-second limit.

Tests

  • Fix
    Timing flakes from CI run 836

    new-themes-notice sets the first-run state before the page loads, view-entrance keeps the value its poll saw and has a new spec for a delayed Inbox, theme-glow marks the Random theme promo as seen, mode-strip-toggle listens for the animation events, and the action bar stays on screen in the quick-add spec.

Docs

  • Docs
    Manual, Help and translations

    Manual §5 and §11.14 and the weekly digest say what the title arrow, the response-time chart and the digest sentences do, with new shots (05-title-restore.jpg, 11-tests-trend.jpg) and retakes of the Tests tab and the digest; a Help line, a tip and an Overview entry cover the trend, in six languages.

  • Docs
    static/data/whats-new/v1.29.2.json and its index entry

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v378. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.29.1 Search, the Inbox and the RSS widget on a touch screen — held back from the What's new window (hideFromModal) like v1.28.3, so v1.29.0 keeps leading it. +1 3 fix Read the post

Search, the Inbox and the RSS widget on a touch screen — held back from the What's new window (hideFromModal) like v1.28.3, so v1.29.0 keeps leading it.

Mobile

  • Fix
    Search on the phone opens at once and keeps the tab bar

    The search code now loads with the bar instead of on the first tap of Search, and the search layer sits above the page and under the bar, so Home, Search, Inbox, Status and More stay in sight (Search is the highlighted tab; another tab leaves search). When the keyboard opens, the bar and the layer lift above it instead of staying behind it.

  • Fix
    The Inbox selects are 44px on an iPhone

    WebKit ignores min-height on a native select, so the site and sort selects stayed at 23px there; they now have a height of their own.

  • New
    The phone specs run on an Android and an iPhone engine

    npm run test:mobile runs the phone specs in Chromium with a Pixel 7 and in WebKit with an iPhone 15; without it nothing changes.

RSS

  • Fix
    RSS headlines have a preview on a touch screen

    The preview of an RSS widget row (the feed's summary, source and age) only showed on hover, so a phone never got it: a tap opened the article, and a press and hold selected a word and opened the row menu. On touch a tap or a press and hold now opens a sheet at the bottom with the preview and three buttons: Open article, Open in a new tab and Close. A tap away or Escape also closes it, the headlines no longer select text, and the desktop hover is as it was.

Docs

  • Docs
    Manual and tip

    Manual §23 says the search sheet keeps the tab bar and lifts above the keyboard, and the RSS line says what a touch screen does with a headline; the RSS tip in Config → Help → Tips names the tap and the press and hold, in six languages. The phone search picture in the manual is taken again with the tab bar under it.

  • Docs
    static/data/whats-new/v1.29.1.json and its index entry

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v377. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.29.0 The phone gets its own way around nextDash. +13 3 fix Read the post

The phone gets its own way around nextDash.

Mobile

  • New
    A tab bar on the phone

    In the phone layout the footer with search and add is replaced by a bar with Home, Search, Inbox, Status and More. Inbox and Status carry a counter (unread items; services down or failing their check). A round + button on the grid keeps the old add-bookmark route. Tablets and desktops are unchanged.

  • New
    Status and More screens

    Status lists every monitored bookmark with a colour (green, amber for a certificate within 14 days, red when down) and pauses notifications for 1 hour or until 07:00 tomorrow: the server holds alerts like quiet hours and sums them up afterwards, except what Always let through allows, and skips feed news pushes (POST /api/notify/pause, one-off notifyPausedUntil). Config → Notifications shows a running pause with a Resume now button. More has dark mode, compact rows (off goes back to the row height you had), the pause, the start screen choice and a "send me the link" card for what is desktop-only.

  • New
    Two start screens, per device

    Home opens with search first (a big search field and one status line) or status first (an "is everything fine?" card, search below). Choose in More; the setting is mobileHome, default search, and follows device-specific settings.

  • New
    A compact search sheet on the phone

    The Search tab opens a full-screen sheet with a real field (it takes the keyboard and its Search key), the modes as a row of chips and bigger result rows, plus a close button, since a phone has no Escape. Typing letters that match a bookmark shortcut no longer opens that bookmark on the way to a longer word; open it with a tap or the Search key. Typing in it searches bookmark names (the desktop default only matches shortcuts and answers "press / to search names", a key a phone does not have; a shortcut needs the / in front there). The assistant is not offered on a phone, and the pinned page filter is gone there (Shift+F stays on desktop).

  • New
    The quick start waits for a desktop

    On a phone the quick start no longer opens; Home says to go through it once on a computer first.

  • Fix
    The bookmark edit form is made for a thumb on the phone

    Fields are 48px high with 16px text (anything smaller makes iOS zoom the page when a field takes focus), the close, Delete, Cancel and Save buttons are 48px, the small info and link buttons have a bigger press area, and the form is a full screen of its own: the header stays on top and Delete, Cancel and Save sit in a bar fixed to the bottom while the fields between them scroll.

  • Fix
    The new-bookmark form on the phone

    The bar has Cancel and Create only: no Create + New, no key hint, and no "New page…" or "New category…" entries in the selects (pages and categories are made on a desktop). The form no longer pans or rubber-bands under a finger; only the fields scroll, up and down, between the fixed header and the fixed bottom bar.

  • New
    A new feed shows its latest posts at once

    Adding a feed with Watch this feed… now fetches the ten newest posts as unread news and opens the popover on the bookmark's row with them, on desktop and on the phone (when the bookmark is not on the page in view, nothing opens). The popover springs in, the bookmark's row wears a ring in the accent colour while it is open (pulsing twice when the feed was just added), a pointer in the same colour runs from the popover to the row and nods three times, and the head carries the feed mark and the site's name with a line saying why it opened. Closing plays the same motion backwards: the popover folds back into the bookmark and the pointer fades. Any popover now has the ring and the pointer, not only the first. The save request takes seed; a script or the MCP tools that leave it out get the plain baseline as before, and a feed edited or retried stays silent about what is old.

  • New
    Show on, in two more places

    The category, widget and collection menus (the ⋯ on a header, also on the phone) have a Show on entry, and Config → Structure has a Show on column in the Categories list and in the Collection sizes list, so you can see and change what shows where without edit mode.

  • Fix
    The Inbox on the phone is made for a thumb

    The header buttons, the filters, the site and sort selects and the search field are 44px (the fields with 16px text, so iOS does not zoom on focus), the tick box has a 44px target, titles read at body size, and the small things in a row (the site, tags, the tag suggestion buttons) have a press area around them. Phone layout only: the desktop Inbox is as it was.

  • New
    A press and hold opens a short bookmark menu on the phone

    On the grid, in the Inbox and on the Status screen. It holds what a thumb does: open in a new tab, copy, share, edit, pin, tags, move, watch the feed and delete (on Status only the first four and watch, there being no grid row to edit). No QR code, no checking or network entries, no selecting and no key chips. Before, a long press opened the inline editor, and iOS never sent the contextmenu event, so the menu could not be reached at all.

  • New
    The news of watched feeds on the phone

    The News button is a desktop control, so the Status screen now has a card with the number unread and a button that opens the news.

  • New
    A phone guide in More

    It is also what the cheat sheet opens on a phone (the :cheat command, Config → Help). One screen lists what works on the phone and what needs a desktop.

  • New
    A hint about swiping pages

    With more than one page, a popover under the page name says once that a swipe changes page.

  • New
    Show a block on desktop only or on the phone only

    Categories, widgets and collections get a Show on choice in the edit panel: everywhere, desktop only or phone only. A tablet counts as a desktop. In edit mode a block hidden on this screen stays on the grid, dimmed and labelled, so nothing gets lost (visibleOn, collectionVisibleOn for built-in and per-tag collections).

List views

  • New
    Drag column borders to resize list view columns

    The headings of Bookmarks, Tags, Inbox and Containers have a handle on the left edge of each resizable column. Drag it left to widen the column; the name column gives way, so a row never outgrows its box. Tag chips refit as the width changes (more chips when wider, folded into +n when narrower). Double-click a handle, or press Delete on it, to put the column back; the arrow keys move a focused handle. Widths are kept per view on the device, not on the server, and a click on a handle never sorts.

Docs

  • Docs
    Translations

    The phone's strings were only English fallbacks in the code (t('mobile.tabs.home', 'Home')), in no locale file. 96 keys are now in all six languages: a new mobile group (tab bar, Status, More, start screens, the phone guide, the search placeholder), config.* (Show on column, start screen choice and its info text, the pause line and Resume now, resize column), editMode.* (Show on) and dashboard.feedWatchOffer.

  • Fix
    Search on the phone keeps the mode you switched to

    Searching bookmark names is the phone's start mode, but every key typed put it back, so a mode chosen while typing was undone at once. It is set only when the panel opens.

  • Fix
    Show on stays out of the Pages and categories window

    The column belongs to Config → Structure; in the narrower window an extra cell pushed the ⋯ out of its column.

  • Docs
    Help and tips

    Paragraphs in helpBehaviorBody (the phone), helpMonitoringConfigBody (pausing), helpEditModeBody (Show on), helpFreshBody (a new feed shows its posts) and helpBmViewSettingsBody (column widths), in six languages, and five tips in TIP_GROUPS: tipPhoneTabs, tipPhoneLongPress, tipWatchFirstPosts, tipEditShowOn, tipListResizeColumns.

  • Docs
    Manual and README

    §23 is rewritten around the tab bar (start screens, search sheet, Status and pause, More, Inbox, short menu, forms, Show on) with eight phone pictures, and 22-phone.jpg and 22-phone-bookmarks.jpg are retaken; short additions in §4, §5, §11, §12.5 and §14.2 and a bullet in the README. The pictures come from tests/manual-screenshots-v1-29.spec.js, which scripts/run-manual-shots.sh now runs; the shot kit marks the swipe hint as seen.

  • Docs
    What's new and News & features

    The window leads with three highlights (the tab bar and Status, Show on, the resizable columns) and carries the start screens, the short menu, the search sheet, the new-feed popover and the pause under them. Config → Overview and About → News & features get three entries dated v1.29.0 (the phone layout, resizable columns, a new feed's posts), in six languages. The release token and data token moved, and tests/whats-new-hidden-release.spec.js names v1.29.0 as the release that leads.

Only docs and tests changed in this release.

v1.28.3 The new theme groups on every view. 1 fix

The new theme groups on every view.

Theme groups

  • Fix
    The new themes also dress the other views

    Instrument, Spatial, Riso, Legible, Living, Cartographic and Stationery drew their frame on the dashboard only, so Bookmarks, Inbox, Containers, Glances, Tags and Config kept the plain panel and looked like another theme. The panel of those views now takes the frame its group gives a category: the oscilloscope bezel, the slide mount, the riso ink border and shadow, the chart neatline and the rest. The pins, torn edges and rulers stay on the dashboard, where the rows they decorate are. Every pane is also filled like a column of the dashboard in the same theme, with the same opacity. Of the 440 themes 339 already matched; the other 101 (Skywatch, Nautical, Subway, Diorama, Gallery, Ledger, Zen and 44 older families with a material, such as gloss, matrix, neon and retro-crt) showed a thinner pane on Config, Inbox and the other views, and now match. The fill follows the Surface setting, the material and the weather of Skywatch.

Only docs and tests changed in this release.

v1.28.2 Eight new theme groups, 25 families in light and dark, each built around an idea that goes beyond colour: one bookmark per line with room between them, a page that follows the health of your services, a row drawn as a label strip, a page drawn as a map. +18 4 fix Read the post

Eight new theme groups, 25 families in light and dark, each built around an idea that goes beyond colour: one bookmark per line with room between them, a page that follows the health of your services, a row drawn as a label strip, a page drawn as a map. In the theme studio each group has its own chip in the Character row and on the card badge, and each family has a backdrop of its own.

Theme groups

  • New
    Stationery

    One bookmark per line, with room between the lines as the only separator. Ledger (cream, serif, a dotted leader from the name to the shortcut letters, numbered lines), Swiss Poster (grotesque type with one cobalt accent, a huge numeral and a heavy rule above every category and widget, the numerals running on from one category to the next, a keyboard row inverted to a solid block), Typewriter (an index card with a punched edge, a red ribbon heading and typed leaders, the same card for widgets) and Zen (a hanging scroll between two rollers, the title as a red stamp, widgets on the same paper). The Rows settings still apply.

  • New
    Living

    The theme answers to your data. Tidewatch draws a waterline whose level follows the health of your services: low teal water when everything is up, amber for a dead link, a high coral surge when something is down. Daydrift moves its palette through the day by the local clock, with a sun or moon crossing an arc. Skywatch shows the weather from the weather widget's own cache (the clock when there is none) as a glyph, with rain, fog, snow, sun and stars drawn in CSS and the categories as window panes. It makes no request of its own, stops when you leave the theme, and stands still under reduced motion and with Effects off.

  • New
    Instrument

    The history is in the row. Cockpit (a wireframe HUD with corner brackets and no fill), Oscilloscope (a CRT screen per category with bezel, screws, graticule and phosphor glow) and Dive Computer (a metal pill with a depth ruler and a ring gauge for up and total). A row that has a heartbeat history or a measured ping gets a trace and a bar; a row without either gets nothing, never invented data. A category head shows up/total and a segmented meter.

  • New
    Tactile

    The row is a physical thing. Label Maker (laminated tape strips in white, yellow, blue, red and green with black print and cut ends, a cassette head with a spool), Keycap (keys that sink when pressed) and Rack Unit (plates with two screws each and a status lamp). Widget lines and the Notes text take the same objects as the category rows, and a widget has the same pane as a category. With reduced motion or Effects off a press changes colour and nothing moves. Status keeps a shape of its own, not only a colour.

  • New
    Spatial

    Depth, drawn so that it shows without moving the mouse. Diorama (cut-paper sheets with torn and stepped edges, a pin and a hard shadow), Lightbox (black slide mounts with sprocket holes and backlit film, a lamp under the cursor) and Orbit (square star-field panels with planets on ring lines). The pointer only writes two CSS variables, once per frame; nothing that holds content is ever transformed, so drag and drop, menus and popovers keep working. It stays still on touch screens, with reduced motion and with Effects off.

  • New
    Cartographic

    The page is a map. Atlas (pins with a dashed leader to a grid coordinate such as B3, a frame with latitude and longitude ticks, contour lines), Nautical (a sea chart with double-line cut-outs, soundings, a degrees and minutes ruler and a compass rose) and Subway Map (a line colour per category, a station dot per bookmark, an interchange on the last row, delayed and out of service tags from the status the row already has). The coordinates are decoration; shortcuts and search are unchanged.

  • New
    Riso

    A two-ink print. Riso Pink-Blue (blue ink with a hard pink block shadow, solid heads, halftone corners), Riso Green-Orange (a stamp look with a double outline and heads tilted a degree) and Mimeograph (one faded purple ink, speckled and bleeding). Light halves overprint with multiply; menus and the side panel stay plain.

  • New
    Legible

    Accessibility as a style. High Contrast Calm is airport signage: square panels with a banded title, ruled strips with a pictogram, black bands on light grey by day and yellow on black by night. Low Vision Amber is amber on black and dark amber on warm white. Colour-blind Safe uses a blue and orange pair and different shapes for different states. Rows are at least 44 px, the keyboard row has a 4 px ring, status is a shape and a word, nothing animates, and text keeps at least 7:1 against its background, measured on the real page over the backdrop.

  • New
    The 25 new families wear the

    new badge. The list in theme_new.go is replaced, as the file says the next collection does, so the earlier 62 families stop being new and the New segment and searching new show only this release's families.

Backdrops

  • New
    Eighteen backdrops, drawn for one family each

    gallerywall and typesheet and zenwash (Stationery: a gallery with arched doorways, now a Swiss modular grid; a pile of typing paper; a raked gravel garden), sundial and cloudstrata (Living: hour lines and sun paths, stacked cloud banks), hudhorizon and decocurve (Instrument: an artificial horizon with a pitch ladder, a dive profile with bubbles), labeltape, keycapfield and rackcables (Tactile), papercuts and filmstrip (Spatial), metrolines (Cartographic: a transit network), stampfield and inkspeckle (Riso) and softsquares, amberhorizon and shapetiles (Legible: quiet enough to keep the contrast). That makes 285 backdrops. The other seven families keep an existing one (swells, cellgrid, stars, topo, oceanblue, halftone, ruled).

Layout

  • Fix
    Five and six columns now work on a wide window

    The page was a container with a ceiling of 1600px, and the side margin comes out of it, so five columns barely fit and six never did, on any screen: the setting offered 6 and drew 4, or 5 on a window of about 1900px. The ceiling now follows the setting: it stays 1600px for up to four columns and grows to what the asked-for columns need at their minimum width, set on the root so the header and every view line up with the grid. A narrower window still keeps only the columns that fit.

  • New
    Page margins in seven steps, Balanced in the middle

    The band beside the columns had three steps, and even Snug left up to 48px on each side and kept the page at 1600px, so a big monitor never filled. It now has seven, three narrower than Balanced and three wider: Full width (almost no edge and no ceiling on the page, a column may grow to 720px), Tight (540px, a high ceiling of 2200px on the page), Snug, Balanced (still the default, as it was), Roomy, Airy and Spacious (the widest, columns down to 270px). At a 1700px window the band is about 3, 20, 40, 100, 130, 150 and 270px, and the columns that fit follow it. The choices are in Appearance → Layout and in the theme studio's Layout tab, :margins takes them, and the six languages have their words. An unknown value still falls back to Balanced.

  • New
    Columns per row is a dropdown from 1 to 8

    It was a number box that took 1 to 12 and drew 6 at most. Eight is the most now, in Appearance → Layout and in the theme studio's Layout tab, the drawing beside it shows all eight, the palette's :columns offers 7 and 8, and the cheat sheet and the info text say 1–8 in six languages. A stored 9 to 12 reads as 8.

  • New
    Space between categories, Space between columns and Page margins are dropdowns

    They were rows of cards; each option is now a line in a dropdown with its sentence in it (Snug — Rows sit close together.), and the drawing of the choice in force stays beside the field. The same in Appearance → Layout and the theme studio.

Introducing the themes

  • New
    A popover shows the eight new theme groups to installs that were already in use

    Once, in the middle of the dashboard, after the What's new window and the setup cards: one tab per group, a screenshot and a line for every theme (Skywatch, Tidewatch and Daydrift say what they follow: the weather, the health of your services, the time of day), a Dark and Light switch, and a button on every card that puts that theme on the page. A click on a screenshot opens it large with the same button, and Open the theme studio opens the studio on the New themes (the theme browser can now be opened on a segment). It counts as answered the moment it is shown, a fresh install does not see it, and corner cards wait while it is still to come. The 100 screenshots are in static/img/new-themes/.

  • New
    A tip in the bell opens the new themes popover again

    Show the new themes waits in the Tips group of every upgraded install until it is read, for whoever closed the popover too soon.

  • New
    Three tips in the bell about the themes that react to something, one a day

    Skywatch (the weather) on the first day, Tidewatch (the health of your bookmarks) on the second, Daydrift (the time of day) on the third, in the Tips group until they are read. Each says what the theme follows and has Use this theme (in the half you wear now) and Open in the theme studio (searching that family). The days count from the first time an upgraded install runs this release (discoverabilityState.themeTipsFrom), a fresh install is not told, and a theme you already wear has no tip.

Bookmarks view

  • New
    The Latest news column is gone from the Bookmarks view

    The newest headline of a watched site stays where it is read best: on the row in the dashboard, in the preview card and in the news window (Shift + W). The column, its heading, its place in Sort and Columns shown and its two locale words are removed; a saved choice that names it is ignored.

Under the hood

  • New
    One file per theme group

    theme_groups.go merges the palettes of every group into the built-in themes and never replaces an id that is already there; a group's id prefix files it under its chip. Each group brings its own stylesheet, its own script when it needs one, and its own spec.

  • Fix
    Daydrift keeps the phone's browser bar with the page

    The bar colour (theme-color) was only set when the theme changed, so it stayed on the colour of that moment while the page moved through the day; every tick now sets it as well.

  • Fix
    Tidewatch counts each outage once

    The count took the down badge and the offline rows together, so one outage counted at least twice; it is now the offline rows, with the badge only deciding the state.

  • Fix
    Asking for the column count no longer forces a layout pass

    The lookup the keyboard and the block mover call all the time wrote the page ceiling every time, even unchanged, which made the next measure lay the page out again; it now writes only when the value changes.

Docs

  • Docs
    Translations, Help and tips

    41 keys in all six languages: the eight group labels, the 25 family descriptions (the theme browser now reads config.themeDesc.<family> and falls back to the English line), five words the new themes draw in CSS, and a tip about the theme groups (tipTuneThemeGroups). Help says 220 families, 440 themes and 285 backdrops and names the groups; the backdrop and theme browser tips carry the new numbers.

  • Docs
    Manual and README

    440 themes, 220 families and 285 backdrops everywhere; a Theme groups bullet in §17.1 with the eight groups, a paragraph in §17.2 that groups are not materials, the 18 new backdrops in §17A.4, and the new badge line. The README names Tarnished Brass as the starting theme, as the manual does, and its two theme montages are retaken with all 220 families. The Layout picture in the manual, the cheat sheet's :columns row (1–8) and two entries in Config → Overview (the theme groups, page margins and columns) are brought up to date.

  • Docs
    What's new, News & features and the cheat sheet

    The What's new window leads with two highlights, the eight theme groups (a collage of one dashboard from each group) and the page margins (a recording that steps from Full width to Spacious on six columns), with the New badge, the 18 backdrops, the dropdowns and the column fix under them. Config → Overview and About → News & features get two entries dated v1.28.2, one for the theme groups and one for the page margins and eight columns, in six languages. The cheat sheet's :columns row says 1–8. The release token and the data token of the window moved, and tests/whats-new-hidden-release.spec.js names v1.28.2 as the release that leads.

  • Docs
    nextdash.cc

    The front page, the features index, the compare page and the gallery slider say 440 themes, 220 families, 285 backdrops and 58 widget kinds; the gallery has the 50 new themes with new pictures and eight new group chips; feature-pages/v1.28.2-pages.php updates the themes page text. A new feature page, Page margins and columns, has three pictures and a loop of the margins stepping from Full width to Spacious, and the release list knows v1.28.1 and v1.28.2.

  • Docs
    Help, manual and site, second pass

    Help's Choosing a theme said a fresh install starts on Aurora Glass and that the 62 newest families wear the new badge; it now says Tarnished Brass and 25, mentions the popover and the bell tips, and the Layout list in Help → Appearance gives columns per row as 1–8 and the seven page margins, in six languages. The manual's theme groups list has a bullet on the popover and the three tips. The site counts 58 widget kinds, as Help and the README do; the count includes the custom widget. On the compare page the Glances and assistant blocks show the Glances page and the assistant at work instead of a dashboard frame, and its widget count (it said 51) is brought up to date.

Only docs and tests changed in this release.

v1.28.1 Three more services on the media tile: Jellystat, Bazarr and Prowlarr. +3 1 fix Read the post

Three more services on the media tile: Jellystat, Bazarr and Prowlarr. Each one is a widget with its own address and API key, a Connect step that checks them, and parts you switch on or off. Under Media in the widget catalogue.

Media widgets

  • New
    A Jellystat widget

    Recent plays, the most viewed, the most active people and a line of totals, each optional. The narrow tile shows one part at a time behind tabs, the wide tile puts them side by side. The key is made under Settings → API Keys in Jellystat. After Connect the libraries are offered; only the totals and the recent plays follow that choice, because Jellystat cannot split its top lists. Period 1 to 365 days (30 by default), refresh every 60 to 3600 seconds (300 by default), and a click opens the item in Jellystat or a small card first.

  • New
    A Bazarr widget

    Three parts, each optional: Missing subtitles (movies and episodes with the languages still missing, such as nl, en+hi or en+forced, the two kinds taking turns so a long movie backlog does not hide the episodes), Recently fetched (language, provider, score and upgraded, newest first, in Bazarr's own time zone) and a line of totals (movies missing, episodes missing, providers in trouble). The key is under Settings → General → Security in Bazarr, and Connect names the version it found. A figure Bazarr could not be asked for shows as a dash, not a zero, and the tile says that part of it could not be read.

  • New
    A Prowlarr widget

    Three parts, each optional: the indexers that are on (queries, grabs, failures and the average answer time, a paused one first), what needs attention (Prowlarr's own health messages and the indexers it has paused, with when they are tried again) and a line of totals. Period 1 to 365 days (7 by default). The key is under Settings → General → Security in Prowlarr. A count Prowlarr could not give shows as a dash, not a zero. The widget never reads Prowlarr's history, which carries the address of every search with the key in it.

Security

  • Fix
    Go 1.26.11

    govulncheck reported GO-2026-6859 in net/http of Go 1.26.10, which nextDash's server code reaches. The toolchain line in go.mod now names 1.26.11, where it is fixed. scripts/release-preflight.sh passes with it.

Docs

  • Docs
    static/data/whats-new/v1.28.1.json and its index entry

    , led by one highlight for the three widgets with a picture. whats-new-stub.js names the release (DASHBOARD_RELEASE) and NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v373; tests/whats-new-hidden-release.spec.js follows. go generate refreshed asset_hashes_gen.go.

  • Docs
    Config → Overview and About → News & features

    carry one entry each for Jellystat, Bazarr and Prowlarr (since: "v1.28.1"), Config → Help and its tip name the three, and MANUAL.md and README.md describe them, with four new pictures. The 79 strings of the three widgets and the Overview entries are in all six languages.

  • New
    Four flaky specs wait for state, not for time

    , and a spec records the pictures for the network tests page on the site.

Only docs and tests changed in this release.

v1.28.0 Network checks on a bookmark. +16 5 fix Read the post

Network checks on a bookmark. A new Tests tab in the Bookmarks view's side panel watches the bookmark's own host with six kinds of check (TCP, Ping, DNS, TLS, HTTP detail and JSON), each with its own schedule, history and alerts, or runs one test right now and saves nothing. The checks show as chips on the dashboard rows, in the bell, in a new Network tests widget, on the status page and through five MCP tools. Three smaller changes ride along: the weather beside the clock rule is larger, the bell is off on a phone, and a new container's notice is a row in the bell.

Network checks

  • New
    A Tests tab on every bookmark

    The side panel of the Bookmarks view has a fourth tab, Tests (4; 1/2/3/4 and [/] switch tabs). A bookmark can carry up to six checks. Three tiles (checks, down, up 24 h) give the picture; each check is an accordion row with its state, cadence, last result, uptime strip and sparkline, and for a failure a block that says what to do about it. The tab carries a dot while a scheduled check is down, and the Health tab says n checks · m down with a link to it.

  • New
    Six kinds of check

    TCP (does the port connect, and how fast), Ping (1 to 10 echoes; down from a set loss), DNS (A, AAAA, CNAME, MX, TXT, NS or CAA, with an optional expected value), TLS (chain, version, days left; a Warning at or below a number of days, with expiry notices on a ladder derived from it), HTTP detail (one GET with the timeline of DNS, connect, TLS, first byte and download as a bar, the redirect chain and the headers) and JSON (one value in an answer, read by a path such as services[name=api].up, with is equal to, is not equal to, is more than, is less than, contains or exists). A check reads Up, Down, Warning, Slow, via TCP or Not measured; Not measured is no outage and sends nothing.

  • New
    Add check, in three steps

    1 · Type, 2 · What to check, 3 · Planning and alerts, with a What this does text in plain words and Test first to run the form once before saving. Planning is Like the bookmark, an interval of your own (5 minutes to 24 hours) or Off; time-out 1 to 10 seconds; Slow from in milliseconds. A check has its own alert, uses the bookmark's retries, quiet hours and maintenance windows, and a webhook or push message names the check. Muted keeps the history and sends nothing.

  • New
    Run once

    Sends one test from the server right now: nothing is saved and nothing alerts, but the same safety guard applies. Save as scheduled check… turns what you just tested into a check. More than six tests a minute from one client are refused.

  • New
    DNS says when the records change

    The first run stores the record set as a baseline; a later, different set (order and TTL ignored) shows as DNS changed with the difference (MX +mail2.example.org) and as a quiet row in the bell with Tests and Accept. The check stays up until you accept. It starts on for MX, TXT, NS, CAA and CNAME and off for A and AAAA, which often rotate behind a CDN. The resolver is System, 1.1.1.1 or 8.8.8.8 (no free address, which would turn the server into an open DNS proxy); a fixed resolver shows DNSSEC validated or DNSSEC not validated for information only.

  • New
    Checks on dashboard rows

    A bookmark row shows its checks as chips (type and a status dot) in the tag cluster: problems first, then the tags, the rest as +n with a popover. A click on a chip opens the Tests tab; the row menu has Network checks for the keyboard. Config → Monitoring → Checks → Check status on dashboard rows chooses Only problems (the default), Always or Never. The Bookmarks view gains a Network tests column filter and a Check type filter with counts, between Health and Pages.

  • New
    Checks in the bell and on the status page

    A scheduled check that is down, and one that came back within 24 hours, sit in the bell with Health and Mute. A service on the status page can list the network checks of its bookmark, ticked per service under Config → Status page; the worst one decides, and a certificate close to expiry counts as degraded.

  • New
    A Network tests widget

    Shows checks you already have, from what is measured; the widget runs nothing. Three looks (Rows, Tiles, Heartbeat), order Problems first or Name, 1 to 20 rows, refresh every 30 to 3600 seconds (60 by default), up to 40 checks picked from a table. There is no free host field. A removed check reads check removed.

  • New
    Config → Monitoring → Checks

    A Network checks panel with the master switch, Ping (Auto: ICMP, with TCP as the fallback, TCP only or Off), Let a check name another host than its bookmark (off), Most scheduled checks (200 by default, up to 1000) and the dashboard-row setting. A status block says whether ICMP works, is blocked (with the snippet to copy), has not been tried yet or is off, and a table lists every check in the install; tick rows to turn several on or off at once.

  • New
    Five MCP tools

    run_network_test, list_net_checks, get_net_check, set_net_check and delete_net_check, behind their own switch Network tests under Data & backups → Webhooks → MCP access, off by default. No tool takes a host or a port, so a client cannot turn them into a scanner; running, adding, changing and deleting need NEXTDASH_WRITE_TOKEN when it is set.

  • New
    Help cards in the tab

    A small ℹ beside the headings, the Run once accordion and the form's Type, Planning, Time-out, Slow from and Alerts fields opens a short card; Esc or a click outside closes it.

  • New
    A blocked host says where it points, to you

    With the address guard refusing a host, your own Tests tab adds Resolves to 192.168.1.20; a notice, webhook or MCP answer never carries the address. The check shows Not measured, not Down.

  • New
    Ping in Docker

    Ping needs ICMP. When the container cannot send it, Ping falls back to TCP and shows via TCP; the Tests tab and Config say so and show net.ipv4.ping_group_range: "0 2147483647" to copy. Both compose files and templates/nextdash.xml carry the snippet, commented out.

  • Fix
    Findings from the review of the network tools

    The checks sit behind the same address guard as previews and favicons, with the resolved address pinned, and refuse carrier-grade NAT (so Tailscale addresses), 0.0.0.0/8, 198.18.0.0/15, 240.0.0.0/4 and IPv6 forms that embed a non-public IPv4 address while local addresses are off. A credential stored on the bookmark goes only to that bookmark's scheme and host:port, never after a redirect elsewhere, and never into a result, sample, the activity log or an MCP answer; a value under a path that names a token, key, secret or password shows as [hidden]. A page save, import, template or restore never takes checks from what a browser sends. The demo runs no test; its checks are seeded.

Bell

  • New
    A new container's notice is a row in the bell

    Undo, Move and Done sit on the row, which lists the adds for as long as they are unacknowledged. It no longer puts a card in the corner, so it works during the quick start and on a phone too. The new tiles are brought on screen before the row names them, and a failed Undo shows a toast.

  • Fix
    The analytics question is a corner card again

    It was a quiet row in the bell. It shows a few seconds after the What's new window closes, and not while the quick-start card is on screen. Closing it with × or reading the detail without deciding snoozes it (3, 14, then 45 days), and being shown starts a one-day cooldown, so a reload past an untouched card does not put it back. Nothing shows when analytics is on, the question is answered or DISABLE_TELEMETRY is set.

  • Fix
    No bell on a phone

    Under 768 px the bell is off; tablet and desktop keep it.

  • New
    A tip in the bell about the network tests

    Every install, new or old, gets one row in the Tips group: Test your services from nextDash, saying what the Tests tab checks (a port, a ping, DNS records, a certificate, an HTTP answer, a value in a JSON answer) and that a test can run once or on a schedule. Open Tests opens the Tests tab of a bookmark that has a check, or the Bookmarks view when none has, and reads the row; it stays until read and is left out while the network checks are off.

Appearance

  • Fix
    The side panel of the Bookmarks view follows the theme on every tab

    Its accordions, tabs, tiles, chips and fields were painted in the page's darkest colour, opaque, and read as black holes on a Signature material, most on the new Tests tab but also on Details, Health and Usage. The panel stands in a frame beside the view, outside .lvs, so the rule of v1.27.4 that turns the two dark colours into the material's field fill never reached it; .lvs-drawer is now named there too. Classic is unchanged.

  • New
    The weather is larger beside the clock rule in the classic header

    The greeting stands over a row of icon and large temperature, with the day and place · condition in two small lines beside them, in the side block the three lines already used, so the pages keep their width. In a narrower header the place and condition go first (under 1300 px), then the greeting and the day (under 1050 px); the icon and temperature stay.

Keyboard

  • Fix
    The key legends say show/hide mode strip

    The legend key for the mode strip read mode strip, which did not say that it switches it.

Docs

  • Docs
    The manual has a chapter on the network checks

    MANUAL §11.14 covers the kinds, states, planning, DNS, TLS, HTTP detail, JSON, credentials, Ping in Docker, the Config panel and the safety rules; the Bookmarks view, widget, status page and MCP chapters point to it. The network texts are in Dutch, German, French, Spanish and Chinese too. nextdash.xml carries the new text. Five new pictures show the Tests tab (a check, a certificate close to expiry, Add check and one Run once with HTTP detail) and the Network checks panel under Config → Monitoring → Checks; every other picture of the manual and the README was retaken for the new header and the side panel.

  • Docs
    Config → Help, tips, Overview and the cheat sheet follow

    Help gains a network-checks paragraph in the Health, header, bell, status page, widget and MCP texts (the widget count is fifty-four kinds), three tips (the Tests tab, Run once and via TCP), and Config → Overview and About → News & features an entry Network tests on every bookmark. The cheat sheet row for the side panel's tabs reads 1 / 2 / 3 / 4 and names Tests, and nextDash-cheatsheet.html and .pdf were regenerated. 170 locale keys nothing reached were removed from all six files; the strings that read show/hide mode strip and Run once were translated.

  • Docs
    static/data/whats-new/v1.28.0.json and its index entry

    ; the first entry of index.json is now v1.28.0, with three highlights (the Tests tab, the checks where you work, the larger weather) and their pictures under media/. whats-new-stub.js moved DASHBOARD_RELEASE to v1.28.0, so the window opens once, and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v372. tests/whats-new-hidden-release.spec.js names v1.28.0 as the release that leads. static/data/licenses.json lists the two Go modules the network checks added (github.com/miekg/dns and golang.org/x/sys), and go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.27.4 The rest of Config and the list views follow the theme: chips, option cards, rows, fields and drawings no longer show as dark holes on a Signature material. 3 fix

The rest of Config and the list views follow the theme: chips, option cards, rows, fields and drawings no longer show as dark holes on a Signature material. Five Config sections open with a clearer first paragraph. Held back from the What's new window (hideFromModal) like v1.27.1 to v1.27.3, so v1.27.0 keeps leading it.

Appearance

  • Fix
    Dark fills inside the views and windows follow the material

    Rows, chips, option cards, segmented tabs, fields and the drawings beside a setting were painted in the page's two darkest colours (--background-primary, --background-secondary), opaque, and read as dark holes on a see-through Signature panel: the Unraid widget chips and the How it works boxes, the Turn on checking cards, Pages and categories, Your rules and Local copies under Config → Bookmarks, the Watch feeds fields, the import cards under Data & backups, Add a widget, and the group rows in Containers. Inside a Config view, a list view (.lvs: Containers, Tags, Inbox, Health) and a window (.modal) the two colours now become the material's field fill and a light lift of the text colour. What must stay solid keeps the page colour, kept as --solid-background-primary and --solid-background-secondary: the options of a dropdown, the sticky column heads, the list views' sticky head and the bulk-select bar. The Collection menu in the Bookmarks view and the ⋯ menu of Pages and categories are drawn as solid small layers, like the other menus, so the list no longer shows through them. Classic is unchanged.

  • Fix
    The / in the Bookmarks search box sits inside the field

    The chip was as tall as the field but 8px from its end, and looked stuck on. It now sits 3px from the field's top, bottom and right edge, with corners that follow the field's.

Config

  • Fix
    A clearer first paragraph in five sections

    Monitoring says what the checks are for before the three modes; Unraid says what the widgets show and that nextDash only reads, before asking for the key; Status page says it is a page of its own for the people who use your services; Containers says what the view lists before the connection settings; AI Assistant says what you can ask in plain words. The five texts are in Dutch, German, French, Spanish and Chinese too.

Docs

  • Docs
    Unraid template

    nextdash.xml carries the v1.27.3 date and changes.

Only docs and tests changed in this release.

v1.27.3 The install count counts installs, not test servers: it waits until a server has run for a day and sends at most one request a day. 4 fix

The install count counts installs, not test servers: it waits until a server has run for a day and sends at most one request a day. Dropdowns take the theme's material instead of the page's darkest colour. Held back from the What's new window (hideFromModal) like v1.27.1 and v1.27.2, so v1.27.0 keeps leading it.

Privacy

  • Fix
    The install count waits a day and then sends once a day at most

    A server started on an empty data folder (a test run, a CI job, a smoke test, a go run) counted as a new install the moment it started, and a container that restarted in a loop sent a request on every start. installPingDue in install_ping.go now holds the request back until the install-id file is 23 hours old, and the new install-ping file in the data folder keeps the time of the last request so that no second one goes out within 23 hours. An install that predates the file sends at its next start as before. NEXTDASH_DISABLE_INSTALL_PING=1 still switches the count off for a run that lasts longer.

Config

  • Fix
    The Version panel in Config → Overview links the changelog on nextdash.cc

    The here after "full changelog" opened CHANGELOG.md on GitHub; it now opens https://nextdash.cc/changelog/, next to the manual on nextdash.cc/docs. The Changelog button under About still points at GitHub.

Watch feeds

  • Fix
    Opening a news item from far down the list shows it

    In the news window on a phone the two columns fold into one, with the article on top and the other items below it. Tapping an item (or the arrows under the article) opened the new article above the window's scroll position, out of sight. The window now scrolls back to the top when an article opens, and holds still for someone who asked for reduced motion. Covered by tests/feed-watch-scroll.spec.js.

Appearance

  • Fix
    Dropdowns follow the theme

    A closed dropdown was filled with the page's darkest colour (--background-secondary, opaque) and read as a hole beside the see-through text fields. On a Signature material it now takes the material's field fill and rule, like the text fields, everywhere: Config, the list views, the theme studio, the bookmark form, the modals, the Inbox, Watch feeds, the tag view and the widget sheets. The options of a native dropdown carry the theme's raised surface (--surface-2, opaque) instead, so its list never shows the page through it, in Classic too. The theme picker's open list is drawn as the other small layers are. Classic keeps its closed dropdowns as they were.

Docs

  • Docs
    Manual §23.8

    The install count says it starts on the second day, that a restart sends nothing more within the day, and names the install-ping file.

  • Docs
    static/data/whats-new/v1.27.3.json and its index entry, held back from the modal

    NEXTDASH_WHATS_NEW_DATA_VERSION moves to whats-new-v370, DASHBOARD_RELEASE stays on v1.27.0, and whats-new-hidden-release.spec.js follows.

  • Docs
    Manual pictures retaken

    159 pictures in screenshots/manual.md/ are taken again on a fresh seed, so they show the dropdowns in the theme's fill and the key legend under each Config page. Eight shot specs still pressed the old keys and stopped (Disk on d, the QR code on Shift+Q, edit in place on Shift+E, the news on Shift+N, Work through on f, health in large on Shift+B); they use ], q, e, Shift+W, u and l now.

  • Docs
    Manual §18.8

    The Version panel's links point at the changelog on nextdash.cc/changelog and the manual on nextdash.cc/docs; it still said both were on GitHub.

  • Docs
    Unraid template

    nextdash.xml carries the v1.27.2 date and changes, in this repository and in unraid_templates.

Only docs and tests changed in this release.

v1.27.2 Config looks like the theme everywhere: selects, checkboxes and radios, the preview beside the Appearance tabs and the Watch feeds list. +2 2 fix

Config looks like the theme everywhere: selects, checkboxes and radios, the preview beside the Appearance tabs and the Watch feeds list. A phone no longer gets key legends or key tips.

Config

  • Fix
    Every select, checkbox and radio in Config wears the theme

    They drew the system's stepper arrows and white boxes on every page. Selects now have a chevron in the text colour and the theme's border; checkboxes and radios are a box in the theme's ink that fills with the accent, with a check, a dot or a dash.

  • Fix
    The preview beside the Appearance tabs is no longer black

    It sat on the theme's darkest colour with the parts that are not the subject of the open tab dimmed to a third; it now rests on a lifted surface, the cells show, and the dimmed parts stay readable.

  • New
    Watch feeds is a table like Structure

    A framed list with a column head (Feed, Status, Checked, Check every), flat rows with a rule between them, a tint on the row under the pointer or the cursor, the summary in the same small line, and Watch more… in the accent.

Keyboard

  • New
    No key legends on a phone

    On a touch device without a mouse the line of keys under the grid, the Inbox, Glances and the Config lists stays away, and so do the two key tips in the bell: a finger cannot press them.

Docs

  • Docs
    Cheat sheet header names ?

    The lead line of nextDash-cheatsheet.html and the PDF (root and static/) still said ! or F1 opens the searchable live list; since v1.27.0 ! opens finders and ? opens Keys and help. The line now reads ? or F1 and names Keys and help (scripts/generate-cheatsheet.cjs).

  • Docs
    Manual, Help and the picture

    §4 says a phone shows no key legends and §14 describes the Watch feeds list as a table with a column head; the Watch feeds Help panel says the same in all six languages, and 12-watch-feeds-config.jpg is taken again.

  • Docs
    Translations

    The four column heads of the Watch feeds table in Dutch, German, French, Spanish and Chinese.

  • Docs
    static/data/whats-new/v1.27.2.json and its index entry, held back

    NEXTDASH_WHATS_NEW_DATA_VERSION moves to whats-new-v369, DASHBOARD_RELEASE stays on v1.27.0, and whats-new-hidden-release.spec.js names v1.27.2 among the held-back releases.

Only docs and tests changed in this release.

v1.27.1 New screenshots in the README and on Unraid's Community Applications, taken on v1.27.0, so both show the mode strip, the key legends and Keys and help. docs

New screenshots in the README and on Unraid's Community Applications, taken on v1.27.0, so both show the mode strip, the key legends and Keys and help. No change to the app itself — held back from the What's new window (hideFromModal) like v1.26.1, so v1.27.0 keeps leading it.

Docs

  • Docs
    README pictures retaken

    The 24 pictures in screenshots/ that the README and the Unraid template show are taken again on v1.27.0 over the demo seed, with the same themes and scenes as on 5 November.

  • Docs
    Unraid template

    nextdash.xml carries the v1.27.0 date and its changes, and the release of these pictures; its screenshots point at the new files on main.

  • Docs
    static/data/whats-new/v1.27.1.json and its index entry, held back

    NEXTDASH_WHATS_NEW_DATA_VERSION moves to whats-new-v368, DASHBOARD_RELEASE stays on v1.27.0, and whats-new-hidden-release.spec.js follows.

Only docs and tests changed in this release.

v1.27.0 One set of keyboard rules for every view. +29 8 fix Read the post

One set of keyboard rules for every view. With the cursor on a row, plain letters act on that row. Shift plus a letter opens a view or a panel. A mode strip beside the page name says what the keys do right now, every view has a key legend, and ? opens a Keys and help sheet for the page you are on. The strip wears the theme's material. Many keys moved, so an existing install is told once in a window it closes with a tick, and the bell then says the cheat sheet is now Keys and help. Three holiday themes, tags in the palette, a Ko-fi card on Config → Overview and two fixes to the bell ride along.

Keyboard

  • New
    Plain letters act on the row under the cursor

    On the dashboard, as in the Inbox: e edits, m moves, t tags, p pins, c sets checking, r shows the bookmark in the Bookmarks view, v opens the preview card, s shares, q shows a QR code, d deletes (asks first) and f filters the grid by its tag; x ticks, j/k move. With no cursor on the grid the same letters start a search. Held down, a letter acts once.

  • New
    Shift opens views and panels

    Shift + B the Bookmarks view (was Shift + H), Shift + C Containers (was Shift + Y), Shift + E edit mode (was Shift + M with nothing selected), Shift + N the bell, Shift + W the news of watched feeds (was Shift + N), Shift + P the Pages panel (was ,), Shift + H the key legend (was Shift + Z), Shift + X the search mode (was Shift + Q; with a bookmark selected it ticks the whole category), and , opens Config (was Shift + S). Shift + B no longer opens the bookmark form; + and Ctrl + Shift + A do.

  • New
    Old keys say what replaced them

    For a couple of releases Shift + Y, Shift + M, Shift + J, Shift + L and Shift + Z still work and put one line on screen naming the new key, once per pair per page load. A Shift letter that used to act on a bookmark names the plain letter instead.

  • New
    ! opens finders, ? opens keys and help

    The two keys swapped. Finders take ! shortcut query (! g nextdash); the ! is the mode, never part of the query sent to the site.

  • New
    The mode key is a badge, not text in the field

    The : of commands, the ! of finders, the = of the assistant and the * of recents show as the badge in front of the search field; Backspace on an empty field leaves the mode with the panel still open. Mode keys pressed on the dashboard no longer land in the search field.

  • New
    One shortcut scheme for every view

    The tag view, the Inbox, the Bookmarks view, Containers, Glances and Config use the same row letters and the same Shift keys. Config's stored backups and trash are lists with a row cursor: e names a row, d removes it, u/n move it.

  • New
    Shift + W explains itself with no feed watched

    It says there is nothing to open instead of doing nothing. W, not Shift + W, spreads a category.

  • Fix
    A letter on a widget's row does nothing

    With the cursor on a widget's row, a row letter (e, d, …) opened the search panel and took the cursor off the grid; the letters belong to no one there and are swallowed, as before the move.

  • Fix
    The widget menu names W for its width

    not Shift+W, like the other title letters in that menu.

  • Fix
    Menu chips announce the plain key

    A screen reader read Shift plus E for a row action whose key is now e.

  • New
    The Shift+Q search-mode tip is gone

    its key having moved.

Mode strip

  • New
    A line beside the page name says what the keys do

    Cursor, N ticked, Edit mode or an armed g chord, with the keys that apply; with none of those it names the mode the keys are in (search on the grid, browse elsewhere). It sits on the page-name line in the classic clock layout, sticks while the page scrolls, stays readable on every theme, fades after two seconds idle and is not drawn below 900 px.

  • New
    It suggests keys for the row under the cursor

    At most four: up to two from the row (down, unfiled, no tags or a tag to filter by, pinned, a video), one that rotates through all row letters, and one letter you have used fewer times than the rest; Ctrl/Cmd + Z goes first while a pin or move can be undone. The use counts stay in localStorage.

  • New
    Shift + S switches it off and on

    with a toast, and so does its switch under Behavior. A one-time note points at the strip, with Got it and Turn it off.

  • Fix
    The strip's note shows after the strip has faded

    The one-time note waits until the strip is drawn, and a strip that had faded after two quiet seconds counted as not drawn; a note that queued behind another (or a slow page) never showed. Asking for the note now brings the strip back from its fade.

  • New
    The strip wears the theme

    It is drawn as the other small layers are (the bell, the digest bar): on a Signature material it takes that material's plate, sheen and edge, and stays a pill; Classic keeps its flat plate with the second-level shadow; with Effects off it loses the decoration and keeps the fill. Before, it was one plate in the page's background colour on every theme.

Key legends

  • New
    Every view has a key legend

    The dashboard's is four lines now: the cursor, finding things, going somewhere, acting on a bookmark. The tag view, the Inbox, the Bookmarks view, Containers, Glances and Config each get one, sticky, switched with Shift + H. Each view has a setting for where its legend sits: below (the default), above, or off.

  • New
    Menus, tours, the start guide and the cheat sheet show the new keys

    The right-click menu names each row letter; the dashboard, Bookmarks, Containers and Inbox tours, the keyboard tour, the printable cheat sheet (nextDash-cheatsheet.html and .pdf) and the registry follow.

Keys and help

  • New
    ? opens a sheet for the page you are on

    This page says where you are, what it is for and the first steps, each with its key; a safe step (a move, a view, a palette mode, an aid on or off) has a Try it button. All keys is the full list, the modes and the learning material (every tour, this page's first) have a tab each, and one filter searches across all four, Help prose included. Keys you have not used yet come first. The keys named are checked against the registry by a spec.

  • New
    A Help panel opens the sheet on its own page's keys

    and the bell has its own entry.

  • Fix
    A long Help quote no longer leaks its key style over the sheet

    The sheet cut a Help paragraph of more than 520 characters at a space in the markup; a space inside <code>Shift + B</code> (in Chinese nearly every space is one) left <code> open, and the browser carried it over everything below. clipHtml closes what the cut leaves open and drops a half-cut entity or tag.

  • Fix
    A damaged tip list cannot stop the sheet from opening

    A value in nextdash:sheet-tips-shown that was valid JSON but not a list ({}, 5) threw in tipFor, so ? and F1 did nothing. It now counts as no tips shown.

  • New
    An arrow says the sheet runs on below the fold

    A round arrow in the lower right corner bobs while there is more to scroll, and goes at the end of the list, on a short tab or when the filter leaves nothing to scroll. A click scrolls one screen down and leaves focus in the filter. A ResizeObserver on the scroller and its panels follows tab switches, the filter and show all; the bob stops under reduced motion.

Shortcuts-changed window

  • New
    Existing installs are told the keys moved

    A window shown once, with the main moves; it closes only after ticking that you have read it, not with Escape or a click beside it. A fresh install never sees it. English only, like What's new.

Search palette

  • New
    Tags in the palette

    # on the dashboard opens the palette on tags; #docker and tag:docker mean the same. AND and OR join tags (docker AND linux OR network, AND binds tighter), written the same in every language. While a word is not yet a whole tag the palette offers tags that complete it, then AND and OR. A # inside a finder query or a question to the assistant stays text.

  • New
    : opens on the commands, with two lists

    Recent and most used side by side on one line, each with its own label; how often each command ran is counted on this device only.

Notifications

  • New
    Two key tips in the bell

    One for the mode strip and Shift + S, a minute into the first visit; one for the key legend and Shift + H, three days later. The start is kept in the seen promos, so it survives a reload and other browsers.

  • New
    A bell tip that the cheat sheet is now Keys and help

    For an install from before v1.27.0, once the window about the moved keys has been answered: it says that ? now says where you are, gives first steps to try and searches the Help, with a button that opens it. A fresh install never gets it; read once, it is gone.

  • New
    A tip for people who watch feeds

    The news moved from Shift + N to Shift + W; shown only while a feed is watched.

  • Fix
    Reading one feed item no longer rings as news

    The server lists the newest ten items, so reading one moved an older one into the list and the bell took it for news. The row now keys on when news last arrived per site.

  • Fix
    A row that comes back rings again

    even with a lower count than before it went away (5, gone, then 3 stayed silent).

  • New
    The install count is no longer announced

    The notice is gone; the switch stays under Privacy.

Config

  • New
    A Support card on Config → Overview

    Under its own Support nextDash heading, with a Ko-fi button.

Bookmarks view

  • New
    Add Bookmark sits in the view's band

    left of Work through.

Themes

  • New
    Three holiday themes

    Christmas Classic, Northern Lights and Gingerbread Village, light and dark. Over the backdrop they draw a tree, a forest or a village and lights, with snow or sprinkles falling in front; category headers get snow caps or icing. The snow lands in the same places on every load. Motion stops with reduced motion and with Effects off, leaving a still picture.

  • New
    A Holidays group in the theme browser

    shown in place of the archetype in the badge and the Character row.

  • New
    A gingerbread baking-tray backdrop

    .

Docs

  • Docs
    Manual and README: the keys

    Every key in the manual and README follows the new scheme; §4 describes the four-line legend and Shift + E for edit mode, §7 the plain row letters, §8.6 finders on !, the tag view, Inbox, Containers and Bookmarks view the Shift + H legend.

  • Docs
    Config → Help and tips

    Help and the tips name the new keys; the bell has its own Help topic and a ? for keys and help. Nine texts that still named old keys now follow the scheme: Daily use (e, m, t), Appearance (v for the preview card), Tags (Shift + T whatever is selected), Health charts (l), the Inbox, Triage and Unsorted (m keeps a link), a Health tip (l) and the Structure tip (Manage in the rail, since Shift + P and Shift + C open the Pages panel and Containers). Finders on their own read ! w, not ?w, in Help and the manual.

  • Docs
    Cheat sheet

    nextDash-cheatsheet.html and the PDF (root and static/) are generated again: W, not Shift + W, spreads a widget.

  • Docs
    Translations

    The 334 new strings (mode strip, Keys and help sheet with its page help, key legends, tips, notes, Support card, palette tags) and the 98 changed ones in Dutch, German, French, Spanish and Chinese. The locale files are in parity again. dashboard.cheatsheetTabsLabel was in en.json twice, and the later Shortcut topics hid Keys and help. commands.paletteMostUsed and config.bmNoTagToFilter were asked for in the code but missing; they are added in all six.

  • Docs
    README

    390 themes, 195 families and 267 backdrops; Tarnished Brass named as the default (it still said Aurora Glass); the cheat sheet on ?, edit mode on Shift + E, and the key legend, mode strip and keys and help in the keyboard lines.

  • Docs
    Manual

    The mode strip (§4), the key move with the old keys that still answer (§7), keys and help with its four tabs and the arrow (§7.6), tags as a search mode with #, AND and OR (§8), the Holidays group (§17.1) and the Support card on the Overview (§18.8); the cheat sheet line at the top reads ?, and the quick reference in §26, the preview card, the QR caption and the Bookmarks view's QR line use the new keys.

  • Docs
    Config → Overview and About → News & features

    Four entries with since: v1.27.0 in overview-features.json, in six languages: one set of keys, the mode strip, tags in the search panel and the holiday themes.

  • Docs
    nextdash.cc

    feature-pages/v1.27.0-pages.php puts the new keys on nineteen feature pages and their Try it boxes, writes the Keys page anew around the one scheme, the strip, the legends and keys and help, adds tags with AND and OR to Find, the Holidays section to Themes and the legend to Glances. The front page, the stats strip, the gallery intro and the comparison say 390 themes, 195 families, 267 backdrops and 53 widget kinds. New pictures of keys and help, the four-line legend and Christmas Classic.

  • Docs
    static/data/whats-new/v1.27.0.json and its index entry

    with three highlights and their recordings: the search panel, one set of keys and the mode strip. whats-new-stub.js names v1.27.0 in DASHBOARD_RELEASE, so an upgraded install opens the notes once, and moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v367; whats-new-hidden-release.spec.js follows.

  • Docs
    A Go check knows Keys and help

    TestNoScriptOutsideConfigReadsALazyKey failed on keyboard-page-help.js, which quotes Help panels; the sheet loads the help scope itself before it builds, so the file is exempt, with the reason in the test.

  • Docs
    Help drawings use the new keys

    and the bell's Help article gets one: Shift + N, Enter, ? (config.helpArtBellKeys, six languages). Daily use, Search, Finders, the Config keys and Unsorted drew ? for finders, ! for the cheat sheet, Shift + E and Shift + K.

  • Docs
    Thirty specs follow the new keys

    CI on the first push failed 48 tests in 38 specs: most pressed the old keys (Shift+M, Shift+D, Shift+T, Shift+C, Shift+W, Shift+Q, Shift+K, Shift+E, , for pages, Shift+N for the news, s for the Health tab); the rest clicked into the bell's coach note, which tests/fixtures.js now marks seen on a page's first load, with the action-bar and mode-strip notes.

  • Docs
    The arrows are clicked standing still in tests, and the keys window waits

    The arrow of the keys window and of Keys and help bobs without end, so a click on it never found it stable in CI; their specs ask for less motion. tests/fixtures.js also marks the window about the moved keys seen on a first load, since an install CI counts as existing opened it and the coach notes waited behind it.

  • Docs
    Every fixed wait in the tests says why

    validate:test-waits failed in CI on 38 bare waitForTimeout calls added with the new keys; each now has a reason above it (most guard a check that nothing happens), and one in bookmarks-shift-b.spec.js waits for the address instead.

  • Docs
    Unraid template

    nextdash.xml carries the v1.26.1 date and changes.

Only docs and tests changed in this release.

v1.26.1 Watched news no longer piles up while you are away: it stops counting after a set age, and the bell holds one line for it instead of a toast. +10 3 fix

Watched news no longer piles up while you are away: it stops counting after a set age, and the bell holds one line for it instead of a toast. Every row in the bell now says how old it is, and the bell panel no longer sits under the buttons of the Inbox, Containers and Glances views.

Watch feeds

  • New
    News stops counting after a while

    Count news as unread for (Config → Watch feeds) takes 4 or 8 hours, 1 day (the default), 2, 3, 7, 14 or 30 days. News nobody opened for that long leaves the purple count, the hover card and the bell. The news window still lists it, dimmed like read news, until newer news pushes it out.

  • New
    The bell holds one line for new news

    The toast is gone. A single row, N new from M watched feeds, in its own Watch feeds group, is updated in place when more arrives instead of adding another. It leaves when the news is read or has expired, Mark read puts it away until there is more, and a bookmark whose feeds are all muted stays out of it.

  • New
    The hover card pages through ten items

    It used to show the three newest unread items; it now carries up to ten.

  • New
    The hover card names the total

    When more is unread than the card carries, its pager reads 1 / 10 · 25 new, and a link in the summary takes the card's text colour instead of the browser's blue.

  • New
    The bell nods for news

    New news from watched feeds moves the bell differently from an alarm: it nods once and a small paper slides in beside it. The hourly nudge does the same when news is all that is unread.

  • Fix
    No dot on the page tabs

    A page tab no longer gets a dot when another page holds unread news; the purple count on the bookmark and the bell are the signals.

  • New
    The purple count stops at 9+

    From ten unread items on, the count on a bookmark reads 9+; the tab title keeps the exact number.

Preview card

  • New
    No hover card in the phone layout

    Below 768 px the card stays away, and it comes back when the window widens, without a redraw.

Notifications

  • New
    News from watched feeds has a tone of its own

    A soft two-note chime instead of the warning bell; the bell keeps its tone for everything else, and Bell sound for new notifications still switches both off.

  • New
    A nudge every hour

    While anything is still unread the bell shakes and pulses once an hour, without a tone, on top of the quiet pulse every minute.

  • New
    Every row in the bell says how old it is

    The time (5 min ago, 2 days ago) sits on the right of the row and starts over when the row gets worse: more of the thing, or something new in it. A row that only shrinks keeps its age, and the times survive a reload on the same device.

  • Fix
    The bell rings only for more, not for less

    When a row's count fell (one site opened, an item expired), the next refresh counted it as new and rang again. It now rings when something is added.

  • Fix
    The bell panel draws over the view headers

    On a theme without backdrop blur the buttons and selects in the header of the Inbox, Containers and Glances views showed over the panel. The panel now sits above them.

Docs

  • Docs
    Manual

    §4 names the Watch feeds group in the bell, the age on each row, the chime and the hourly nudge, and says the hover card stays away in the phone layout; §14 describes the one bell row, the 9+ count, ten items in the hover card with the total, the new Count news as unread for setting, and Bell and push on a muted feed.

  • Docs
    Config → Help

    Watch feeds and Alerts & notifications describe the bell row, the expiry, the pager with its total, the age on each row and the hourly nudge, and no longer mention a dot on the page tab or a toast.

  • Docs
    Tips

    A new tip, News stops counting after a day, leads to the setting; the tips for the hover card pager and the bell say ten items and the age of a row. The unused toast strings are gone.

  • Docs
    Pictures

    The manual's pictures of the bell (with a Watch feeds row and the age of each row), of the news popover and of Config → Watch feeds are taken again, and the bell page and the Watch feeds page on nextdash.cc describe the expiry, the chime, the nod and the hourly nudge, with new bell pictures.

  • Docs
    Translations

    The new strings in Dutch, German, French, Spanish and Chinese: the setting and its choices, the bell row, the tip and the changed Help text. A muted feed's switch now reads Bell and push.

Only docs and tests changed in this release.

v1.26.0 A notifications bell in the navigation bar, a greeting with your name beside a large clock, a Clock widget with a face, the moon and the sun, and a lighter start: the theme stylesheet shrinks from 9.4 MB to 379 KB. +19 24 fix Read the post

A notifications bell in the navigation bar, a greeting with your name beside a large clock, a Clock widget with a face, the moon and the sun, and a lighter start: the theme stylesheet shrinks from 9.4 MB to 379 KB. Eight fixes from a code review ride along, and a new install starts on Tarnished Brass.

Notifications

  • New
    A notifications bell in the navigation bar

    New things that need you wait in the bell instead of popping up on the dashboard: maintenance and privacy questions, urgent notices and outages, the notice that an update was installed and the one that a new release is out (no toast any more), the digest card (once per digest) and the tips. Rows are grouped (Health, Clean up, System, Privacy, Tips). No answers a question for good and the row slides away; Mark read and Mark all read clear the rest. The bell keeps its place in a folded header, its header and a More below arrow stay put while the list scrolls, and a first-time note explains it.

  • New
    The bell shakes and rings for something new

    It shakes and pulses, with a short bell tone you can switch off in Config (Bell sound for new notifications).

  • New
    Config can bring back dismissed notifications

    Bring back dismissed notifications puts every answered No and every read row back in the bell.

  • New
    Tips: two a day, each leading to its own place

    Two new tips a day wait in the bell, whether or not yesterday's were read. Each has a button to the place it is about (Config, the Inbox, the Bookmarks view, Containers, the tag cloud, the palette and more).

  • Fix
    A row you took up stays away

    Pressing the coloured button on a row (Start, Open the Inbox) slid the row out and closed the panel, but the row was back the next time the bell opened. It is now put aside until it gets worse, the way No does, without telling the source that anything was declined.

  • Fix
    Tips no longer offer a pace they do not keep

    Keyboard tips come (a day or a week) is gone from Behavior → Privacy & sync → Onboarding: the bell holds two tips a day whatever it said. Its hint and the ℹ of Show occasional keyboard tips describe the bell now, and the offers for tag suggestions and link review say they wait there, in six languages.

  • New
    Mark read in the Watch feeds popover

    The popover has a Mark read button, quieter than the Reader button beside it.

  • New
    Bell usage in the analytics

    The bell reports how it is used, in fixed words and bucketed counts; the text of a notification never leaves.

  • New
    One-time notes for the bell and the action bar

    A short coach note says what the bell is and what the action bar offers, once.

Header

  • New
    A large clock in the classic header

    The clock placement Large clock, greeting beside it draws the time large with the greeting on its side and a halo on both corners; the other two placements keep their single line.

  • New
    Your name in the greeting

    Your name (Config → Appearance → Date & time, in its own Greeting group) turns the first line into "Good evening, Jordi"; it changes with the hour. Leave it empty to be greeted without a name.

  • New
    The quick start asks for the name

    in a new About you step, and existing users are asked once in a coach note.

  • New
    Tarnished Brass is the theme of a new install

    Installs that already chose a theme keep it.

Clock and Countdown

  • New
    The Clock widget has a face

    A large analogue clock, other places listed under it (the face shows the first three), with a seconds hand, the moon and its phase and sunrise, sunset and daylight for your weather location. The moon and the sun appear when the widget is two columns wide; Plain lines of time keeps the old look.

  • New
    The Countdown shows its figure large

    in the middle, with the date under it.

DNS blockers

  • New
    AdGuard Home and Pi-hole widgets

    One tile for both, on the shared media base: queries, how many were blocked, a day by the hour, and the top blocked domains and clients. Four looks, chosen in the settings: pulse (one big blocked percentage and the last day as a strip, the default), leaders (the top lists with bars), tiles (four figures and the hourly chart) and mix (pulse on top, the lists below, two columns only). A click opens a card with the top ten lists and a button to the service, or goes straight there when the click is set to open. A figure the service did not send is not drawn, and no queries has no percentage rather than 0 %.

What's new

  • New
    A compact What's new window

    A Ko-fi bar replaces the card, and the screenshots open larger on a click.

Docs

  • Docs
    Translations

    The bell, the greeting, the tip buttons, the action-bar note and the AdGuard Home and Pi-hole widgets in Dutch, German, French, Spanish and Chinese. Forty-one strings that only had an English fallback in the code (the DNS widgets, the What's new footer, Mark read in the Watch feeds popover) are now in en.json and translated. The French header clock option and the greeting strings no longer show English.

  • Docs
    Config → Help

    Header & action buttons covers the large clock, the greeting and the bell; Alerts & notifications has a paragraph on the bell; Widget kinds counts fifty-three kinds, adds AdGuard Home and Pi-hole and describes the clock face.

  • Docs
    README and manual: the default look

    A fresh install starts on Tarnished Brass in the manual (§17, §17A.3) and the README, which also counts fifty-three widget kinds, names the Clock face, AdGuard Home, Pi-hole and the bell, and has a new dashboard picture. The other README pictures (Containers, Glances, the Bookmarks view, Inbox, search, Config and Unraid) are retaken on the current app, each in the theme its caption names; the two collages of all themes are unchanged.

  • Docs
    Tips

    Four new tips: the bell, your name in the greeting, the clock face and the DNS widgets. Each leads to its place from the bell.

Browser extension

  • Fix
    The saved panel no longer stands open

    A rule in popup.css had lost its selector line and swallowed the .hidden rule after it, so Bookmark saved… open in nextDash showed under the buttons from the first look, and the form did not hide after a save.

  • Fix
    The duplicate-address warning shows again

    The panel carried both a hidden class and the hidden attribute popup.js sets; once the .hidden rule was back, the class kept the warning out of sight for good. It now uses the attribute alone.

Bookmarks view

  • Fix
    Fix first lists a shared address once

    Two bookmarks with the same address gave two identical lines in Collection health → Fix first (Docker Hub — Duplicate URL in 2 bookmarks, twice). They are one place to start now.

Reset and start-up

  • Fix
    A factory reset forgets the weekly digest

    digest.json survived Reset all data, so a digest made before the reset was offered to the new install as its first week, and the link-review row waited behind it. The file goes with the rest now.

  • Fix
    The Quick start leaves no bar behind when it was finished already

    When its script arrived after the guide had been answered, it still drew its bar for half a second before taking it away. It checks first and draws nothing.

  • Fix
    The Quick start keeps °F when you click it straight after typing a city

    Leaving the city field and clicking the unit saved twice at once, and the save with the old unit sometimes landed last. The Quick start's saves now go out one after the other.

Search

  • Fix
    A Help search keeps its results when the page is slow

    The release heading and the Help text arrive a moment after Config → Help opens; when they came after you had already searched, Help wrote Getting started back over the results, with your words still in the box. They now redraw the results instead.

  • Fix
    The calculator reads a decimal comma

    1,5 + 1 is 2.5 and 15% van 2,5 is 0.375; before, every comma was dropped and 2,5 became 25. A comma before exactly three digits still groups thousands (1,000, 1,234,567).

Widgets

  • New
    Settings in a widget's menu opens its sheet over the dashboard

    The same sheet the edit panel's Settings opens, so you stay where you are; Config → Widgets opens only when the sheet cannot be drawn.

  • Fix
    A Tabs widget off its schedule gives its widgets back

    Outside its time window or on a day it is off, a Tabs widget is not drawn, and the widgets in its tabs now stand in the grid instead of disappearing with it.

  • Fix
    Copying a widget keeps a widget saved meanwhile

    The copy is inserted into the page as it stands at that moment, under one lock, so a widget added or changed in another tab while the copy was made is no longer written away.

  • Fix
    The Tabs settings offer only what can be kept

    A widget that another Tabs widget already holds is no longer offered, and with six tabs ticked the other boxes wait until one is unticked; before, the server dropped both without a word on save.

  • Fix
    Config → Glances waits for its settings before it can be used

    A click on Test connection in the moment before the settings were read got its answer, which was then wiped when they arrived; a choice made in that moment was not saved at all. The fields and the button stay shut until the settings are in.

Digest

  • Fix
    A day that was down shows on the uptime chart

    A day on which every check failed was stored as 0, the same value as a day without checks, and left out of the line. Days without checks are now -1 under a new key (uptimeDays), so a digest saved before draws no uptime chart rather than false outages.

  • Fix
    The bars of opened bookmarks are calendar days

    They counted 24-hour spans ending at the moment the digest was made, so an evening landed under the next day's name. They now follow the days in the time zone the digest is sent in.

Import

  • Fix
    A Homepage file with aliases stops at its limit

    A group listing the same aliased set of services many times kept adding rows after the import's budget was spent, so a small file could take minutes and a lot of memory before it was refused. It now stops at the limit.

Appearance

  • Fix
    Checkbox rows in Appearance line up with the other labels

    The toggle's hover padding sat inside the column, so its words stood 8 px right of every other label and the box 8 px left of the control's edge.

  • New
    Every Appearance tab lists its sections under the preview

    The list beside the settings now shows on every tab, not only on Date & weather, and stands under the preview, so the preview stays in place when you switch tabs. The entries are larger, and the section in view is marked with a bar.

  • Fix
    The backdrop picker no longer holds on to old thumbnails

    Each search keystroke made a new observer for lazy painting and never let the old one go, so hundreds of thumbnails that were no longer on the page stayed in memory. One observer per picker now, released when the picker is drawn again.

  • Fix
    The last Appearance tab you click is the one that stays

    Clicking Theme and then Rows straight away, while the theme was still being saved, could end on Theme: the first switch finished last and took the page back. A switch that has been overtaken now stops.

Performance

  • Fix
    The theme stylesheet no longer carries every backdrop

    /api/theme.css held the colours of all 386 theme blocks and, inside each, an inline SVG backdrop of ~24 KB: 9.4 MB, 920 KB gzipped, in front of the first paint. It is now 379 KB (41 KB gzipped). The page opens with the backdrop of its own theme inline; theme-loader.js watches data-theme and data-backdrop-recipe and asks /api/theme.css?scope=backdrop&theme=…&recipe=… for any other the document switches to, whoever writes the attribute. On a 10 Mbit line with 80 ms latency a cold load paints in 0.6 s instead of 2.0 s. The seed and the neutral accent follow the same route (reloadBackdropCSS), and the endpoint is revalidated by ETag (weak ones from a proxy match). A reload that lands while another theme was being fetched asks for that one again. At most 8 themes and 8 recipes per request.

  • New
    Icons are stored at a size they are drawn at

    A fetched or uploaded PNG or JPEG larger than 192 px is scaled down (alpha kept) and a multi-size .ico whose best entry (the smallest of 64 px or more) is a PNG is stored as that PNG; a 512 px, 324 KB icon becomes 59 KB. Anything unreadable, animated (GIF, APNG), vector, a JPEG turned by its EXIF orientation, larger than 2048 px square, or an .ico whose best entry is a bitmap is stored as it arrived, and a result that is not smaller is dropped. Icons already stored are not rewritten.

  • Fix
    Start-up asks for the same answer once

    The update status, the app discovery and the data revision were each fetched two or three times by their separate readers, and two health-trend tiles each fetched the whole series. Callers that arrive while a request is on its way now share it (nextDashFetchShared); nothing is kept once it has answered, and a read made after one of our writes began never joins a request that started before it (fresh: true for the reads that follow a save).

  • Fix
    What's new recordings wait until they are seen

    Every spotlight recording started downloading (300 KB each) when the window opened, whether it was on screen or not. They now load and play when scrolled into view, and pause when scrolled out; closing the window lets go of what watched them.

  • New
    Media tiles show their last answer while the real one is on its way

    After a reload, a Jellyfin, Arr, Seerr, downloads, Home Assistant or Beszel tile drew its waiting line until the service answered. It now draws the answer from a moment ago at once, with how old it is, and replaces it when the real one arrives. The answer is kept in sessionStorage for the tab only, never shown when older than ten minutes, shown without its controls, and a failed or partial answer is not kept. If the service does not answer, the held picture stays on screen with its age instead of "unreachable".

  • Fix
    The Overview's text is fetched with the settings

    The ~99 KB of Overview strings joined the Help prose in the lazy locale scope (scope=help), so the language file every dashboard loads is 17% smaller (181 KB gzipped from 220 KB). The three strings the update notice and the What's new window print stay in the core scope, and a test fails when another script outside the config module starts reading one that is not.

Only docs and tests changed in this release.

v1.25.1 The manual now covers the widget schedule, the Watch feeds news widget, the settings of each widget kind, the phone settings and every search command and key that was missing. docs

The manual now covers the widget schedule, the Watch feeds news widget, the settings of each widget kind, the phone settings and every search command and key that was missing. No change to the app itself. Held back from the What's new window (hideFromModal), so v1.25.0 keeps leading it.

Docs

  • Docs
    The manual says when a widget shows

    §16.2 has its own heading, When a widget shows, in the table of contents, with an example for office hours and one that runs past midnight.

  • Docs
    The Watch feeds news widget is in the widget table

    with its three layouts, and the row for a Feeds widget that no longer exists is gone. §14.2 points to the widget.

  • Docs
    Settings per widget kind

    A table at the end of §16.1 lists what the settings panel of Processor, Memory, Disks, Containers, Health, Uptime, Certificates, Domains, Neglected, Trash, Backups and the other kinds offers, with ranges and defaults.

  • Docs
    Settings that were missing

    On phones and tablets (§18.5, §23); the Watch feeds settings, statistics and the alert channel (§14.4); the digest with feeds, the contact address for push and the delay between retries (§12); the page and category for imports and Page to save (§20.2); Offer to review tag suggestions; Archive service and Weather location; and certificate warnings from 3 to 120 days.

  • Docs
    Commands and keys

    §8.5 lists :action, :clock, :time, :unit, :weather, :highlight, :items, :collapse, :empty, :tags, :share, :import, :archive, :ask and :tour. §7.4 has the keys on a widget row and in a Tabs widget, and the chart keys are in §11.8 and §15.3.

  • Docs
    README

    The two collages of all 192 dark and 192 light themes sit behind a collapsed link.

Only docs and tests changed in this release.

v1.25.0 Widgets get a lot more to do: a Tabs widget, Clock and Countdown, duplicate, set times and days, and limits for disks and memory. +23 9 fix Read the post

Widgets get a lot more to do: a Tabs widget, Clock and Countdown, duplicate, set times and days, and limits for disks and memory. Search answers sums, Config shows what you changed from the defaults, a page keeps a history of its layouts, Homepage, Dashy and Homer configurations can be imported, and the backdrops are redrawn one recipe per theme. A fresh install starts on Aurora Glass.

Widgets

  • New
    A Tabs widget

    Several widgets in one tile, with a tab for each. Add it from the widget catalogue. Tabs are widgets of the same page; a tab that moves to another page leaves the Tabs widget.

  • New
    Clock and Countdown widgets

    A clock for any time zone and a countdown to a date.

  • New
    Duplicate a widget

    The widget's menu has a Duplicate entry that makes a copy with the same settings.

  • New
    Show a widget only on set times and days

    Every widget type has a window of the day (it may run past midnight) and the days of the week. Both times or neither; all seven days is the same as no limit.

  • New
    Amber and red limits per disk and memory widget

    Set where the figure turns amber and red, in percent used, so a full archive disk need not be red. A pair that makes no sense (red before amber) is ignored.

  • New
    Refresh now

    The menu of media, Beszel, Home Assistant and custom widgets has a Refresh now.

  • New
    Uptime widget: response time of the last day

Layout

  • New
    Layout history

    nextDash keeps earlier arrangements of each page. Pick one in Config, see what restoring it would change, and restore it. A restore keeps what it replaces, so it can be undone. The history travels in the backup.

Search

  • New
    Search answers sums

    Type 15% of 240, 2+2*3 or 5 km in mi and the answer is the top row; Enter copies it. Nothing leaves the browser and nothing is evaluated. A word, shortcut, date, phone number or range such as 24/7 is never taken for a sum.

  • New
    Six more commands

    :news, :unsorted, :studio, :cloud, :legend and :hypr.

Config

  • New
    What you changed from the defaults

    A list of every setting that differs from the default, and an Overview panel with the same list.

  • New
    Actions next to settings in Find settings

    A found setting can be acted on from the result.

  • New
    Overview chips

    Expiring certificates, failing widgets and a failed backup show up as chips.

  • New
    Data & backups says what can be imported

    Cards name each kind of file.

  • New
    Import a Homepage, Dashy or Homer configuration
  • Fix
    Config no longer moves while a setting is saved

    The page is held in place in any browser.

  • Fix
    Config tours do not open over a section you have left
  • Fix
    "Nothing changed" says the right thing

    The message of the What you changed list and the one on a settings tab shared a text key, so a tab said Every setting is at its default. Each has its own now.

Themes

  • New
    A backdrop recipe for every theme

    Each backdrop pair, each Look and Ocean (its own sonar) has a recipe of its own, drawn in the theme's colours.

  • New
    A better backdrop picker

    A short view, groups, search and thumbnails that load when you scroll to them. The backdrop settings sit with the backdrops in the theme studio.

  • Fix
    The backdrop groups are in English

    The groups in the backdrop picker (Patterns, Colour & glow, Fire & light, Nature & water, Sky & space, Materials, Paper & ink, Tech) were Dutch in every language; they are English now and translated in the other five.

  • Fix
    The eight neutral themes draw their own backdrop

    Neutral, Stone, Gray, Zinc, Slate, Chalk, Concrete and Black still pointed at an old shared recipe, so their new backdrops were never drawn.

  • Fix
    The backdrop picker keeps the focus on the tile you clicked

    In All backdrops a click put the focus on the copy of that backdrop under Used lately, so the keyboard carried on from the wrong place. It stays on the tile you chose.

  • New
    Aurora Glass is the default theme

    on new installs. Installs that already chose a theme keep it.

  • New
    Tag colours

    Give a tag a colour; it shows in the tag cloud, the rows and the preview.

Rows

  • New
    Online/offline status is on again for new installs

    Loading state and Ping times stay off. Installs that already have these settings keep them.

Watch feeds

  • New
    Statistics CSV includes the watched feed figures
  • New
    The weekly digest is easier to read

    with charts.

  • Fix
    The news button shows only with an active feed

    and returns to the open article.

  • Fix
    Saving a watch feed keeps the scroll position
  • Fix
    Clearer picker

    Stop on the left, Save (in the accent) and Cancel (in the warning colour) on the right; the empty section explains itself.

Assistant

  • New
    Tables and leaner answers

    The panel renders tables, and the assistant is asked for a shorter answer layout.

Docs

  • Docs
    Config → Help and its tips are current

    Help says fifty-one widget kinds and lists the new ones, 266 backdrops with the short picker, the new commands, sums in search, tag colours, importing a Homepage, Dashy or Homer configuration, layout history, What you changed and the Overview chips. Nine new tips cover the Tabs widget, set times and days, the widget menu with its limits, tag colours, sums, What you changed, layout history, importing another dashboard and the extra commands.

  • Docs
    Translations

    The v1.25.0 texts are in Dutch, German, French, Chinese and Spanish: all 202 new interface texts, the Help and the tips, and 47 texts that code asked for but en.json did not have (the digest, the backdrop picker, six commands).

  • Docs
    MANUAL, README and the pictures

    The manual and README describe every new feature, count 266 backdrops and fifty-one widget kinds, and say a fresh install starts on Aurora Glass. The manual and README pictures were retaken in Aurora Glass.

  • Docs
    Config → Overview and About → News & features

    list five v1.25.0 features (new backdrops, Tabs/Clock/Countdown, layout history, search sums, what you changed and the import), in six languages.

  • Docs
    Cheat sheet

    The cheat sheet and its PDF have a row for the arrow keys, Home and End in a Tabs widget.

  • Docs
    static/data/whats-new/v1.25.0.json and its index entry

    ; the release leads the What's new window with three highlights (Tabs, Clock and Countdown; search sums; a backdrop for every theme). whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v363 and DASHBOARD_RELEASE to v1.25.0. go generate refreshed asset_hashes_gen.go.

  • Docs
    nextdash.cc

    The feature pages for widgets, search, Config, data, tags and themes show the new features with pictures; the theme gallery is retaken for all 192 families; the figures on the site are 266 backdrops and fifty-one widget kinds. About thirty wrong or stale sentences on the site were corrected (default theme, keys, tab names, chapter numbers, counts).

Only docs and tests changed in this release.

v1.24.2 Config → Watch feeds gets tabs like the other sections, the news popover has its Reader button on a phone too, and a new install starts without row status. +3

Config → Watch feeds gets tabs like the other sections, the news popover has its Reader button on a phone too, and a new install starts without row status. Held back from the What's new window (hideFromModal), so v1.24.0 keeps leading it.

Watch feeds

  • New
    Config → Watch feeds has two tabs

    Feeds lists the watched feeds; Settings holds how their news reaches you (the check window, the news view, push). The tab you left on is remembered, the address follows it (#config/feed-watch/settings), and the settings search sends a news setting to the Settings tab. Older links to the settings on the Bookmarks tab open it there too.

  • New
    The Reader button in the news popover is on a phone too

    Tap a row with news and the head of the popover shows Reader between the bar to the site and the cross, as on a computer. It opens the news window on that site alone.

Rows

  • New
    A new install starts without row status

    Config → Appearance → Rows → Row status: Online/offline and Ping times are off by default now (Loading state already was), so a fresh dashboard shows rows as just their names. An install that already has these settings keeps them as they are; they are one click away for anyone who wants them.

Docs

  • Docs
    The Help text of Watch feeds is current

    It names the two tabs and the popover with its Reader button (on a computer and a phone), and gives the news view setting as Config → Watch feeds → Settings; all six languages.

  • Docs
    The manual says so too

    §14.4 describes the two tabs and §14.2 the Reader button on a phone, with retaken pictures. The new look is §17A, so Glances keeps §16A.

  • Docs
    static/data/whats-new/v1.24.2.json and its index entry

    , flagged hideFromModal; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v362 and DASHBOARD_RELEASE stays on v1.24.0. tests/whats-new-hidden-release.spec.js follows. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.24.1 A small follow-up to Watch feeds: the One column news window no longer opens on a long list when nothing is new, and adding a feed says what to expect. +1 1 fix

A small follow-up to Watch feeds: the One column news window no longer opens on a long list when nothing is new, and adding a feed says what to expect. Held back from the What's new window (hideFromModal), so v1.24.0 keeps leading it.

Watch feeds

  • Fix
    One column is one article at a time, also when nothing is new

    With Show news as → One column the window walked only the new items. When none were new (everything read, or the window opened by hand with nothing waiting) it fell back to the front page and listed every earlier entry, 68 of them in one reader's case. It now walks the feeds' earlier entries one by one, with the counter and the arrows, and no Index button; with news waiting nothing changes. tests/feed-watch-news.spec.js opens it with twelve earlier entries and nothing new, and fails without the change.

  • New
    Adding a feed says what to expect

    When you save, nextDash reads the feed once and counts what is already there as seen, so a bookmark shows no news (and a click still opens the site) until the site publishes something new. The toast after saving now says so: Watching {name} · checked every {interval}. You'll see news when it publishes something new. It shows after the right-click menu and after the bookmark form, in six languages.

Docs

  • Docs
    Watch feeds is its own chapter in the manual

    It was §12.6 under Checks & health; it is now §14, after Inbox, with four sections (14.1 Following a site, 14.2 What you see, 14.3 The news window, 14.4 Managing it). Containers is §15, Widgets §16, Glances §16A and the chapters after it each move up by one, to Glossary at §27; the contents, the §-references, the anchors and the README's links follow, and Keeping a copy of a page and The status page become §12.6 and §12.7.

  • Docs
    The manual says what a new feed does

    The Start paragraph now explains that a feed's existing entries count as seen and when news shows; the news window paragraph describes One column with nothing new.

  • Docs
    static/data/whats-new/v1.24.1.json and its index entry

    , flagged hideFromModal; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v361 and DASHBOARD_RELEASE stays on v1.24.0. tests/whats-new-hidden-release.spec.js follows. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.24.0 Watch feeds replace Fresh: follow the RSS (or Atom, or JSON Feed) feed of any site you have a bookmark for, get a stripe, a badge and a headline on the row, a preview card that leads with the news, and a news window of your own that reads like a paper; a safety pass over every file nextDash writes, so an unreadable file is never overwritten with defaults; the MCP endpoint answers counts and queries; a redesigned What's new modal and an assistant tour. +23 18 fix Read the post

Watch feeds replace Fresh: follow the RSS (or Atom, or JSON Feed) feed of any site you have a bookmark for, get a stripe, a badge and a headline on the row, a preview card that leads with the news, and a news window of your own that reads like a paper; a safety pass over every file nextDash writes, so an unreadable file is never overwritten with defaults; the MCP endpoint answers counts and queries; a redesigned What's new modal and an assistant tour.

Bookmarks view

  • New
    Select every bookmark

    Ctrl/Cmd + A ticks every bookmark the filter and the list search show, rows not yet drawn included, and pressing it again clears them; a Select all (N) / Deselect all button in the toolbar does the same. In the search field Ctrl/Cmd + A still selects the text. The manual claimed x / Shift + X and a Select all in the ⋯ menu did this; they never did, and §11.4 and §11.6 now say what each key does. Reported as issue #20; tests/bookmarks-view-select-all.spec.js covers it with more bookmarks than one drawn chunk.

Health

  • Fix
    A server with no connection no longer marks everything broken

    When nextDash started before the machine was online, the first round of checks recorded DNS lookup failed for every bookmark and filled the Bookmarks view and Work through with fake rot, which a restart did not clear. A round that reaches at least ten different sites and fails for at least 80% of them with a lookup, timeout, refused or unreachable error is now treated as the server's own outage: its failures are held back (no broken status, no sample, no alert, no incident), every bookmark keeps its earlier status, the Bookmarks view shows No connection from this server since …, and the round is tried again a minute later. Addresses on your own network are never held back; after thirty minutes failures are recorded normally. It covers the monitors, Retest all, the scheduled recheck and the checks the browser asks for; Retest all says why it held back. Nothing is sent to any third party. Reported as issue #20; if the first round after a start still marks your bookmarks broken, please say so on the issue, with the last error a bookmark shows. Go tests cover the rule around the 80% line, the real Linux and Docker error strings, long sweeps, overlapping rechecks and the thirty-minute limit.

  • Fix
    The first 15 minutes after a start are forgiving

    After nextDash starts, a bookmark's first failed check (any address, including your own services on the LAN and containers that are still starting) is not recorded: no broken status, sample, alert or incident, and the earlier status stays. The same bookmark failing again at least 45 seconds later is recorded, and an answer clears the first failure. Only unattended checks wait (the monitors, the scheduled recheck and the checks the browser asks for); Retest all records at once; copies of one address with their own rules share one decision, and the scheduled recheck retries once, not for the whole window. A service that is really dead is recorded a minute or two later than before, in that window only. NEXTDASH_HEALTH_STARTUP_GRACE sets the window (a duration such as 5m; 0 switches it off) and the end-to-end tests set it to 0; Docker, Glances and Unraid are not affected.

Watch feeds

  • New
    Follow the RSS feed of any site

    Right-click a bookmark → Watch this feed…, use the Watch feeds row of the bookmark form, or press # on the bookmark in hand. nextDash lists the RSS or Atom feeds the page advertises (and tries the usual addresses when the page says nothing, as it does behind a cookie wall), you tick one or more or paste an address, and you choose how often to check: 30 minutes, 1, 2, 4, 6, 12 or 24 hours. Up to 100 feeds can be watched. Nothing is followed until you ask, and nextDash only reads feeds: nothing is sent to anyone. The old Fresh feature is gone, with its texts and its walkthrough.

  • New
    What is read

    RSS and Atom, and JSON Feed too. Each item keeps its title, link, lead (reduced to a few safe tags, never scripts) and its picture; feeds that use another character set are converted. A feed that fails five times in a row is paused and tried again once a day, an aborted poll does not count as a failure, and a feed can be moved to its new address when the site moves it.

  • New
    What it keeps

    The ten newest new items of each feed with their text and picture, fifty recent entries as short copies without pictures, and the ids of the last 75 entries so nothing counts as new twice. Opening the bookmark (or an article's headline) clears its count; the purple mark and the news window close by themselves after 15, 30 (default), 60 or 120 minutes, counted from when the tab is in view. Check watched feeds now polls them all at once, and status:watched and status:unwatched search for followed bookmarks.

  • New
    Rows show the news

    A stripe, a bold name, the newest headline, a badge with a halo and a dot on the page tab for new items; a feed icon on watched bookmarks, muted and unhealthy states included (Settings → Show a feed icon on watched bookmarks, on).

  • New
    A paper for all the news

    One news modal for everything you watch, with read and unread per item, three layouts, one article per screen in one column, j/k through the news, and a masthead that stays at the top. Esc closes at once; the Index button goes back to the front page.

  • New
    The news popover

    Click a row with news for six headlines, a Reader button and an open-site button; it grows out of the row, +n more expands in place up to 10, and the layout fits the screen. On a phone a tap shows the headlines first and the bar on top goes to the site (five headlines).

  • New
    Manage in one place

    Config → Watch feeds (marked new in the rail) lists every watched feed with its newest item; follow several sites at once, and mute, pause or set a word filter per feed. Watch more puts sites with a feed first.

  • New
    Add one from the bookmark form

    A Watch feeds row saves with the bookmark, in place of the offer chip; adding a watch switches the availability check on, and one that is on stays.

  • New
    Dashboard

    A widget with the sites that have new items, in three layouts, and a Watch feeds news widget on a fresh install (added once to existing installs). The Bookmarks view has a column with the latest news.

  • New
    JSON Feed, digest and webhooks

    JSON Feed is read next to RSS and Atom; a digest line and the news go to webhooks and the notify target.

  • New
    Statistics

    Stats → Watch feeds shows the numbers with a period switch and the settings; the statistics have a reset route and travel in the backup.

  • New
    Keys

    Shift+N opens the news; # watches the feed of the bookmark in hand. Adding a category by key is gone. Coming back to the tab opens the news only on a computer and only when switched on (off); muted feeds never bring the paper back on their own.

  • New
    Phones

    The news button is desktop only (a phone opens the paper from the toast); the news stripe stands before the favicon.

  • New
    A preview card that leads with the news

    Hovering a bookmark with news now shows the photo, the headline and a short lead first, two equal buttons (Open reader and Open page), and a pager (‹ 1 / 3 ›) when the site has more than one new item; the site's own picture and description no longer sit beside it. Open page now opens that item's own page. The card is about 420 px high instead of 770.

  • Fix
    The news modal follows the theme

    The header, buttons, links, list cards and accent come from the active theme and its material, not from a fixed black and purple. Only the Newspaper view keeps its own paper look. The horizontal scrollbar under the footer is gone, and the footer buttons share one height, border and hover.

  • Fix
    The news list reads right

    A feed item with several paragraphs or list items showed them run together in the list ("…read.The list…"); they now keep their spaces. In Config → Watch feeds a muted row no longer pushes its columns a few pixels out of line.

  • Fix
    :config offers Watch feeds

    The command palette listed every Config section except this one.

  • Fix
    Feeds

    An aborted poll is not a failure; feeds of deleted bookmarks are dropped; an entry dated in the future no longer stays new after an open; pictures come back after a restore. Each feed keeps ten full items, fifty light copies and 75 seen ids.

Phones

  • New
    Notifications and links

    Two settings: Hide notifications and corner cards on phones (on) and Open links in a new tab on phones (off).

  • Fix
    News and picker windows

    have no empty band under the content; the popover keeps under its badge when the page moves and the row's preview card stays away.

Assistant

  • New
    AI Assistant tour

    A guided tour of the panel and its settings.

  • Fix
    Conversations are safe

    A conversation file that failed to read is never saved over; a panic during Apply leaves the proposal failed, not applying; a proposal no longer counts as a lookup.

MCP

  • New
    Queries and counts

    query_bookmarks, query_containers and get_stats, with counts that survive a limit; get_stats, get_app_status and get_bookmark_history report inbox and trash.

  • New
    Settings overview

    A read-only, allowlisted look at the configuration, behind its own switch.

  • Fix
    Safe check errors

    Health view counters and container links that match the view.

What's new

  • New
    A new overview

    Two-column summary, developer card, support bar and counts on the filter chips; the support card also sits beside the release intro.

Themes

  • New
    Tidal Slate (dark)

    is the default theme on new installs, with Tidal Slate (light) as its light half for auto dark mode. Installs that already chose a theme keep it.

  • Fix
    Text fields share one fill

    in the signature themes, and more fields take it (config-input has a style); the news popover follows the material of the theme; in Ink the folio stays put when you hover the header.

  • Fix
    An open category sort menu stays above the next category

    In the Ink and frost looks every category is its own layer, so the category below drew over the menu and took its clicks.

Action bar

  • New
    The hover popover names the button

    With the key chips off, resting on an action button showed only its key (>). It now shows the name first, in your language, then the key: search >, cheat !.

Notices

  • New
    Four hints are toasts now

    The theme studio hint, the Updated from … to … notice, the Inbox extension invitation and the image-update invitation appear as one line in a toast, with no buttons, and say where to go (Shift+A, the ★ button, Config → Containers → Updates). Showing one counts as answered, or snoozed for the two invitations; the switches in Config still turn them off. Corner cards that ask a question stay corner cards.

Reliability

  • Fix
    An unreadable file is never overwritten

    Settings, Secrets, Push (keys and devices), Trash and page order, Glances hosts, the status page token and the status page: when a file cannot be read, nextDash keeps it and does not write defaults over it. Settings are handed out as a copy; a restore holds the settings lock; push keys and chats stay out of the wrong backup; overlapping deletes of one page leave one trash entry.

  • Fix
    Glances

    A dip under the line no longer lowers an open incident's peak, the incident cap never drops an open incident, and a muted alert gives no lost-reading notice.

  • Fix
    Widgets and API

    The last good answer is kept, Docker logs stream from the end, disk and stats are guarded; long API runs answer past 60 s; strings are cut on rune boundaries and NaN sample rates are rejected.

  • Fix
    Config, dashboard, search

    A theme reset sticks, a widget deletes by id, one bulk apply and page save run at a time; preview retries; IME keys, accent-blind picks and finder case in the search; a sturdier modal focus trap and notice queue.

  • Fix
    Health and domains

    Reminders stop after a silent recovery; day summaries are tidier; a known expiry date stays in the report after a failed lookup.

  • Fix
    Extension

    The typed form survives tab changes and stale favicon answers are ignored.

  • Fix
    Bookmarks and Discovery

    A page move that also changes the URL keeps its shortcut; no empty category for an app that cannot be placed.

Docs

  • Docs
    MANUAL.md and README.md

    Watch feeds, the funnel tools and the settings overview are in the manual; the default theme (Tidal Slate), the four toasts and the news-first preview card are corrected in both. The manual has six new pictures (04-preview-card-news, 12-watch-feeds-news, -news-columns, -paper, -config, -stats), the README says 23 MCP tools, and four README dashboard pictures that still showed the removed Fresh block are retaken.

  • Docs
    Sixteen diagrams in the manual

    Hand-drawn SVGs, eleven of them animated, sit beside the text they explain: the install routes (§2), pages, categories and the inbox (§3), the dashboard laid out and numbered (§4), the ways a bookmark comes in (§5), how a check reaches its verdict and the offline guard with the start-up grace (§12), Watch feeds from feed to row, card and window (§12.6), the inbox (§13), how a container finds its bookmark (§14), a custom widget's path to a tile (§15), the layers of a look (§16), the data folder (§19), the extension's capture route (§21), what the write token gates and what nextDash contacts (§23), and a broken but the site works tree (§24). Each follows the light or dark scheme and holds still with reduced motion; they live in screenshots/manual.md/ beside the pictures.

  • Docs
    Config → Help, tips, Overview and News & features

    The Watch feeds panel is rewritten (the news window, the preview card and its pager, Shift + N, #, Config and Stats); four panels name Tidal Slate and the toasts; a Watching feeds tip group has three tips; Overview has two new entries; the cheat sheet has a The news section and its PDF is regenerated.

  • Docs
    static/data/whats-new/v1.24.0.json and its index entry

    , with two highlights; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v360 and DASHBOARD_RELEASE to 2026.11-dashboard-release-v1.24.0, so the window opens once for everyone. go generate refreshed asset_hashes_gen.go.

  • Docs
    Translations

    All of the above, the AI Assistant tour and a few older strings (76 keys per language) are in Dutch, German, French, Spanish and Chinese; the Help panel for Watch feeds still carried its old name in all five and is renamed.

Only docs and tests changed in this release.

October 2026

v1.23.0 An assistant that answers questions about your bookmarks, Health and containers on a model you choose, and proposes changes that wait for your click; the MCP endpoint grows from four tools to seventeen, in four groups you switch on one by one; the theme studio takes the material of the views; the Quick start fits shorter windows; a background save no longer puts back settings changed in another tab. +14 4 fix

An assistant that answers questions about your bookmarks, Health and containers on a model you choose, and proposes changes that wait for your click; the MCP endpoint grows from four tools to seventeen, in four groups you switch on one by one; the theme studio takes the material of the views; the Quick start fits shorter windows; a background save no longer puts back settings changed in another tab.

Assistant

  • New
    Ask in plain words

    :ask in the command palette, or = in the search bar, opens the panel; with a question after it, it starts a new conversation and asks it straight away. A lone = lists the latest conversations (Enter opens one) and what follows :ask or = never reaches the search history or the recents. The panel is laid out like the command palette: the question line on top, conversations on the left, the open one on the right, answers in a small markdown subset (paragraphs, lists, code, links that open a Config page without leaving the dashboard).

  • New
    Claude, OpenAI or a server of your own

    ai_provider.go with an Anthropic and an OpenAI chat adapter; OpenAI-compatible takes a server address and a model, the key is optional and addresses on your own network are allowed. Answers stream; a stream that ends early or sends garbage is an error, not a short answer. Off until Turn the assistant on is ticked, and off in the demo.

  • New
    A key that stays on the server

    ai-secrets.json in the data folder, one key per provider, mode 0600, never sent back: the page only learns whether a key is saved (GET/PUT/DELETE /api/ai/key). It travels in a backup only with Tokens and passwords.

  • New
    It looks things up, and changes nothing by itself

    The tool loop reads through the same tools and group switches as the MCP endpoint and stops after 8 rounds, 20 lookups or two minutes; the partial answer says where it stopped. What it wants to change comes back as proposals under its answer, one row each, with Apply, Skip and Apply all; Apply all skips deletions and container actions. The group is checked again at Apply, with NEXTDASH_WRITE_TOKEN set Apply needs the token, and applied changes carry the source assistant in the activity log. A refused Apply shows the server's message and stays applicable.

  • New
    It knows the manual

    ai_docs.go searches the MANUAL.md and README.md that ship with the install, inside nextDash, so where do I set up the status page? is answered from the manual and sends nothing to the web; main.go embeds both files and .dockerignore lets them through.

  • New
    Conversations kept on the server

    ai-conversations.json: texts, tool names with their sizes, proposals and what became of them, token counts; never the answers of the lookups. The newest 50 for 90 days by default (Conversations to keep, Days to keep them); a file that cannot be read is set aside as .broken, an applying proposal left by a crash becomes failed. Delete one with ×, or all with Delete all (it asks once more; hidden while the list is filtered). They travel in every backup.

  • New
    Config → AI Assistant

    A page of its own in the Services group, with one tab, Settings: Turn it on, Provider, Conversations and What it can see and do, each with an ℹ, a line under Test connection that says what is still missing, and the four MCP switches read-only with an Open MCP access button. The settings are found by Find settings.

  • New
    It looks like the rest

    The panel and the page take the overlay material of the theme and the look (glass blurs, classic does not) through the shared overlay layers, and the answers have their own typography.

  • Fix
    Background saves send only their own keys

    See Settings below.

  • Docs
    Help and tips

    A Assistant tab in Config → Help (five panels) and a tips group of four.

MCP

  • New
    Tool groups

    The endpoint answered four tools; it now has 17 in five tiers: always on (search_bookmarks, get_bookmark, list_tags, list_pages, add_bookmark), and four switches under Data & backups → Webhooks → MCP access, all off: Bookmarks: edit and delete, Health and Inbox: read, Containers: read, Containers: control. The switches can be ticked when either the endpoint or the assistant is on, and tools/list shows only what is switched on.

  • New
    Edit and delete bookmarks

    update_bookmark (name, note, tags), move_bookmark (refused when the target page already holds the URL), delete_bookmark (goes to the Trash through the same path as the UI), create_category and rename_category. They need the write token when one is set.

  • New
    Health and Inbox

    get_health_summary, list_health_issues (down, or a certificate due to expire) and list_inbox, read from the cache; no check is run.

  • New
    Containers

    list_containers, get_container, get_container_logs (needs the write token when one is set; environment variables are never returned) and container_action (start, stop, restart, pause, unpause, remove, update, rollback) behind Containers: control, which also needs NEXTDASH_DOCKER_CONTROL and keeps its long write deadline.

  • New
    Writes through MCP are marked

    The activity log says when a bookmark edit came through MCP.

  • Docs
    Manual §23.6

    lists the tools by group; §23.11 is the assistant.

Theme studio

  • New
    The material of the views

    The studio draws with the same overlay material as the views: glass on a glass theme, solid on classic, with the same border and shadow.

Quick start

  • Fix
    It fits shorter windows

    Head and foot stay put and only the middle scrolls (.sg-mid); the answer about the example links comes first, then weather, bookmarks and the rest to look at as three small cards, with less air on a short window.

Bookmarks

  • Fix
    The preview card stays off the hovered row

    Beside the row it covered what the pointer was on; it goes below it (above near the bottom edge) and stays on screen. Its size is read without the open animation's scale, which made it look narrower than it ends up and the flip miscount.

Settings

  • Fix
    A background save sends only its own keys

    A tip seen, a migration or a search pick posted this tab's whole copy of the settings, so a tab loaded earlier put back whatever had changed since in another tab, through the API or the MCP switches. saveSettings({ keys }) sends only those keys and the server keeps the rest (mergeSettingsFromBody); Config's own save still sends every field. tests/settings-background-saves.spec.js fails without it.

Docs

  • Docs
    MANUAL.md §23.6 and §23.11

    , new pictures (23-assistant-panel, 23-assistant-conversations, 23-assistant-settings, 23-mcp-access) and retaken ones for the Quick start, the command palette, the theme studio and the Config rail; the intro of README and MANUAL says nextDash is more than bookmarks, and README lists the assistant and the 17 MCP tools.

  • Docs
    Config → Help → Assistant, tips, Overview and News & features

    (two entries, the assistant and the MCP groups), the cheat sheet row for = and its PDF.

  • Docs
    Translations

    The assistant's screens, the MCP groups, the cheat sheet row and seventeen older strings (the weekly digest, the tag view's Score, Glances 5) had no locale keys and read in English everywhere; they are in all six languages.

  • Docs
    static/data/whats-new/v1.23.0.json and its index entry

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v359 and DASHBOARD_RELEASE to 2026.10-dashboard-release-v1.23.0. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.22.5 The tag view can show bookmarks with all of its tags, add a tag to a selection, sort by score and remember its sort; the page filter takes several words and opens collapsed categories with a hit; the Recent sheet is two tiles across with the date, a page at a time, from every page. +21 22 fix

The tag view can show bookmarks with all of its tags, add a tag to a selection, sort by score and remember its sort; the page filter takes several words and opens collapsed categories with a hit; the Recent sheet is two tiles across with the date, a page at a time, from every page. The action bar gets an eleventh button for the theme studio and answers the mouse better, every dashboard modal opens in the middle of the window, the edit-mode panel says what is in a block and offers its actions, the Glances Hosts table puts trouble first, and a fresh install starts on Ocean.

Tag view

  • New
    Any or all

    With two or more tags the word between the pills is a switch: "or" shows the bookmarks with any of them, "and" only those with every one. TagViewModel.matches(pool, tags, { mode }); the address carries it as #tag/a+b?all (hashFor, modeFromHash), so a reload or a shared link opens the same view. An "and" view with no matches offers Show any of them.

  • New
    Add tag… on a selection

    The selection bar gets Add tag…: one or more tags (commas) with the tags in use as autocomplete, put on every ticked row on its own page through the same PATCH /api/bookmarks addTags the suggestions use, with its undo.

  • New
    Score sorts

    The Score column header and the sort select sort by health score, highest first; bookmarks not checked yet go last in both directions.

  • New
    The sort is remembered

    per device (nextdash:tag-view-sort), so the view opens on the sort last picked.

  • New
    The search reads the tags, and takes several words

    applyFilters matches name, address, host and tags, and every word must match somewhere, in any order.

  • Fix
    Page sorts in the order of the page tabs

    TagViewModel.sort sorted by page id, so after reordering pages the column agreed with neither the tabs nor the rail; it takes pageOrder now.

  • Fix
    Open in the side panel counts as an open

    It called window.open directly, so opens, Last opened and Recent missed it; it goes through recordBookmarkOpened like the row's link.

  • Fix
    Health is asked again after a failed load

    ensureHealth kept its guard when health.load() returned nothing, so the scores stayed away until a reload.

  • Fix
    The new tag view texts are translated

    The eleven strings of the any/all switch, its hints, Show any of them and the Add tag… dialog were only fallbacks in dashboard-tag-view.js, so they read in English in every language; they are in all six locale files now (dashboard.tagViewAnd, tagViewMode*Hint, tagViewEmptyAll, tagViewShowAny, tagViewAddTag*).

Page filter (Shift + F)

  • New
    Several words

    Every word must match the row, in any order; each is marked in the name.

  • New
    Down and Enter

    ↓ or Enter in the bar puts the keyboard cursor on the first row left; Enter on a query that leaves one bookmark opens it.

  • Fix
    A hit in a collapsed category is shown

    The count included rows inside collapsed categories that stayed folded; such a category opens (grid-filter-open) while the query lasts, without touching its saved state, and its rows count for the keyboard.

  • Fix
    The keyboard cursor skips rows the filter hides

    _isNavigableRow did not know grid-filter-hidden, so j/k could land on a row nobody could see.

Recent bookmarks

  • New
    Two tiles across, with the date

    The Recent sheet (*) is a column of its own, 46rem at most and centred on the header, instead of the page's whole width in three columns. Each bookmark is a tile: a calendar block with the day and month it was last opened, the name and its key, the weekday and time (and how long ago, under a day), its category — or its page's name when it lives on another page — and how often it was opened, with a bar against the most opened. The full date is in the tile's tooltip. Dates follow the app's language (settings.language).

  • New
    Earlier bookmarks, a page at a time

    Ten to a page with a pager in the foot ("11–20 of 34", the page numbers, first and last with a gap between on long histories). ] and PageDown go back, [ and PageUp forward; ← and → still walk the line. Open shown opens the page on screen. Every opening starts on the newest page.

  • New
    Every page's bookmarks

    The sheet reads the current page and allBookmarks (DashboardRecent.recentPool), and asks for the cross-page load when startup skipped it.

  • Fix
    Quieter open buttons

    centred over the pager.

Search

  • Fix
    The search panel looks like the other overlays

    On the Signature style it takes the overlay fill (--ov-fill), so it is as opaque as Recent bookmarks; it used to follow the categories (--palette-fill, their alpha plus a tenth, never under 70%) and read as a thinner veil on glass. On Classic it has the modal's ground, corner and cast. Its results sit on the same slab as the recents list, inset from the panel's edge.

  • Fix
    The modals on the dashboard read in its font

    Recent bookmarks, the bookmark form, the tag cloud, notes, confirmations and the other modals opened on the bookmarks view take --font-family-dashboard (Source Code Pro by default), as the search panel already did. In Config and the other views they stay in Inter.

Glances: Hosts

  • New
    Trouble first

    Until a heading is pressed, the Hosts table lists a host that stopped answering first, then red, yellow and healthy ones, and last what is switched off or has no address; Config's order within each.

  • New
    The headings sort

    as the other Glances tables do (DashboardGlancesTable.build, id hosts); rows without a reading keep their order after the rest.

  • New
    The fullest disk is named

    The mount (diskMount, sent all along and never drawn) stands beside its meter.

  • New
    The last hour of the processor

    is a small line beside its meter: glancesHostRow.cpuHour, the coarse points of the last hour, copied out of the ring (glancesHost.cpuHour).

  • New
    Temperatures follow the weather's unit

    With Fahrenheit picked for the weather, every Glances temperature is written in °F (DashboardGlances.formatTemp/tempNumber); the yellow and red lines stay in Celsius.

Inbox tile

  • Fix
    A link saved elsewhere shows without a reload

    inbox.json and trash.json move the data revision, but the Inbox and Trash tiles kept their cached answer; the revision check clears both and redraws them.

  • Fix
    A snoozed link comes back on the tile when it wakes

    The tile cached the list with the sleeping links already dropped and has no beat of its own; it caches every item, splits waiting from asleep on each draw, and sets one timer for the first to wake.

  • New
    "N asleep"

    A line under the rows counts the snoozed links, so a short tile is not taken for the whole inbox.

Bookmarks view

  • Fix
    The Collection menu is walked with the keys

    It opened with nothing focused and the arrow keys did nothing; the first item takes the focus, and ↑/↓, Home and End move through it.

  • Fix
    Merge duplicates says when there is nothing to merge

    When the report's groups had shrunk to one bookmark each, the action reloaded the list in silence; it says "No duplicates left to merge."

Action bar

  • New
    A theme studio button

    The palette is the eleventh action button and opens the theme studio, as Shift + A does. It sits last in the bar, is switched on and off under Config → Appearance → Action bar → Buttons shown (showThemeStudioButton, on by default, also for old settings files) and with :buttons theme, and stays off a phone layout. maxHeaderActions and :maxactions go to 11.

  • New
    A docked bar answers the mouse better

    It comes back from anywhere along its edge, within 24px of it rather than 6px beside the bar, after the pointer rests there for 150ms, so a quick pass on the way to the Dock or the scrollbar leaves it away; resting on the handle does the same. Leaving the window through the edge beside the bar counts as reaching it. Called by the pointer it goes 700ms after the pointer leaves a 40px margin around it, or 1.5s after it came if the pointer never got there, instead of the full delay; a pointer parked on the edge has to leave it before the bar comes again. A frame now reads the latest pointer position, so a move that left the edge before the frame ran is no longer missed.

  • Fix
    The slide-away setting says what it still decides

    Config → Appearance → Action bar reads "Slide a docked bar away after loading", and its explanation says the delay is for after a load or keyboard use, while a bar called back with the mouse goes shortly after the pointer leaves it whatever is picked (actionBarAutoHideLabel, actionBarAutoHideInfoMessage).

  • Fix
    Every dashboard modal opens in the middle of the window

    The search panel (search, commands, finders, the cheat sheet), Recent bookmarks, the pages panel, what's new and the quick-add omnibox sat above where the bottom dock used to be, or hung from the header (.header-sheet); the tag cloud sat a little above the middle. They are all centred now, with the same 2rem margin above and below. The theme studio stays docked at the side, so the page it previews stays in view. The overlays are 100vw wide instead of 100%, because the stable scrollbar gutter made them a scrollbar narrower than the window and put every modal 5px left of centre.

  • Fix
    The search cursor follows the last typed character

    The prompt row's gap and a margin stood between the text and the blinking _; with text in the prompt the cursor now sits right after it.

  • Fix
    The search panel's side rail is readable

    The scopes you are not in were drawn in the tertiary ink, and a scope the query does not reach dropped to 35% on top of that; they take the secondary ink now and dim to 60%. The scope you are in is never dimmed, even when it has no results yet.

  • Fix
    "tab switches" lines up with the rail

    The hint under the scopes is a row in their grid now: ⇥ under the keys, "switches" under the names. The key is no longer part of the translated string (scopeRailHint became scopeRailHintLabel).

Edit mode

  • New
    The panel says what is in a block and offers its actions

    A category shows its bookmarks, how many were opened this week and how many are broken, with Add bookmark, Move to page… and Delete; a widget its type and what it shows, with Settings…, Move to page… and Delete; a page its categories, bookmarks and widgets, with Add category and Delete page (not on the first page). The buttons do what the block's right-click menu does, with the same question before a delete. The panel's text is a step larger.

  • New
    A width that cannot be chosen says why

    Spreading needs a limit on items per category, at least two columns and a layout that is not locked; the greyed-out choice names the missing one under the field. The one-column message used a key without its dashboard. path and stayed English; it reads in every language now.

  • Fix
    A right-click menu stays open in edit mode

    The right button's auxclick follows its contextmenu; edit mode took it as a click, selected the block, and redrawing the panel closed the menu that had just opened, so a collection's menu (and any block's, after the first) never showed. _handleClick now leaves the right button to the menu.

  • Fix
    The widget settings sheet takes its text colours from the theme

    It hangs on <body>, outside the Config layout that maps the theme's colours onto --text-muted and friends, so its muted text fell back to a fixed grey on light and dark themes alike; .config-widget-overlay gets the same map.

Themes

  • Fix
    The views take the category surface and the glint

    Under the Signature style with the category surface on Open, the Bookmarks, tag, inbox, containers and Glances views drew one plate in the material whatever it was; enamel, paper, velvet, ink and terminal now give their views the category card they draw, and a view's plate catches the same shine as a column.

  • Fix
    A setting changed on another device survives closing the theme studio

    While the studio is open such a change waits; a save from this tab before it was read sent every field back as it was, and put the other device's value back on the server. saveSettings now reads the waiting change first.

  • New
    Ocean is the theme a fresh install starts on

    Ocean [dark], with Ocean [light] for auto dark mode. Existing installs keep their theme; one still to run the v1.22.0 move lands on Aurora Glass as before, so its dialog stays right.

Tests

  • Fix
    Two Docker timeline tests no longer age out

    TestDockerTimelineRecordsEvents and TestContainerNotifierOwnStopSignal recorded their events on 29 September 2026, and the timeline prunes against the wall clock at 30 days, so from 29 October they found an empty timeline. Their clock starts an hour before now.

  • Fix
    :maxactions offers 11

    in edit-mode.spec.js, and whats-new-hidden-release.spec.js expects v1.22.5 to lead the modal.

  • Fix
    Specs follow the action bar and the centred modals

    config-page-templates opens the pages panel with , (a docked bar has slid away), look-migration-notice looks for Open the Theme Studio inside its dialog (the action bar has a button of that name now), header-sheet-reduced-motion measures against the window's centre line, overlay-views lets the five card materials give their view plate a layer (paper's grain), and recents-tiles waits for the search component before it opens recents mode.

  • Fix
    updated-notice keeps the corner for its own card

    The analytics invitation asks for the same corner a second after the Updated card; when it got there first, the Updated card waited behind it and the test timed out. The test answers the analytics question in its setup, and still waits for the notes to load before it closes them.

Only docs and tests changed in this release.

v1.22.4 Edit the dashboard in place, search that learns your hours, a checkup for what needs tidying, a reworked weekly digest and a guided way to add widgets. +18 5 fix Read the post

Edit the dashboard in place, search that learns your hours, a checkup for what needs tidying, a reworked weekly digest and a guided way to add widgets. Every release held back from the What's new window since v1.20.2 (hideFromModal) is shown in it now, and nothing is flagged any more.

Edit mode

  • New
    Edit mode

    DashboardEditMode is switched on by Shift + M when no bookmark row is selected (with a row selected the bookmark's own Shift + M, Move, still answers), by the pencil in the action bar, by :edit mode, or by Edit in panel… in the category and widget menus. While it is on a bar says so, a click selects a block instead of opening a bookmark, the grid's bare letters, arrows and Enter are taken, the preview card stays away and comes back after, and Esc leaves from the inside out (dialog, panel field, mode). Desktop only; a phone layout ends it. The pure key rules are in edit-mode-model.js.

  • New
    The panel

    DashboardEditModePanel is a ListViewDrawer docked at the right like the views' panels, and the grid gives way with padding-right. A category: name, icon, width, view, sorting; a page: name, emoji, colour; a widget: name, width, state, and Settings…. Every change is saved as it is made; Esc in a text field gives the old text back; a category deleted elsewhere clears the panel; a save reloads the page first when d.categories no longer matches the server.

  • New
    A widget's sheet over the dashboard

    openWidgetSheetOverDashboard opens the Config → Widgets sheet on the dashboard, restores Config's page filter, search and drafts when it closes, and counts as a modal for the dashboard's keys. The sheet joined the overlay theming, so it is drawn like the other dialogs in every theme, in Config as well.

  • New
    The pencil is the tenth action button

    showEditModeButton (on by default, also for old settings files), maxHeaderActions goes to 10, :maxactions offers 10, and the button carries its key for screen readers.

  • New
    A click on a block's title chooses the block and leaves it as it is

    In the mode the capture handler stops the title's own click, which would otherwise fold the block and save that.

  • New
    The edit-mode button explains itself

    under Config → Appearance → Action bar (showEditModeButtonInfoTitle and showEditModeButtonInfoMessage in six languages), which tests/config-info-reset.spec.js asks of every setting with a default.

  • New
    A corner card

    introduces edit mode and Shift + M, once, no sooner than three minutes after the latest corner card (minGapAfterCardMs in NoticeCard, kept across loads), and the dashboard tour has a step for it.

Search

  • New
    Usually now

    search-usually-now.js ranks bookmarks by opens within ±1.5 hours of the current time, on the same kind of day, over eight weeks (at least three), from each bookmark's openLog; it is the first group of the empty panel.

  • New
    Actions on a result

    → unfolds open, open in a new tab, edit, copy address, show in the list and move under a bookmark result; ← or Esc folds them. Enter chords fold the open actions in the phone's input.

Checkup

  • New
    :checkup

    checkup.js and checkup_structure.go walk dead links, duplicates, never-opened and stale bookmarks, empty categories and pages, and widgets that report an error, reusing the Bookmarks view's actions. dashboard-widget-state.js lets a widget report how it is doing. Deleting a category from the checkup, the menu or the panel goes through one finishCategoryDelete.

  • Fix
    A page of uncategorised bookmarks is not an empty page

    findEmptyStructure counted a page with no categories and no widgets as empty, bookmarks or not, so the checkup offered to delete a page that still held links.

Weekly digest

  • New
    Reworked

    The digest is always on: the Config switch is gone and an old file that had it off is read as on. The window has a list of parts in three groups (Needs you, Tidy up, Good to know) beside a detail, with Close always in view; the corner card has Read the digest, Snooze 1 day and Got it with two reminders; the bar asks before it closes; a fresh install gets its first digest after at least seven days; not opened counts 30 days; and the checkup is a part of it.

  • New
    The week in figures

    A row of figures along the top of the window: bookmarks opened, bookmarks added, uptime with its outages, and the Inbox with how many links are new, each next to the seven days before with ▲ or ▼ (green when it went the better way). digestWeek in the snapshot counts opens from each bookmark's openLog, added from createdAt (the unsorted page left out), uptime pooled over the check history without maintenance samples, and outages from the samples that raised an alert; it follows the digest's own switches, and a figure with nothing behind it is left out of the snapshot and the window.

  • New
    An Overview, and detail behind every name

    The window opens on an Overview with one line per part saying where it stands, each a way into that part. A broken link shows its page, since when it is down and the last check's message (brokenItems); the most opened show their counts (topOpenedItems); never opened shows the page (neverOpenedItems); not opened lately shows how long ago, longest first (staleItems); the Inbox says how long its oldest link has waited (inboxOldestDays). A snapshot from before keeps its chips. Covered by tests/digest-window.spec.js and the TestDigestWeek* and TestDigest*Items* tests.

  • Fix
    Not opened lately leaves out a bookmark whose stale is ignored

    The count now comes from the bookmarks rather than the Health report, and skipped the ignore the report applies.

Widgets

  • New
    The wizard

    One list of widgets, connect and test an address or key before a media widget is added, a page picker for the add, and the old catalogue and Custom links open the same guide. The tour and manual describe it.

  • New
    Three sections in every widget's settings

    (what it shows, how it connects, where it sits). A section's default is stamped so only a real toggle is remembered, working inside a section pins it, and a media widget that fails to connect opens Connection and says so on its title.

  • New
    One card per widget

    in Config → Widgets with kind, state and page.

  • Fix
    Widget cards keep their surface in flat themes

Config

  • New
    Finders is a section of its own

    , and Fresh moves from Behavior to Bookmarks.

  • New
    The demo has a Glances host that answers in-process

    ("Tower").

  • Fix
    The demo starts in a fraction of the time

    capPoints in glances_history.go copied a whole history ring on every point, so seeding the Tower's seven days cost seconds of CPU at every start and every reset of the public demo, and more than thirty on a busy CI runner, where it timed out the demo server of tests/demo-analytics.spec.js. It reslices now: 4.0 s becomes 0.3 s on one CPU.

Inbox

  • Fix
    Icons the outbound limit refused are fetched again

    The startup icon backfill stamped a link as tried when the limit turned the request away, so on an Inbox larger than the limit the rest never got an icon. It now leaves those unstamped, as the add path already did.

Docs

  • Docs
    static/data/whats-new/v1.22.4.json and its index entry

    ; whats-new-stub.js moved to DASHBOARD_RELEASE v1.22.4 and whats-new-v357. hideFromModal is removed from every entry of the index, and tests/whats-new-hidden-release.spec.js now expects an empty list and every earlier release in the modal.

  • Docs
    Config → Help

    (edit mode panel; digest, search, keyboard, header and health texts), Tips, Overview and About → News & features (four entries), the cheat sheet with its PDF regenerated, MANUAL.md, and the six locale files.

  • Docs
    README.md and MANUAL.md

    describe edit mode, Usually now with result actions, the checkup and the weekly digest with its figures and Overview, with new shots (nextdash-edit-mode.jpg, nextdash-digest.jpg, 04-edit-mode*.jpg, 08-search-*.jpg, 12-checkup.jpg, 12-weekly-digest.jpg); every README shot that shows the action bar is retaken with the pencil as its tenth button.

  • Docs
    Help and the manual say which switch the digest's figures follow

    uptime and outages stay with the broken links, while the opens, the added bookmarks and the Inbox go with Include most opened, unused and Inbox, in six languages (helpDigestBody).

  • Docs
    Texts say "action bar" for the pencil

    (it is not in the header) and the digest's own group names, Needs you, Tidy up and Good to know, in Help, the manual, the What's new item and the five translations; two Dutch checkup labels are translated.

Only docs and tests changed in this release.

v1.22.3 A new install starts better and the quiet features get found: the Quick start guide asks first whether to keep the example links, offers ready-made pages and a CSV import, and walks through ten steps; there are tours for the keyboard, Monitoring and Unraid; tips can come weekly; four offer cards ask before doing something, and Config's settings search remembers what you opened. +24 16 fix Read the post

A new install starts better and the quiet features get found: the Quick start guide asks first whether to keep the example links, offers ready-made pages and a CSV import, and walks through ten steps; there are tours for the keyboard, Monitoring and Unraid; tips can come weekly; four offer cards ask before doing something, and Config's settings search remembers what you opened. The usage analytics send less and carry what was missing to read them: an install code, a hostname replaced by one word, the language, how the server runs, and a handful of small events. Everything analytics stays behind the opt-in: with Privacy-friendly analytics off, nothing here is in the page and nothing is sent. Held back from the What's new window.

First start

  • New
    the Quick start guide asks before it does

    It opens as Welcome to nextDash in two columns. First you choose between Keep these example links and Start with an empty page; the ready-made pages (Homelab, Media server, Developer) stay locked until you have, because where they go depends on it: beside the examples as a new page, or onto the emptied main page (target on POST /api/onboarding/template, and platform on GET /api/page-templates/bundled). A weather town, a language list with a hint when the browser asks for another language, a button to the manual at nextdash.cc and a note that nextDash can feel like a lot are in the same window.

  • New
    import a CSV file from the guide

    One button in the guide, a link to Config → Data & backups for the other importers, and the usual question where the links go.

  • New
    import to a new page

    The destination question for CSV and browser-bookmark files has a third answer, On a new page: Imported, Imported 2 and so on. The dialog is styled outside Config too (it was an unstyled list).

  • New
    ten steps, three at a time

    Take the 1-minute tour, Open the Bookmarks view, Browse by tag, Open the Inbox view, Add a widget, Turn on status checks, Set up notifications, Open the Config settings, Learn the shortcuts and Add a second page, plus Connect your Unraid server on an Unraid server. The rest is behind Show more. The old import and extension steps are gone.

  • New
    a tip after a ready-made page

    A short popover says how to edit, delete and add a bookmark and that Checking can be set to Monitor per bookmark (the Bookmarks view shows when one is down). Nothing is monitored by itself.

  • New
    an example tag cloud, once

    Browse by tag in a library without tags shows ten made-up words and a way to the Tags view, one time. Closing the example offers Open Tags view, and the step counts only once you have taken it.

  • Fix
    the guide opens again on an empty data folder

    A browser that had seen it kept a flag in local storage and never opened it after the data was cleared; the flag is now tied to firstRunAt.

  • Fix
    the bar stays on every page

    The Quick start bar is in view on the other pages as well.

Tours and tips

  • New
    a keyboard tour

    Four steps: typing anywhere, : for commands, ? for finders, and /, *, !. It never opens by itself: the search panel's empty state offers it until it has been seen (open for people on Hypr mode), :tour keyboard and Config → Help → Guided tours start it.

  • New
    Config tours for Monitoring and Unraid

    A Tour button on the band of each, in the same slot as the other tabs, and a one-time tour on the first visit. Monitoring explains that checking is chosen per bookmark; Unraid covers connecting, the widgets and staying read-only.

  • New
    the dashboard tour has a step for the mouse

    Nine steps now; the new third one covers the right-click menu of a bookmark and the other things you can do with the mouse, where the tour only had keys.

  • New
    keyboard tips come daily or weekly, and section tours have a switch

    Keyboard tips come and Offer a tour the first time a section opens sit in Config → Behavior → Onboarding (sessionTipsFrequency, enableSectionTours, default on). Tours still need Show occasional keyboard tips to be on.

  • New
    the settings search remembers

    With an empty search, Recent lists the last eight settings you opened or changed, kept in this browser only.

Offers

  • New
    Check images for updates? in the Containers view

    A card after the third open, with Turn on (daily), Not now and Never. Nothing updates by itself.

  • New
    Re-check your links? in the Bookmarks view

    When the last real check is old, the age counts from that check, and a second card offers to turn the automatic re-check on. The Config text now says it is on by default.

  • New
    the browser extension in the Inbox

    A card and a line in the empty Inbox, both linking to the browser-extension page of the docs.

  • New
    What changed after an update

    Says which version you came from, and does not hold the other cards back.

  • New
    tags for one category

    Find tags on a category's menu, and in Config's category menu.

  • New
    a switch for each

    Config → Behavior → Onboarding has one for each offer (enableDockerUpdateNotice, enableHealthRecheckNotice, enableInboxExtensionNotice, enableUpdatedNotice). The notice cards can belong to one view (view on NoticeCard.define), and a card marked essential does not make the others wait.

Privacy & sync

  • New
    an install code on the settings snapshot

    analytics_identity.go hashes the install-id file with its own purpose (usage-analytics: + id, first 16 hex characters of the SHA-256), so it cannot be matched to the daily install count, and puts it on the script tag as data-install. It follows the analytics switch, is empty in the demo, and the file is not even read while analytics is off (TestAnalyticsInstallRefNotCollectedWhenDisabled). Umami's own visitor id rotates monthly and differs per browser, which made retention and release uptake unmeasurable. Once the tracker has loaded the code is also passed to umami.identify, so Umami stores it as the session's distinct_id and the sessions of one install stay together past the monthly id, as the daily install count's do; Umami records no event for it.

  • New
    hostname, referrer and page title no longer leave

    Outside the demo the tracker gets a data-before-send hook (nextdashBeforeSend) that replaces the hostname by localhost, lan or domain, empties the referrer and sets the title to nextDash. The settings snapshot carries the same word as exposure, plus distribution (docker, unraid or other, from /.dockerenv and HOST_OS) and language.

  • New
    app-updated, first-bookmark, app-error

    The minor release a browser moved from and to (never on the first visit), the time from first visit to first bookmark as a band for an install that started with ten bookmarks or fewer, and a failure as a kind plus the view name, never the message, at most three per page load and only from scripts of the app's own origin.

  • New
    bookmark-created says where it came from

    source: new-modal for the New bookmark dialog and inline-form for the category form, on the result: ok event.

  • Fix
    snapshots go out when they change

    A snapshot per page load was 55% of all events and about 700,000 stored properties in a hundred days, enough to make Umami's own Events page fail. Each of the five now goes out the first time, when its payload (which holds the release) changed, in a new calendar month, or after seven days; what was sent is kept in local storage (nextdash.analytics) and only written once the tracker has loaded. Constant fields (eleven settings, two for Containers, fifteen for the views) and widget types nobody has are left out.

  • Fix
    one pageview per page load

    Umami hooks history.pushState and replaceState and counted every in-app view change as a pageview, which made pageviews and the bounce rate meaningless. data-auto-track is off and the load is reported once with the path only.

  • Fix
    a loop cannot flood the data

    nextdashTrack drops an identical event within 500 ms and caps the rest at 100 per rolling minute; the snapshots are exempt from the cap. One day had 2,575 pageviews from 21 visitors.

  • New
    events for the new features

    start-guide:open, :close, :step, :finish and :link with fixed words and a band for how many steps were done, start-template, start-import, language-suggest, keyboard-tour, monitoring-tutorial and unraid-tutorial (shown, opened, finished with an outcome), docker-update-offer, health-recheck-offer, updated-notice, config:settings-search (recent, typed or browse), whats-new:closed, bookmark:edit-close and bookmark:edit-invalid. modal:commands and modal:finders say whether a key, a button or a tab opened them, and modal:tag-cloud whether it was the example. No free text and no exact numbers.

  • New
    more on the snapshots

    The share of bookmarks without tags as a band, and the smart collections and tag collections in use. demo:refused is capped at five per action per visit.

  • Fix
    first-bookmark fires on a default install

    The seed carries about a hundred example links, so the ten-link rule never matched; an install that is less than a day old now counts as fresh.

  • Fix
    bookmark-created counts the bookmark once it is saved

    It also fired when the form was refused or the server said no, on top of the saved event.

  • New
    NEXTDASH_DISABLE_INSTALL_PING=1

    Switches off the daily install count alone, where DISABLE_TELEMETRY also takes the analytics away. Test runs and CI shards start a server on an empty data folder, which counted as a new install each time and made up most of the count.

Config

  • Fix
    the title stays clear of the buttons, and the band is one height

    In a material that sets titles in capitals with wide letter-spacing (brushed), the title ran into Only changed, because the band's buttons did not shrink and the title block could shrink to nothing. The title keeps its own width (min-content, on one line, mark and word together), the buttons give way (count first, then the filter), and the description is one line with an ellipsis, so the band is 67px high on every tab and the rail does not move as you go down it.

  • Fix
    Config → Monitoring fits a phone

    The filter and the tour slot made the band 385px wide; below 640px they wrap and shrink.

  • Fix
    monitoring texts point at the Bookmarks view

    Three Config texts said Health view, in all six languages.

  • Fix
    the band's line is one line in every section

    The description under a section's title could wrap to a second line, which made the sticky band sixteen pixels taller in Inbox, Appearance and Behavior than in Bookmarks and moved everything under it when you went from one tab to another. .config-view-head.lvs-description is now nowrap with an ellipsis (the whole sentence is still its title), and the Inbox, Appearance and Behavior lines are shorter in all six languages so that they fit in the 400px the filter leaves them.

Security

  • Fix
    golang.org/x/net v0.62.0

    GO-2026-6860: the HTML parser took quadratic time when it coalesced text nodes, and importing a bookmark file reaches it (ParseNetscapeBookmarks). govulncheck reports nothing after the update.

Appearance

  • Fix
    the docked action bar stands apart from the cards

    It took the paint of a category and was lost against the cards it slid over. A layer of the surface colour now goes over the material's own paint (about 38% on a glass theme, more where the theme itself is opaque, from --cat-glass-alpha), with an edge that leans to the accent and a cast in a filter, so each material's own edge stays. A button that is on is filled with the accent, as the lit view in the header is. Ink keeps its thin plate.

  • Fix
    the command palette looks like the dashboard

    Its fill follows how solid the categories are (their alpha plus a tenth, never under 70%) instead of the overlay's 80%, it starts with the two skewed blocks of a column head, and its mode word is set as a column head is in that material. The ring and the cast stay. Neon, terminal, ink and paper keep their own fill.

  • Fix
    Pages and Recents rise like the other dialogs

    The two sheets had their own drop; they now use the rise of the add-bookmark form and the search panel.

  • Fix
    tour dots keep their size in Signature materials

    The rule for a dot also matched the row of dots and made it eight pixels square.

Tests

  • New
    specs for what is above

    The guide's choice and steps, the import destination, the tag step, the three tours, tip frequency, Recent in the settings search, the dock and the palette, the Config band and the Monitoring page at 360px, the tour dots, and bookmark-created on a refused save. Falsified where the change is behaviour.

  • New
    analytics-snapshot-gate.test.cjs and analytics-pageview-rate.test.cjs

    The gate (changed, month, week, release, a tracker that never loaded), the three small events, the install code, the hostname words and the rate limiter, against a fake storage and clock. analytics-count-buckets.test.cjs skips the tracker's own pageview call.

  • Fix
    the analytics specs read the snapshots again

    They clear the remembered snapshots before each load, the stubs ignore the tracker's pageview call, and the widgets spec no longer expects a type the fixture does not have. NEXTDASH_DISABLE_INSTALL_PING is in the e2e server's environment and in the CI step.

Docs

  • Docs
    Help, Tips, MANUAL and README for the above

    The Config → Help panels for the guide, import, tips and offers, the tips Config tour list and find a value, seven new manual pictures (Quick start, the example cloud, the keyboard tour, the Monitoring tour, Recent in the settings search, the tips settings) and the chapters they sit in. 228 new and changed strings are translated in Dutch, German, French, Chinese and Spanish.

  • Docs
    MANUAL.md §23.7 and §23.8

    (the table, how often, the install code, where it runs, the environment variable), the README's variable table and its privacy line, Config → Help → Statistics → Privacy & analytics, and the three privacy strings in the six locale files.

  • Docs
    static/data/whats-new/v1.22.3.json and its index entry

    , held back from the What's new window; NEXTDASH_WHATS_NEW_DATA_VERSION in whats-new-stub.js moved to whats-new-v355 and DASHBOARD_RELEASE stays on v1.22.0. tests/whats-new-hidden-release.spec.js follows. go generate refreshed asset_hashes_gen.go.

  • Docs
    new screenshots

    The manual's pictures are retaken in Arctic Cyan dark and the README's in their own themes.

Only docs and tests changed in this release.

v1.22.2 The action bar, the five views and Config are drawn like a category under every Signature material, instead of as the dialog plate of that material, and the blocks on Config lie on their pane as a light tint instead of a box of their own colour — held back from the What's new window (hideFromModal) like v1.22.1, so v1.22.0 keeps leading it. 5 fix Read the post

The action bar, the five views and Config are drawn like a category under every Signature material, instead of as the dialog plate of that material, and the blocks on Config lie on their pane as a light tint instead of a box of their own colour — held back from the What's new window (hideFromModal) like v1.22.1, so v1.22.0 keeps leading it.

Appearance

  • Fix
    the action bar draws like a category

    Out of the header, the bar was a plate in the material of a dialog: an accent bar on the edge, a mark on top and the shine of the overlay. Under Category surface glass or card it now draws the ruit or card of a category with the same hairline, sheen, cast and radius, and under a Signature material it takes the paint of that material's category rule. What a category sets for its own layout (position, padding) is reset for the dock. Ink keeps a thin plate, since a bare row of icons has nothing to tell it apart from the bookmarks. Under open the dock keeps the plate of the overlay.

  • Fix
    the views draw like a category

    Bookmarks, Inbox, Containers, Glances and Tags carried the overlay plate (shine, edge, cast); under every Signature material they now take the fill, edge, shadow and blur of that material's category, including --surface-sheen for terminal and ink. The overlay plate stays under open.

  • Fix
    Config draws like a category

    The same for the Config view itself; the panels, widgets, tiles and update bar on it take the corner of the material.

  • Fix
    the blocks of Config lie on the pane as a tint

    Under Signature a block lay on the small fill of the material (--ov-fill-small, 96% on glass), which read as a box of its own colour. Under every surface but open it now takes what Classic gives it: 35% of the surface colour with a hairline, and a 4% tint on a card surface.

  • Fix
    the cards on those views take the corners of the material

    The summary card and the Glances, Docker, tag and Inbox cards use the radius of the material's category, up to 14px.

Tests

  • Fix
    the config pane spec expects the pane of a category

    config-panes.spec.js asked for a fill that is neither clear nor solid under Signature; Aurora's category lets the backdrop supply the colour, so the Config view now does too, and the spec asks for the blur and a fill below 1.

  • Fix
    CI

    Weighted shards, balanced on what each spec file costs, and per-spec timings (scripts/slow-specs.cjs); the Playwright image was tried and left again.

Docs

  • Docs
    static/data/whats-new/v1.22.2.json and its index entry

    , held back from the What's new window; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v354. go generate refreshed asset_hashes_gen.go. tests/whats-new-hidden-release.spec.js lists v1.22.2 as held back.

Only docs and tests changed in this release.

v1.22.1 Glances 5 is recognised and named as not supported yet, instead of being taken for Glances 3, and the icon in front of a bookmark opens it, like the name beside it. +5 5 fix Read the post

Glances 5 is recognised and named as not supported yet, instead of being taken for Glances 3, and the icon in front of a bookmark opens it, like the name beside it.

Dashboard

  • Fix
    a click on a bookmark's icon opens the bookmark

    The icon sat in the row's lead, next to the link rather than inside it, so a click on it went nowhere. populateBookmarkRowView now makes the icon slot an anchor of its own, with the name's sanitised href, target and rel, out of the tab order and hidden from assistive tech. The grid's delegated click and auxclick listeners take it as the name, so a plain click, Cmd/Ctrl+click, middle click and Alt/Shift+click for selection behave the same and the open is recorded. A long press on the icon blocks the click that ends it, as on the name. A mouse press on the icon hands focus to the name once the button is up, not before: moving focus during the press cancelled the row's drag. The icon gets a pointer cursor, and the default one while a selection is open. Covered by tests/bookmark-icon-opens-link.spec.js; every test but the drag one fails without the fix.

Glances

  • Fix
    a Glances 5 server is no longer called version 3

    Glances 5 (5.0.0b1, beta) serves its API under /api/5 with a new data model, so /api/4/status answers 404 and nextDash said the server answered like version 3. glancesGet in glances_client.go now asks /api/5/status when that happens; if it answers, the error is Glances 5 not supported, and Config and the Glances view say that Glances 5 is not supported yet and that Glances 4 is needed. Reading Glances 5 itself waits until 5.0 is stable. TestGlancesConnect covers it; it fails without the fix.

  • Fix
    the key legend sits inside its panel

    Under a Signature material the key legend at the foot of the Glances view (and the Inbox's) is drawn as a plate, but it kept only the top padding of its old rule, so the keys sat on its bottom edge. theme-overlays.css gives it room on every side.

  • Fix
    a refresh no longer throws a scrolled Safari reader to the top of the Glances page

    Every beat redraws the open section, and in WebKit that redraw moved the scroll to the top, so a reader half-way down the page had to scroll back every few seconds; Chromium kept the place. _drawSection() in dashboard-glances.js reads the scroll position before the redraw and puts it back in the same task, as the Containers view does since v1.21.3. tests/glances-redraw-scroll.spec.js moves the page to the top half-way through a redraw, as WebKit did; it fails without the fix.

Weekly digest

  • New
    a clearer digest window

    Four counts across the top (broken links, what runs out within 30 days, container updates, never opened) that count up and each open their view; under them the parts in two columns with a coloured dot, so a full week fits without scrolling. Certificates and domains are bars of days left, nearest first; domains more than 200 days out become a count. A part you opened gets a tick and dims, and so does its tile.

  • New
    :digest and an overview panel

    The command palette opens the latest digest with :digest, and Config's overview has a Weekly digest panel with the parts still to open, the counts and the date; Read opens the same window. Covered by tests/digest-notice.spec.js.

Health

  • New
    an Uptime badge section on a monitored bookmark's Health tab

    A preview of the badge, a choice of 7 or 30 days and two buttons, Copy Markdown and Copy HTML, that put the snippet for this server on the clipboard. While Serve uptime badges is off the section says so and has a button to the switch; a bookmark that is not monitored has no section, since the route answers no data for it. Covered by tests/bookmarks-health-badge.spec.js.

Widgets

  • New
    Retry all on the Feeds widget

    With more than one stopped feed the tile offers Retry all N, which asks the server to try every stopped feed again now (POST /api/feeds/retry with no address) instead of one click per row.

Config

  • New
    the corner cards list is complete

    Behavior → Privacy & sync → Onboarding now lists the install count, the weekly digest and analytics next to the other cards, each with Answered or Not shown yet and Show again. Analytics keeps its answer in the settings, so its row reads them and a reset writes them back; someone who turned analytics on has nothing to be asked again. Covered by tests/config-notice-cards.spec.js.

  • Fix
    the cheat sheet listed :digest twice

    and had no English string for it; the registry check failed on both.

Tests

  • Fix
    the Glances entrance spec no longer fails on a busy runner

    It asked every block to rise once the entrance window was open when the blocks were drawn, but a block waits up to about 200 ms for its turn and a rise that has not started when the window closes is dropped with it. On a runner under load the window closes inside that wait: the page behaves, the spec failed (the same spec failed on the base of v1.22.0 under a 5x CPU throttle). It now measures how long the window stayed open after the blocks arrived and asks for the rise only when that was longer than 300 ms.

Docs

  • Docs
    the manual, the six languages and static/data/whats-new/v1.22.1.json

    The manual names the badge section, Retry all and the full list of corner cards; nl, de, fr, es and zh carry the new strings; the release is held back from the What's new window (hideFromModal) like v1.21.2 and v1.21.3, so v1.22.0 keeps leading it. whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v353. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.22.0 A new look. Every material now has a surface of its own, drawn through cards, headers, menus, dialogs and the side panel, and the themes were redrawn with it. +23 45 fix Read the post

A new look. Every material now has a surface of its own, drawn through cards, headers, menus, dialogs and the side panel, and the themes were redrawn with it. New backdrops and patterns fit each theme. Aurora Glass is the default theme, and every existing install moves onto it once, with a dialog that offers the way back. Next to it: a Classic ThinkDashboard theme, a redesigned cheat sheet, a two-column bookmark form with a live preview, and a round of fixes in Config, the dashboard and Glances.

Look

  • New
    signature material style

    Each of the twelve materials (glass, paper, enamel, brushed metal, neon, ink, terminal and the rest) draws its own surface, category header and widget header, and every header keeps the //. Paper columns read as an index card, enamel as a glazed tile, neon with a glowing top edge, brushed metal and glass with a shine per column. Theme Studio → Surface → Material style keeps Classic as a choice for the flat, old look.

  • New
    Aurora Glass is the default theme

    A fresh install starts on Aurora Glass, on the dark or light half.

  • New
    every install moves onto Aurora Glass once

    The themes were redrawn for the new look, so keeping the old drawing beside it would mean two of everything. The move keeps the dark or light half you were on, and lookMigration remembers the theme you had. Bookmarks, categories, settings and own themes stay as they were. Covered by aurora_glass_migration_test.go.

  • New
    a dialog explains the move

    It shows the theme you had next to the one you have now, offers Go back to {theme} and Open the Theme Studio, and appears once, before any corner card. Opening the studio from it waits for the studio to load first.

  • New
    backdrops chosen per theme

    Each material has a pool of its own and each theme picks from it. Eighteen patterns replace the colour washes, with new recipes such as haze, veil, spotlight, silk, caustics, dawn, linen, dotgrid, ruled and grain, a blue sea for Ocean, bricks for Concrete, a small honeycomb for Bokeh, and rack and terminal backdrops for the four Unraid themes. Hexagons, chevron, prism, sunset, dunes, mountains and blueprint are drawn finer and the loud ones calmed. Every recipe carries the colour of its theme; a dark page carries more of it.

  • New
    a quiet centre

    A Quiet centre slider fades the backdrop behind the bookmarks. It is kept per theme, with the install-wide value as the fallback.

  • New
    neutrals on one ladder

    The eight neutral themes (Neutral, Stone, Gray, Zinc, Slate, Chalk, Concrete, Black) sit on one lightness ladder, each with a material and a backdrop of its own. Accent of the neutrals picks one of six colours for all of them, or the theme's own. Covered by tests/neutral-accent.spec.js.

  • New
    ThinkDashboard Classic

    The ThinkDashboard theme from v1.0.0 returns with its colours and grid of dots; the current one is now ThinkDashboard Modern. Covered by tests/theme-thinkdashboard-classic.spec.js.

  • New
    Unraid themes redrawn

    Card panels and server colours, a calmer band, and old Unraid copies move to the new card drawing.

  • New
    Gloss Chrome and Gloss Amber on glass

    , like the other lacquer themes; Gloss Chrome keeps its plain grey band. 65 dark themes move to colour recipes and textures get their colour back.

  • Fix
    the Theme Studio keeps your place

    A picked backdrop keeps the focus and the scroll; theme card names keep their width beside the pills.

  • Removed
    the Berry, theme browser and clock and weather corner cards

    Berry is no longer the default, and the dialog above covers the new look.

Overlays

  • New
    overlays, views and Config take the look of the material

    , with four levels of elevation. Layers take the light of their material, ink layers carry a bar on the top edge, neon layers glow, and small layers are closed per material.

  • New
    the action bar is a handle on the screen edge

    , in the surface of the material, with the mark of the head and hairlines between the groups.

  • New
    the cheat sheet has a search field

    , topics in columns, and a dock that shows the keys of the row you pick and follows focus. Rows carry their keys for screen readers, and focus looks different from selected. Cards stay whole in Safari.

  • New
    add and edit bookmark in two columns with a live preview

    Two columns only with a fine pointer, tab order runs down each column, and the label is not read twice. The icon picker opens in the page, so the form no longer clips it.

  • New
    the preview card shows the picture on the left

    ; cards without a scrim get a closed fill.

  • New
    Save this link, What's New, views and Config lie on the surface of the material

    : address, preview, choices, blocks, chips, summaries, cards, controls and table heads.

  • New
    the popover arrow points at the control that was pressed

    , follows it when hidden and shown, and clears when the popover hides.

  • Fix
    layers respect your settings

    Reduced transparency closes them, effects off is flat, animations off stays off, and the toast and preview have no blur. Shadows follow the light of the page.

  • Fix
    bookmark rows take one inset from one variable

    , so icons line up with and without a ping and each layout keeps its own padding.

  • Fix
    selects, lists and tutorial dots stay readable on the layers

    ; the active tutorial dot is lit, and quick add and the palette show their focus.

  • Fix
    the Bookmarks view has no second blur layer under the plate

    , and its rail is lit like the other views. The Config bookmarks preview scrolls with the page.

Keyboard

  • New
    Shift+G opens Glances from every view

    In lists, the last row is now End instead of G.

Config

  • Fix
    the Config band keeps filter and count in the same place on every tab
  • Fix
    taking a tag off a bookmark no longer undoes a settings save

    refuseRemovedTags read the settings, added the refusal and wrote them all back without settingsMu, so a Config save landing in between was lost or put back. It now holds the same lock as SaveSettings. TestRefusalWaitsForTheSettingsLock fails without it.

  • Fix
    POST /api/pages refuses a page id below 1

    A 0 or a negative id was written as bookmarks-0.json, which no page list reads back, and stayed in pages.json. Now 400 Invalid page ID. Covered by TestSavePagesRefusesAnIDBelowOne.

  • Fix
    a page delete that fails no longer leaves a trash entry

    DeletePage trashes the page before removing its file; when the removal failed, the entry stayed as a copy of a live page whose Restore answered 409. The entry is now taken back out. Covered by TestDeletePageThatFailsLeavesNoTrashEntry.

  • Fix
    a duplicate whose categories fail leaves no empty page behind

    duplicatePage saved the copy first and, when the categories write failed, showed "Could not duplicate this page" over a page that did exist; a retry made a second one. discardDuplicatedPage deletes the copy and drops its trash entry.

  • Fix
    a category deleted on another device stays deleted

    The categories editor sends the whole list, and addCategoriesMadeElsewhere only added what was new on the server, so the next edit here put a category deleted elsewhere back. _catOnServer remembers what the server last had; a category gone from it since leaves the list too.

  • Fix
    category saves for one page go out one at a time

    Two quick toggles sent two whole lists at once and the older could land last, so the server kept the first click while the button showed the second. saveCategories now queues per page. The last three are covered by tests/config-structure-review-fixes.spec.js, each failing without its fix.

  • Fix
    a settings save that leaves keys out of the backdrop tuning keeps their defaults

    SaveSettings decoded a missing calm, scale or brightness as 0 and clamped it, so a tab still running the page from before the quiet centre stored no quiet centre at all. It now fills the absent keys as a settings file does (fillMissingBackdropTuning); an explicit 0 stays. Covered by TestSaveSettingsFillsMissingBackdropTuning.

  • Fix
    restoring a backup with many local captures no longer runs the server out of memory

    stagedFilesFromZipReader read every capture under archives/ into memory before the restore applied, and captures are left out of the 1 GB total, so a backup with a few hundred of them needed gigabytes of RAM. A capture is now copied out of the archive when the staging directory is written, one at a time, and still held to the 64 MB entry limit there. Covered by TestRestoreReadsCapturesWhenWritingThem and TestRestoreHoldsCapturesToTheEntryLimit; the first fails without it.

  • New
    Overview → New in nextDash lists the features since v1.20.3

    Eleven items, newest first: every theme redrawn, 75 backdrops and the quiet centre, Signature or Classic, the neutrals with one accent and ThinkDashboard Classic, the searchable cheat sheet, the two-column bookmark form, the Glances page, widget and insights, domain expiry and Add new bookmark in a category menu. Each has a button to where it lives. The texts are in static/data/overview-features.json and the 55 keys under config.overviewNewFeature* in all six languages. v1.21.2 and v1.21.3 are fixes held back from What's new and have no item.

  • New
    Overview → Version links the manual to nextdash.cc/docs

    "You can find the full changelog here and the manual here" sent the manual to MANUAL.md on GitHub; the changelog link stays there.

  • Fix
    a repaint from another section waits for that section's file

    Statistics, Help, About, Overview, Logs, Data & backups (trash, webhooks) and Appearance repainted when this.section said they were open, even while the file that draws them was still loading, so a late answer could paint into a body that was not there yet. Each now asks inSection(id), which is true only when the section is open and its file has run.

  • New
    the section planner reads those gates

    scripts/config-section-plan.mjs treats inSection() like the older this.section === checks when it works out which methods belong to which section, so the split of dashboard-config.js still comes out right; tests/config-section-plan.test.mjs covers it.

  • New
    Data & backups and Appearance load from files of their own

    About 2,900 and 2,400 lines of dashboard-config.js move to dashboard-config-data-backups.js and dashboard-config-appearance.js, fetched the first time the section is opened, like Statistics, Glances and Inbox before them. Config opens with less script to read, and nothing about either section changes. The specs that reach into these sections wait for their file first (config-archive-keys-stay, config-local-archives, config-silent-data-loss, config-import-roundtrip, category-header-theme, dashboard-category-spacing, dashboard-column-spacing, theme-choices-hold).

  • Fix
    a section opened from inside Config waits for its file

    With Config already open, a jump to another section (from the command palette, or the Appearance tab a setting names) switched the heading before the section's file had landed, so render() threw and the old body stayed under the new heading. The jump now waits for the file and then draws.

  • New
    the section planner knows the lazy files

    scripts/config-section-plan.mjs sees callers outside a section and the section files that already exist, and the extractor ends a static array at its semicolon, so the next sections can be split off the same way.

  • Fix
    Export CSV and the imports work before Data & backups has been opened

    Since that section moved to its own file, the CSV export of ticked rows (dashboard and Bookmarks view), the browser import and the CSV import called functions that file had not loaded yet and did nothing. Each now loads the file first.

  • Fix
    Home and End on a tab or a chart

    End became "the last row" and "the last section" in v1.22.0, and Config's key handler took it from a focused tab and from a chart's day read-out. Tabs go to the first and last tab again, and a chart to its first and last day.

  • Fix
    a focused block title shows it

    Under Signature the title's tint was cleared with the rest of its background, so moving through blocks with the keyboard showed no mark on the title that had the focus.

  • Fix
    Config tables

    A name in a Structure, Pages or Finders table read as an input box at rest under Signature, and the collection whose editor is open lost its accent bar and line.

  • Fix
    Collection health fits a 560 px window again

    The modal's chrome is taller since the overlays took the material's surface, leaving a few pixels of scroll at 1000 × 560. A fifth step takes the air out of the cards.

Dashboard

  • Fix
    a category save keeps the default category's name in every language

    A new page's default category is stored as the key dashboard.others; the dashboard held it translated ("Others", "Overig"), and a category drag or resize sent that back, so the name stayed in the language it was saved in. clonePageCategories keeps the stored name next to the drawn one and DashboardData.storedCategory() puts it back on save, unless the category was renamed since. Covered by tests/dashboard-review-fixes.spec.js, which fails without it.

  • Fix
    the first settings change made on another device now shows up

    The revision poll only noticed a settings change against a settings revision it already held, and nothing set one at load, so the first change after opening the dashboard was taken as the starting point. fetchAndStoreDataRevision seeds it.

  • Fix
    revision checks no longer run side by side

    Focus and visibilitychange were throttled to one call per 500 ms, and on a slow server a full settings refresh outlasted that. refreshIfDataRevisionChanged now hands a second caller the check already running, and the listener catches its rejection. These two are covered by the same spec, each failing without its fix.

  • Removed
    the one-time key hint along the bottom

    After the quick start, > search · : commands · ? finders · + bookmark wiped in from left to right under the grid, once per browser. It no longer fits a dashboard whose actions stand in the header or on the edge. Gone: #search-flow-hint, initializeSearchFlowHint and its initializeButtonTipsRotation entry point, and the .sfh-seg styles. An empty .button-container now drops its plate through :empty.

  • Fix
    the header falls back to four page tabs, like the server

    pageTabCap used 5 when maxPageTabs was missing, while the server default and the command palette use 4. tests/dashboard-page-strip.spec.js now holds the default to four.

  • Fix
    a client that refuses gzip gets no gzip

    clientAcceptsGzip looked only at the name in Accept-Encoding, so gzip;q=0, which means "not gzip", was answered compressed. A weight of 0 is now read as a no. TestGzipRefusedWithZeroWeight fails without it.

Theme studio

  • Fix
    Cancel while Apply is saving waits for the save

    Escape, the ×, Cancel or a click beside the panel during Apply put the old look on screen while the save stored the new one, and the next unrelated save sent the old one back; a second Apply posted the colours twice. theme-browser.js now ignores every way out while Apply runs.

  • Fix
    a second Shift+A while the studio loads opens the same one

    openLookStudio checked isOpen before its loads, so a second call took a new snapshot over the first: Cancel no longer went back to the look from before, and config did not come back on close. One opening runs at a time (_lookStudioOpening), and the check runs again after the loads.

  • Fix
    a settings change from another device no longer wipes the preview

    refreshIfDataRevisionChanged loaded the settings under the open studio, which replaced the previewed look with the stored one. It now leaves the settings revision as it was while the studio is open, so the first poll after it closes applies the change.

  • Fix
    Reset all also resets the rest of the Surface tab

    lookDefaults() left out categorySurface, widgetSurface, widgetOpacity, materialStyle and neutralAccent, and a forced value of those held for every theme after Reset all. Covered by TestLookDefaultsCoverTheSurfaceTab.

  • Fix
    a theme's own look clears the glass and backdrop of the look before

    A theme's look is stored without the parts that follow the theme, and applying it left those as they were, so after Neon the theme's cards kept Neon's edge and see-through glass. themeLookAnswers fills the left-out backdrop, depth and glass with "follow the theme".

  • Fix
    a studio with nothing to show hands back to config

    When ThemeBrowser.open had nothing to draw, config had already stepped aside and never came back. Covered, with the four above, by tests/look-studio-edge-cases.spec.js.

  • Fix
    Material style no longer snaps back, and no longer picks Classic for every theme

    With "Use these for every theme" off, the select offered "Follow the theme" and read a per-theme answer that nothing wrote; picking it stored Classic install-wide and the select showed it again on the next paint. It is install-wide in every scope now, as the setting is. Covered by tests/appearance-background-surface.spec.js.

  • Fix
    a look keeps the theme's own quiet centre

    The quiet centre is a theme's own answer in theme scope, so Save as theme with its look left it out, and a look applied over it was outranked by it. currentLookAnswers now saves the one shown and applyLookAnswers takes the theme's own over. Covered by tests/look-studio-calm.spec.js.

Inbox

  • Fix
    Undo after pasting the same link again keeps one row

    With "no duplicate URLs" on, RestoreInboxLinkEvicting only compared ids, so deleting a link, pasting its URL again and then pressing Undo left two rows with the same address. It now answers with the item already there when the setting is on; PutInboxItem passes the setting in. Covered by TestUndoKeepsOneRowWhenTheURLCameBack.

  • Fix
    cancelling Promote on a found app leaves no empty category

    discoveryCategoryFor makes the category the app's kind names so the form can preselect it, and closing the form without saving left it on the dashboard. The category is remembered (_pendingDiscoveryCategory) and releaseDiscoveryCategory takes it away again once the form closes with nothing in it, without a trash entry. Covered in tests/app-discovery.spec.js.

  • Fix
    adding a found app no longer undoes a category edit made at the same time

    addDiscoveredBookmarks read the page's categories and saved them back later, so a rename or delete in Config in between was written back as it was. The read and the save now happen under one store lock, through the new MutateCategoriesByPage. TestMutateCategoriesByPageHoldsTheLockFromReadToSave fails without it.

Containers

  • Fix
    Remove stopped needs the names it was asked about

    pruneStoppedContainers treated a request without names as "every stopped container", so a call with no body removed them all. It now answers 400 names-required; the Disk tab always sends the list its question showed. TestDockerPruneStoppedContainers covers both.

  • Fix
    a usage alert that ends without "back to normal" stops its reminders

    checkDockerUsage forgot a high-CPU or memory spell when the container stopped, was muted or usage alerts were switched off, but sent no "up", so the reminder register kept it open: up to three "still has a problem" reminders for a load that was gone, and a later spell found it open and got none of its own. Those spells now leave the register through closeOpenAlerts. TestDockerUsageSpellEndedSilentlyLeavesTheRegister fails without it.

Glances

  • Fix
    a host removed and added again under the same name is started once

    Every host loop reported its end on exited, also a loop that was stopped, and the sampler then stopped whatever ran under that id: the new loop, which reported its own end, and so on without stopping, each round a beat that recorded the host as down. A stopped loop now reports nothing. TestGlancesReaddedHostStartsOnce fails without it.

  • Fix
    a new disk or sensor gets a graph on a machine that has filled its series

    The machine's own series (disks, interfaces, temperatures, mounts) had a limit of 96 and never gave a place back, so a disk renamed at a reboot or a sensor that left held its slot for good and anything new was silently not recorded. roomFor now drops the one that has been silent longest once it has been silent a day, as processes and containers already did. TestGlancesSilentMachineSeriesMakeRoom fails without it.

  • Fix
    Insights weighs the load against every processor

    The core count was the number of core:* series, which stops at 32, so on a bigger machine a load of 40 counted as over the cores. The sampler keeps the count the host reports (glancesHost.cores) and glancesComputeLoad uses it. TestGlancesLoadCountsEveryCore fails without it.

  • Fix
    the last beat of a removed host does not bring it back

    glancesNotify and glancesSlowReads looked the host up again by id, which made a new one for a host removed in between, and a host added again under that name inherited its notice cooldown. Both now take the beat's own host. TestGlancesNoticeOfARemovedHostMakesNoNewOne fails without it.

  • Fix
    Insights gives the real length of an outage still going on

    The availability note counted an ongoing outage but added nothing for it, so a host down for two hours read "1 min in all", and a past outage that began before the range counted in full. Each outage now counts from the start of the range to its end, and one still going on to now. Covered in tests/dashboard-glances-view.spec.js.

Domains

  • Fix
    with IANA unreachable, domain lookups no longer ask for the server list each time

    A failed refresh of the RDAP bootstrap list kept the old one but not its age, so every lookup asked again and waited out the ten-second timeout under the client's lock. The old list now serves another hour first. TestRDAPBootstrapFailureIsNotRetriedPerLookup fails without it.

Docs

  • Docs
    MANUAL.md follows the new look

    A new chapter, 16A The new look, says what changed against the old design and why, that every existing install moved onto Aurora Glass once, how the new and changed backdrops work, and three ways back to the old look (Go back to ‹theme› in the dialog, the theme studio, or Material style → Classic). §16 has the 190+ families, the 75 backdrops, Material style, the accent of the neutrals and Quiet centre. The cheat sheet, the preview card, the action bar, the Unraid themes, the Glances load, the Config band, the icon picker, the two-column bookmark form and the keys (Shift+G, End, g chords) are described as they work now.

  • Docs
    all 131 screenshots in MANUAL.md are taken again in Aurora Glass dark

    , five new ones for 16A, three for Collection health and one for the container timeline. They run over the demo data the server seeds itself (NEXTDASH_DEMO=1, now 101 links with favicons and previews), never over data-demo. The dashboard shows the health, Jellyfin and Glances tiles; the Jellyfin titles and posters come from tests/helpers/media-mock.js and are made up. SHOT_THEME is aurora-glass-dark, and tests/manual-screenshots-v1-22.spec.js takes the 16A shots.

  • New
    the demo looks like months of use

    . The inbox holds 24 links over six weeks, read, snoozed, with notes and tags. Opens run over 90 days with a working rhythm and fewer on weekends, so Usage and its heatmap have a shape. Health has 11 monitors with outages and a slow site, and a 90-day trend whose score climbs while the unchecked links go from 40 to none. TestDemoSeedsThreePagesOfPublicSites expects 90 trend points, and about 100 links.

  • Docs
    the manual's shots follow the demo's own clock

    NOW in tests/helpers/manual-shot-kit.js is the moment the seed was made, and the dates in the fixtures follow, so charts end on the day shown in the header. tests/helpers/docker-history.js gives Containers and Statistics → Server thirty days of crashes, failed health checks and nine updates. New shots: Collection health on its Monitors and Trend tabs (11-collection-health-monitors.jpg, -trend.jpg) and a container's Timeline (14-container-timeline.jpg).

  • New
    the demo seeds 50 more sites for nerds and hackers

    : Security, Linux and Play on Dev, Makers on Homelab and Privacy on Self-hosted. TestDemoSeedsThreePagesOfPublicSites now expects about 100 links.

  • Docs
    Config → Help follows the new look, in all six languages

    The Themes panel names Aurora Glass as the default, more than 190 families and 75 backdrops, and the theme studio instead of the theme browser. New in it: the Signature and Classic material styles, the eight neutrals and their accent, ThinkDashboard Classic, Quiet centre, and a paragraph on the move to Aurora Glass. Appearance lists the new Surfaces settings and the eighth backdrop slider. Keyboard adds Shift+G and the new cheat sheet, and uses a lowercase g for the chords. Bookmarks, Inbox and Config list g/End for first and last. The bookmark form is described in two columns. Five tips follow (tipTuneThemeBrowser, tipTuneThemeBrowserWidth, tipTuneGloss, tipTuneLooks, tipTuneBackdrop).

  • Docs
    README.md follows the new look

    It names Aurora Glass as the default, 192 theme families (384 themes), the twelve materials and the three collections, the signature and Classic material styles, 75 backdrops with a quiet centre, and calls the panel the theme studio. All 22 pictures are taken again over the demo data the server seeds itself; the dashboard is in Aurora Glass, the bookmarks view in its light half and the command palette in ThinkDashboard Classic, the rest in a theme each.

  • Docs
    the theme studio is called the theme studio

    The Overview news item about it said "look studio"; its title now says theme studio in all six languages.

  • Docs
    the Quiet centre, Material style and the accent of the neutrals are translated

    in Dutch, German, French, Spanish and Chinese: 20 keys under config (backdropCalm, materialStyle*, neutralAccent*), so validate:locale-parity passes again.

  • New
    What's new leads with the redrawn themes

    static/data/whats-new/v1.22.0.json has three highlights, each with its own picture or recording: every theme redrawn (a screenshot, with a button to the theme studio), 75 backdrops with a quiet centre (a recording) and the searchable cheat sheet (a recording). The plan is in tests/fixtures/whats-new-media/v1.22.0.js, the files in static/data/whats-new/media/, and whats-new-stub.js names v1.22.0 as the release the window opens for.

  • Docs
    nextdash.cc follows the new look

    Every feature page has new pictures in Aurora Glass dark, with six on Statistics (all tabs) and two more on Tags (the tag picker and the tags offered on a new bookmark). The theme gallery shows all 192 families in dark and light with the backdrop each comes with, and has a Classic group for ThinkDashboard Classic. The hero and the slider open on Aurora Glass.

  • New
    scripts refill the demo data and retake the manual's shots

    . The first lets the server seed itself and fetches the favicons, the second takes the four shot specs with eight workers and reads the real exit code, the third checks that every picture MANUAL.md names exists and that every file is used. They refuse data-demo and port 8080.

  • Fix
    every fixed wait in the tests says why

    validate-test-waits (the validate-json job in CI) failed on 31 waitForTimeout calls without a // reason directly above them: the overlay, material-header, neutral-accent, view-entrance and look-migration specs, the manual-shot spec for 16A and the What's new media plan. Each now says what it waits for, or that it is pacing for a capture or the check is that nothing happens.

  • Fix
    the e2e specs follow the new look

    31 specs pinned the old drawing: the widget title strip, the depth ladder, the glow ring, the title offsets and handle, the glass, card and open panes of Config and the list views, the sheets that hang from the header, the cheat sheet's folded topics, the Help text, and the number of backdrops. Each now tests what it protects under Signature, or puts the page in Classic without saving it where the old drawing is the point. The ℹ popover spec waits for the page to hold still and presses the button again if a late scroll closed the popover, the About diagnostics spec waits for the platform, the Glances entrance spec only counts blocks that were drawn while the entrance window was open (a slow runner gets them without a rise), and the two Look studio specs that timed out on the CI runner get more room.

Only docs and tests changed in this release.

v1.21.3 The Containers view keeps its scroll position in Safari as well — held back from the What's new window (hideFromModal) like v1.21.2, so v1.21.1 keeps leading it. 1 fix

The Containers view keeps its scroll position in Safari as well — held back from the What's new window (hideFromModal) like v1.21.2, so v1.21.1 keeps leading it.

Containers

  • Fix
    a poll no longer throws a scrolled Safari reader to the top

    v1.21.2 held the list's height while a redraw emptied and refilled it, which was enough in Chromium. WebKit still lost the place whenever the list was swapped while the rail's figures above it had just changed, with nothing read in between. render() in dashboard-docker.js now builds the new body before it is put in place in one go, and reads the scroll position before the redraw and puts it back in the same task, so nothing moves on screen. tests/list-view-redraw-scroll.spec.js has a second test that moves the page to the top half-way through a redraw, as WebKit did; it fails without the fix.

Docs

  • Docs
    static/data/whats-new/v1.21.3.json and its index entry

    , held back like v1.21.2; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v351. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.21.2 A list view keeps its scroll position when a poll redraws it, and the Containers table no longer runs past the right edge of a narrow list. 2 fix

A list view keeps its scroll position when a poll redraws it, and the Containers table no longer runs past the right edge of a narrow list.

Lists and Containers

  • Fix
    a poll's redraw no longer throws a scrolled list view to the top

    A redraw empties the list body and fills it again, and a read in between (an app icon asks the theme whether it is dark) laid the page out with the body empty, so the browser moved the scroll to the top. ListViewShell has a holdHeight() that keeps the body as tall as it was until the redraw is over; the Containers, Glances and Inbox views call it. Covered by tests/list-view-redraw-scroll.spec.js.

  • Fix
    the Name and Image columns in Containers give way to the list width

    At a narrow list two 16rem columns plus the rest outgrew the pane and the table ran past its right edge in Chrome. Both columns are capped by the width of the list as well.

Only docs and tests changed in this release.

v1.21.1 Glances Insights answers more of what you ask a machine: nine new blocks, an info button on every title, and the Containers view says why no container could be paired. +4 12 fix

Glances Insights answers more of what you ask a machine: nine new blocks, an info button on every title, and the Containers view says why no container could be paired. A write token now also refuses host names nextDash does not know, icons are served more safely, and a handful of small click and save problems are gone.

Glances

  • New
    nine more Insights blocks

    Compared with before sets the range against the one just before it, A typical day draws the average of each hour, Peaks and rhythm names the busiest and quietest hour and the readings far above their usual level, Load and cores sets the load against the number of cores and shows how evenly they share the work, Memory and swap splits the memory into in use, cache and free, Temperature per sensor, Disk space over time, Disk activity and Network per interface (with the containers behind the traffic) complete it. internal/app/glances_insights_more.go computes them from the record next to the first set, dashboard-glances-insights.js draws them, and a block with too little behind it is left out.

  • New
    an info button on every Insights title

    dashboard-glances-info.js has nine more texts that say what a block shows in two or three sentences. The page's blocks also fill two columns now: one left alone on its row takes the whole row, and the Insights panels hide their scrollbars.

  • New
    the link with Containers says why nothing paired

    When Config → Glances says the host is the Docker host but no container could be matched, /api/glances/docker-link carries a problem (glances-unreadable, docker-unreadable or none-matched, with both counts). Config → Glances → Advanced and the side panel in the Containers view say which one, covered by tests/glances-containers-link.spec.js.

  • Fix
    containers did not pair on Glances 4

    A container's ports are read as the one string Glances 4 sends, so the containers pair up.

  • Fix
    the typical-and-peak table needed a scrollbar

    It takes the whole row now.

Security

  • New
    unknown host names are refused when a write token is set

    host_guard.go answers Host not allowed (421) to a request that names a host nextDash does not know, so a page on another domain cannot point its own name at your address and take the token. IP addresses, localhost, names without dots and the private endings .local, .lan, .home.arpa, .internal and .ts.net always pass; NEXTDASH_ALLOWED_HOSTS adds public names (*.example.com, or * to turn the check off). Status pages under /s/ are not checked.

  • Fix
    the SVG sanitizer is stricter and served icons are sandboxed
  • Fix
    the host check logs through the log helper

    host_guard.go called log.Printf directly, which TestNoDirectPrintfOutsideLogx refuses; it uses logInfo now.

Bookmarks and the dashboard

  • Fix
    localhost:3000 is a web address

    A bookmark URL such as localhost:3000 got https:// in front of it instead of being read as a scheme.

  • Fix
    a double click or Enter saves a bookmark once
  • Fix
    creating a page or a category no longer overwrites the list when reading it failed
  • Fix
    Restore commits the leftover categories with the rest
  • Fix
    polling

    Widget beats do not stack, the health facts share one read, and hidden tabs skip the status checks.

  • Fix
    a second page-tab rename cannot start while a popover is open
  • Fix
    a view's entrance waits for its rows

    so a slow load still rises in.

  • Fix
    row checkboxes sit above their 24px hit-area overlay

    so a click lands on them; the 24px targets keep the layout they had in the field notes, the Appearance control column and the category +. The note box shows a focus ring.

Docs

  • Docs
    static/data/whats-new/v1.21.1.json and its index entry

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v349 and DASHBOARD_RELEASE to v1.21.1. go generate refreshed asset_hashes_gen.go.

  • Docs
    the manual

    §15A.3 lists every Insights block and the info buttons, §15A.6 the three link messages, §23.2 which host names may open a server with a write token, and §24 has a Host not allowed entry. The two Insights screenshots are new; the Glances shots for nextdash.cc come from the same fixture.

  • Docs
    Config → Help

    A new Insights panel in the Glances topic, with a drawing of a typical day whose bars rise one after the other (only where motion is welcome) and a meter for the load against the cores; the Containers panel says what the three link messages mean, and Self-hosting explains which host names may open a server with a write token. Six languages, and tests/config-help-glances.spec.js counts eight panels.

  • Docs
    a check for keys without a translation, and the 34 it found

    npm run validate:locale-referenced reads every t('section.key', 'fallback') in static/js and fails on a key that is not in locales/en.json, the one direction the other locale checks cannot see. It found 34 strings that had no key in any file and so showed in English everywhere: the Emby and Plex widgets (fifteen each: states, relative times, the open and close buttons), the Home Assistant widget's two messages, the Jellyfin widget's Nobody is watching right now, and the tag view's add suggested key. They are in all six languages now. The manual's Finders line says the finders you use most are suggested first.

  • Docs
    the What's new pictures

    tests/fixtures/whats-new-media/v1.21.1.js takes the Insights and the link-message images.

  • Docs
    release script

    release-to-main.sh puts the tree of origin/dev on main as one commit and stops when the local dev differs from origin/dev by more than site/.

Only docs and tests changed in this release.

v1.21.0 Glances arrives: a page for the hosts you run Glances on, with graphs, insights and incidents, a widget for the dashboard and notices for a disk that fills up. +11 30 fix

Glances arrives: a page for the hosts you run Glances on, with graphs, insights and incidents, a widget for the dashboard and notices for a disk that fills up. Berry is the default theme now, with a card that offers it to everyone who is not on it. Next to it come domain expiry through RDAP, a round of accessibility and mobile fixes, and a hardening pass over uploads, backups and request handling.

Glances

  • New
    a Glances page

    Overview, Processes and Containers sections with graphs, insights, tabs and a side panel, recording of its own history, and a connection switch. It has a navigation icon, Shift+G, info buttons and works in demo mode.

  • New
    several hosts

    A Hosts section lists every host in one table; a host menu and a list in Config pick the one you look at. Config → Glances has a host bar and five tabs, split into what is per host and what is shared, and saves as you change it, with no Save button.

  • New
    incidents and notices

    An incident panel gives the cause, :glances commands sit behind write access, and a notice warns about a disk that is filling up and records the busiest process by itself. Glances notices have their own browser-notification switch.

  • New
    compare and export

    Compare with last week, save a graph as an image, a hosts strip, per-core series, a record pace you set and a reset.

  • New
    a Glances widget

    One host on the dashboard as meters or the processor graph, with a sparkline, following the meter settings.

  • New
    links with Containers

    The Containers view reads CPU, memory and network from Glances on the Docker host and shows restart marks; Config says which host is the Docker host, and both views link to each other.

  • New
    a page tour

    Six animated steps, a Tour button in the header and a replay from Config and Help. Help has a Glances topic with seven tips; the cheat sheet and its PDF list the Glances keys.

  • Fix
    keys and focus

    Escape closes the side panel first and stays on the list; one search bar sits above Processes and Containers with a count and a clear button; the view returns at once from the last read and rises in like the other list views.

  • Docs
    specs and translations

    Specs cover hosts, commands, the incident panel and accessibility; the new strings are in all six languages.

Domains

  • New
    domain expiry through RDAP

    A widget, a badge in Bookmarks and alerts show when a domain runs out.

Look

  • New
    Berry is the default theme

    A fresh install starts on Berry [dark] (look-berry-dark, with look-berry-light for auto dark mode) in place of Confetti. Installs keep the theme they have. The one-time corner card that offered Confetti now offers Berry and is shown again to everyone who is not already on Berry, in either half, including those who answered the Confetti card: its id is berry-theme-try-v1, and a fresh install starts with it answered. Try Berry applies the dark half and can be undone with Go back. The card's strings are dashboard.berryNotice* in all six languages.

  • Fix
    tertiary text reaches 4.5:1

    The default themes had tertiary text under the WCAG AA ratio.

  • Fix
    a visible focus ring on inputs

    Inputs that only changed their border colour on focus now draw a ring.

  • Fix
    no-animations no longer moves centred elements
  • New
    refreshed backdrops

    Hexagons, blueprint, prism, chevron, sunset and mountains.

Dashboard

  • Fix
    24 px targets and a 12 px text floor

    Layer tokens replace loose z-index values, and the tip waits for a modal to close.

  • Fix
    Mobile

    Overlays use dvh, tap targets are bigger and the Config tabs fade at the edge.

  • Fix
    touch drag lock, a category race, Escape in modals and status and weather glitches
  • Fix
    a search opens on the letter you typed

    The first letter went into the search line in the upper-case reading the key checks use, so immich showed as Immich. It goes in as typed now. j and k walk the grid only while the cursor is in it, and outside it a letter opens the search, as before.

  • Fix
    Escape in the bookmark grid leaves it

    The cursor was cleared, but the row's link kept DOM focus, so the row stayed lit and the grid still felt like the place the keys went. Escape now lets go of that focus too: no row is marked, and j and k are letters for the search again.

  • Fix
    cancelling a search typed from nowhere leaves the grid alone

    Escape handed focus back to the grid, and with no row picked it put the cursor on the first row, lit it, and made j and k steps through the rows again. A search that started with no row picked and no control that opened it now gives no focus back; one opened from a row still brings that row back.

  • Fix
    the date popover stays on screen

    the place picker uses valid ARIA and the dismiss label is translated.

  • Fix
    rejected saves and commands are caught

    the finder shortcut is escaped and search picks are flushed.

  • Fix
    moving a widget saves what was typed first

    and 0 is the tenth page, not the Inbox.

  • Fix
    collapsed categories and the theme migration

    are guarded against bad browser storage.

  • New
    Add new bookmark in a category's right-click menu

    The first entry on a category header opens the add-bookmark form with that category already chosen, the same form the + button opens. Smart collections and the list of unfiled bookmarks do not show it.

  • Fix
    the Glances widget is styled before the Glances page is opened

    Its rules sat in the Glances page's stylesheet, which only loads with that view, so a widget on a dashboard that had not opened the page drew a plain blue link and a black sparkline. They are in dashboard-widget-glances.css now, linked with the dashboard's own sheets.

  • Fix
    the Calendar tile expands recurring events
  • Fix
    widgets

    keep no cached error from a closed tab, retry sooner, and Radarr shows its release day.

Inbox, Containers and Config

  • Fix
    Inbox

    Roomier rows on mobile, one title and a collapsible key legend.

  • Fix
    Containers

    Red only for failures, dormant links and one note bar. Container alerts stay apart by kind and resync after a gap in events.

  • Fix
    Config

    Clearer labels, a grouped menu, a sticky Bookmarks preview and 24 px targets.

  • Fix
    Health

    Results stay on their page and a failed save is retried.

Server

  • Fix
    uploaded SVGs are served under a sandboxed policy
  • Fix
    a backup zip is restored without copying it into memory first

    and its size is capped.

  • Fix
    a settings body that is too large answers 413

    and only a plausible X-Request-ID from the client is accepted.

  • Fix
    PATCH preflights

    are allowed on the bookmark and Inbox routes.

  • Fix
    tag lookup asks for the write token
  • Fix
    an empty list is not cached after a failed read

    and health and runtime caches reset when an import fails halfway.

  • Fix
    merging duplicate bookmarks carries the monitoring setup over
  • Fix
    odd bytes cannot panic the HTML parsers

    (length is kept when lowercasing).

  • Fix
    small ones

    page order, backup prune order, a Config race and duplicate URLs.

  • Docs
    the Docker build

    drops the needless -a and -installsuffix flags.

Docs

  • Docs
    translations

    The 35 strings for domain expiry, six that had no key in any locale file (Compose lines, the overview's checked count, Category name, a container link that is not running and the Inbox key legend's two labels) and the new category menu entry are in Dutch, German, French, Chinese and Spanish.

  • Docs
    Dutch says bookmark

    All 829 strings in locales/nl.json that said bladwijzer now say bookmark, compounds included (bookmarkformulier), plus the no-JavaScript line in templates/dashboard.html and the two specs that matched the old word.

  • Docs
    the manual

    A new §15A, Glances, with eight screenshots, and the Glances lines that belong elsewhere (the keys, §14 Containers, the widget kinds, Config's section table, troubleshooting, the glossary). 0 is described as the tenth page, the category menu's new entry, the Inbox key legend, the Containers row colours and dormant links, the Config rail's Services and Info groups and the restore limits are in. Six screenshots are retaken, in Gloss Chrome dark over the demo that nextDash seeds itself rather than over data-demo.

  • Docs
    the README

    It names the Glances page and widget, domain expiry, the About tab and Copy diagnostics, 29 backdrops, forty-eight kinds of widget and seven webhook events, and opens with a picture of the dashboard in Berry. Its twenty pictures are taken again over the demo nextDash seeds itself, at 1920×1200, each in the theme its caption names, with two new ones for Glances; the captions say what the new pictures show. The Unraid template lists the two Glances pictures.

  • Docs
    nextdash.cc

    A Glances page among the features, and the sentences that were out of date on ten others: the number of widget kinds (forty-eight), the Beszel, Glances and Domains tiles, domain expiry under Health and Alerts, the Theme tab and the two typefaces under Appearance, About and Copy diagnostics under Config, the Containers colours and links, the Inbox key legend, 0 for the tenth page, the category menu and the Server tab of Statistics. The homepage hero opens on Berry, Beszel and Glances are under Works with, and the theme gallery (463 pictures) and the stills of the feature pages are taken again in Berry over the demo nextDash seeds itself. The docs splitter takes chapter 15A, so the manual's Glances chapter builds. The same branch also lands the earlier site work: a Contact page and form in the footer, a Developer link to jordibrw.nl, the Theme studio counts of v1.20 with all 29 backdrops, the Quick start guide on Install, and a gallery of every theme with a note that they are examples (site/).

  • Docs
    the shot kit

    tests/helpers/manual-shot-kit.js reads the theme and the output folder from SHOT_THEME and SHOTS_OUT, and a test can name its own theme and change its copy of the data.

  • Docs
    the What's new window

    v1.21.0 leads it, with a recording of the Glances page and pictures of the Domains and Glances widgets taken over the neutral demo. The Glances answers the shots need moved from the manual spec to tests/helpers/glances-mock.js, and the shot kit has a domains patch. The Dutch, German, French, Spanish and Chinese cheat sheet lines for Glances are translated.

  • Docs
    a test

    tests/dashboard-category-menu-add-bookmark.spec.js opens a category's menu, picks Add new bookmark and expects the form on that category.

Only docs and tests changed in this release.

v1.20.3 The dashboard is set in Source Code Pro and every other screen in Inter, and Config → About has a new look with a Project, an Install and a News & features tab. +4 1 fix

The dashboard is set in Source Code Pro and every other screen in Inter, and Config → About has a new look with a Project, an Install and a News & features tab. It is held back from the What's new window (hideFromModal), so v1.20.1 keeps leading it. v1.20.2 was never tagged on its own; it ships with this release.

Look

  • New
    two fonts, one for the dashboard and one for the rest

    The header bar, the bookmark grid and the search panel are set in the font preset under Appearance, Source Code Pro by default. Config, Inbox, Tags, Containers, the modals and the other views read in Inter, which is served from /static/fonts like the mono. The font you pick, or the look you apply, still decides the dashboard only; code, addresses and key chips stay on the mono everywhere. The tag cloud panel is Inter. --font-family-ui and --font-family-dashboard are the two roles, and the dashboard surfaces swap what --font-family-main means for their subtree, so the rules that ask for it need no change; the grid follows data-active-view="bookmarks".

  • Fix
    the +N on a tag offer takes the page font

    .tag-offer-more was a button with no font of its own and drew in the browser's default, Arial.

  • Docs
    a test for the split

    tests/font-default.spec.js asks for Source Code Pro on the header bar and the grid, Inter on the body and in Config, and Inter loaded from /static/fonts.

Config

  • New
    About has three tabs: Project, Install and News & features

    Project says what nextDash is, why it exists and who makes it, with links to the docs, the issues, the changelog and the manual, a Ko-fi card at the top right and the roadmap. Install shows the release you run and whether a newer one is out, tiles for pages, categories, bookmarks, widgets, tags, data size, uptime and platform, and Copy diagnostics, the facts a bug report asks for with no file paths in them. News & features is the old second tab, moved and restyled. The old colophon tab address opens Project.

  • New
    GET /api/about-info

    The facts behind the Install tab: release, build version and commit, build date, Go version, OS and architecture, start time, uptime, the size of the data folder and the listen port. No paths.

  • New
    a licence list under Credits and licences

    The collapsed block at the foot of Project lists the licences of what nextDash ships with. It is generated by scripts/gen-licenses.mjs into static/data/licenses.json, and scripts/release-preflight.sh checks that the file is current.

  • Docs
    tests for About

    tests/config-about.spec.js and tests/config-about-section.spec.js cover the three tabs, the old tab address, the facts, the copied diagnostics and the licence list; about_info_test.go pins /api/about-info.

Docs

  • Docs
    the manual

    §16's Typeface line says the preset sets the dashboard and Inter the rest; §17.8's About paragraph describes the three tabs, with a shot of Project and one of Install. The five full-page Config shots (Appearance, Bookmarks, Inbox, Containers, Help) are retaken, now in Inter.

  • Docs
    Help

    Config (the About line), Appearance (the typeface) and Getting started (the Install tab and Copy diagnostics) say what changed, in six languages.

  • Docs
    translations

    The 34 About strings (config.about*) were English fallbacks in the code only; they are in locales/ in all six languages now. The overview carries an item for the Install tab and its diagnostics, since v1.20.3, in six languages.

Only docs and tests changed in this release.

v1.20.2 The text of the whole app is set in Source Code Pro again, the mono the app is named for. 4 fix

The text of the whole app is set in Source Code Pro again, the mono the app is named for. A fresh install starts on it, an install still on Inter moves to it once, and Inter stays one pick away under Appearance. It is held back from the What's new window (hideFromModal) like v1.19.10 and v1.19.11 were, so v1.20.1 keeps leading it.

Look

  • Fix
    the text font is Source Code Pro by default, and was Inter

    Inter had been the default since the text in a mono cut long names short in narrow columns, and the code-like parts (the //, addresses, figures, key chips) stayed on the mono. The default is the mono for the text as well now: FontPreset is source-code-pro on a fresh install, for a value that is not a preset and for a custom font whose file is gone, and the same fallback stands in the browser and in --font-family-main, so nothing paints in Inter before the settings arrive. The preload of Inter left templates/dashboard.html; the mono was preloaded already, and a reader who picks Inter loads it as before.

  • Fix
    an install on Inter moves once

    fontDefaultMonoMigrated is the mirror of the move to Inter in v1.20.0: an install still on Inter goes to Source Code Pro, one on another preset or an uploaded font stays, and a reader who goes back to Inter after the pass keeps it. The server cannot tell a reader who chose Inter from one who was given it, so the first group moves with the second. An install from before the move to Inter passes both and ends on the mono.

  • Fix
    the two looks that set Inter set the mono

    Glass and Glass boxed in the look studio named Inter for their text; they name Source Code Pro now, like the default they sit beside. The looks that name DM Sans or IBM Plex keep them.

  • Fix
    Go 1.26.10, for GO-2026-6809

    govulncheck found crypto/x509 in Go 1.26.9 distrusting too few compromised intermediate certificates, reached through WriteNetscapeBookmarks. toolchain in go.mod is go1.26.10, the release that fixes it, and the scan finds nothing.

  • Docs
    tests for the default

    TestFontDefaultIsSourceCodeProOnAFreshInstall and TestFontDefaultMovesEveryoneOnInterOnce in font_default_test.go pin the fresh install, the move, the presets that stay, an uploaded font, a reader who goes back and a file without the key; TestNormalizeFontPreset follows the fallback; tests/font-default.spec.js asks for Source Code Pro on the page, loaded from /static/fonts with no request to a font CDN.

Docs

  • Docs
    the manual

    §16's Typeface line says a fresh install reads in Source Code Pro, that an install on Inter moved once and that Inter stays a pick. Help and the translations follow in the next docs round; go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.20.1 Four Beszel widgets show how your other machines are doing: every system, one system in full, only the ones that need a look, and every disk. +2 14 fix

Four Beszel widgets show how your other machines are doing: every system, one system in full, only the ones that need a look, and every disk. Confetti keeps the // and the widget icon in its headers. The Containers and Bookmarks views fit a laptop window again, and the Bookmarks header waits for a scroll before it turns solid, as the other list views do. Config is one pane now, easier to read on glass, with its hints under the settings, a calmer Overview, Statistics and Logs, and the Unraid connection first.

Widgets

  • New
    four Beszel widgets

    They read a Beszel hub and sit under How is this machine doing?: Beszel systems (every system with a dot for its state; narrow, the reading closest to its limit, wide, processor, memory and disk as bars with the temperature and uptime), Beszel system (one system in full, and wide, its processor over the last hour), Beszel attention (only the systems that are down, waiting, paused, or running hot or full, with the reason when wide, or one line saying all are fine) and Beszel storage (the root disk and every extra disk of each system, fullest first, grouped per system when wide). A reading turns amber at 80 % and red at 90 %, a temperature at 70 °C and 85 °C. A system that is down shows that it is down and since when, never the readings Beszel keeps from before.

  • New
    Beszel is set up like the other service tiles

    The hub's address and the email and password of a Beszel user, then Connect, which says Connected to Beszel with how many systems it found and lists them: boxes to tick for systems, attention and storage (all ticked means every system, one added later included), one system for the single-system tile. Then the figures to show (processor, memory, disk and temperature to start with; graphics card, network and load on request — a figure the agent does not report is left out, never drawn as zero), the order, leaving out paused systems, the click, rows and refresh (30 s at least, 60 s by default). The password stays on the server, which signs in itself and again when the session runs out. Four tiles on one page ask the hub once per refresh, not four times.

  • Fix
    a service that could not be reached said its sign-in was refused

    A sign-in that never got an answer — no route to the host, a refused connection, a timeout — was reported as refused that sign-in, which sends you to retype a password that was right. It now says the service could not be reached; an answer that came back and said no is still a refusal. This holds for every tile that signs in, qBittorrent included.

Themes

  • Fix
    Confetti keeps the // and the widget icon

    On Follow the theme Confetti drew its headers Clean, which hides the // before a category name and the panel icon before a widget name (they show as a grip on hover). Confetti now keeps the theme header like every other theme; Clean stays one pick away in Category header → Style.

List views

  • Fix
    the Containers table ran past its pane on a laptop window

    Which columns give way was decided by the window's width (768–1099 px), but the rail, the pane's padding and the page margin take a different share at every size: at 1140 px the list had 664 px for a 781 px table. The columns now answer to the list's own width, a container query on .lvs-body (docker-list): Image goes under 860 px, CPU, RAM, Size and Restarts under 660 px. The body is the container rather than the table, so the sticky column heads keep the window as their scroller.

  • Fix
    the Bookmarks header was dark before anything scrolled

    The rule that leaves a list view's header see-through at rest named the Tags, Inbox and Containers views, whose band is the shell's .lvs-header; the Bookmarks view's band is config's .config-view-head and was left out, so it showed its scrolled, nearly solid fill from the first paint. It is in the rule now.

  • Fix
    the Bookmarks toolbar overlapped itself on a laptop window

    It never wrapped, so beside the rail the search box shrank to 0 px and the count was drawn over it, and Add Bookmark ran past the edge. The toolbar wraps at every width and the search box keeps at least 12rem.

  • Docs
    three new tests guard these fixes

    On a laptop-sized window the table stays inside the list in tests/docker-columns.spec.js, the Bookmarks case of the header of … is part of the pane in tests/config-panes.spec.js, and on a laptop-sized window the toolbar wraps in tests/config-bookmarks-redesign.spec.js; each fails without its fix.

Config

  • Fix
    Appearance's tabs took two lines on a normal window

    Each group's label stood above its tabs, so the three groups needed a second row for nine tabs. The label now sits in front of its tabs, a thin rule sets the groups apart, the tabs are a little narrower, and two names are shorter: Theme (was Theme & type) and Previews (was Link previews). The strip is one line from about 1440 px wide; narrower, it still wraps by whole groups. Old links keep working; the tab ids did not change.

  • Docs
    a test for the one-line strip

    On a wide window the strip is one line in tests/config-appearance-groups.spec.js, and the wrap test there now checks the label in front of the tabs; both fail on the old layout.

  • Fix
    Config was a pane per panel, now it is one

    Config had two arrangements, loose panes on the page and one pane round the whole view, and the loose one was the default, so on a glass theme it read as a different application beside the other views. It is one pane now, round the header, the list of sections and the content; a panel, an overview card or a table inside keeps a faint tint and a hairline rather than a pane of its own, so a long settings page still shows where a block starts and ends. The other arrangement is gone.

  • Fix
    hints sit under their setting, and an ℹ that said the same is gone

    The line under a setting is the first sentence of its info, so an ℹ with a one-sentence info opened a dialog that repeated it. The ℹ is left out where it would only repeat the line, and stays where there is more to read; Appearance keeps all of them, since its line is cut to one row and the dialog is the way to read the rest.

  • Fix
    Appearance rows and widget names collided

    A row's label, its explanation and its control, and the names in the widget lists, ran into each other at some widths.

  • Fix
    shorter intros, a lower Bookmarks preview, Compose lines folded

    The opening lines of Categories, the status modes, the Unraid connection and the Status page say what the tab is for and leave the rest to the settings; the Bookmarks view's preview is shorter, so the settings are what the tab shows; and on Containers → Connection the compose lines for the Docker socket sit folded under Compose lines, since they are for the one time you set it up and the status above them is what you came to read.

  • Fix
    the way to a view is at the right edge of the band

    Bookmarks and Inbox each have a view of their own, and the link to it (Open the Bookmarks view ↗, Open the Inbox ↗) was a button drawn into the body of one tab. It stands in the same place in both now, beside the section's title. A divider sets Containers apart in the list of sections, and Statistics' first tab is Summary (was Overview).

  • Fix
    Unraid opens on the connection

    The section opened on All, with How it works above the connection form and the seven widgets drawn in miniature with example figures. It opens on Connection now, the address and key first and the widgets as chips under them, each with its Add; How it works is a tab of its own. All and What you get are gone.

  • Fix
    a calmer Overview, Statistics and Logs

    The six figures at the top of a Statistics tab stand three and three, or all six on a wide window, or two and two on a narrow one, never five and one left over; the tiles of Logs stay out of the way until the log has a line, since three zeros say nothing.

  • Fix
    toggles, row buttons and Delete are easier to hit and to read

    A checkbox and its words are one target, a little taller than the text and tinted under the pointer, with nothing around it moving. Duplicate, Delete and the other buttons in a table row have an edge and a faint fill and their ink at full strength, instead of two grey words beside a number; Delete was red on a red-tinted row and nearly vanished, and is pulled towards the text colour now, on a light theme as well. The title above the list of sections is small and muted, since the band above it already says where you are.

  • Docs
    tests for the one pane

    tests/config-panes.spec.js now asks for one pane round Config and no second arrangement, and two structure tests follow the new buttons.

Docs

  • Docs
    the Beszel widgets, server side

    widgets_beszel.go reads /api/collections/systems/records with the PocketBase session the Custom widget already knew (token in Authorization, no Bearer), and for the single-system tile the last hour of system_stats (type='1m', filtered by system and time; the collection refuses a sort). The four types share one cached question per hub, sign-in and refresh, keyed by the login (host, user, password hash) rather than the credential id, because each widget files its sign-in under an id of its own. An expired token makes PocketBase answer 200 with an empty list, so a list that was full and comes back empty signs in once more before it is believed. MediaItem gains an optional meters block and MediaResult an optional counts; answers without them are byte-identical to before. Routes GET /api/widgets/beszel, /beszel-system, /beszel-attention, /beszel-storage and POST /api/widgets/beszel/setup (write token, denied in demo mode). Tests in widgets_beszel_test.go and widgets_beszel_route_test.go run on a scrubbed recording of a real hub in internal/app/testdata/beszel/.

  • Docs
    the Beszel tiles

    dashboard-widget-beszel.js draws the four types through the media tile's new draw hook, with the one- and two-column forms switched by the panel's container query; meterTone and meterBar in dashboard-media-tile.js are shared helpers. A checkset setting can now name its starting selection (defaults), used for the Beszel figures. tests/dashboard-widget-beszel.spec.js covers each tile at 320 and 680 px, a down system that carries stale readings, and Connect → choose → Save.

  • Docs
    mediaSignInError

    in widgets_media.go tells a transport failure (*url.Error) from a refusal, for mediaRequest and the Beszel sign-in; a test signs in to a closed address.

  • Docs
    107 strings in six languages

    The Beszel widgets', and the ones Plex, Home Assistant, the Containers notes and the now-playing tiles had only in English: widget names and descriptions, setup words, values and errors.

  • Docs
    Help and MANUAL

    Config → Help → Widgets lists the four Beszel kinds (forty-six in all) and Beszel among the services with a tile of their own, in six languages. MANUAL §15.1 has a table of the four with three screenshots (15-beszel.jpg, 15-beszel-system.jpg, 15-beszel-narrow.jpg, taken by the new 15 beszel shot with data patch beszel), §15.3 the set-up, and the homelab sections mention them.

  • Docs
    the Unraid template

    lists the v1.20.0 changes, the same as the copy Community Applications reads.

  • Docs
    Help, tips and the manual follow Config

    Config → Help names the tabs as they are now (Theme, Previews, Statistics' Summary), says that Appearance's tabs share one line from about 1440 px wide, that a short line under a setting explains it and an ℹ opens the rest where there is more, that Unraid opens on Connection, and where the link to the Bookmarks view and the Inbox stands; a tip, the themes topic and two news lines that sent you to Theme & type and Link previews send you to the new names. MANUAL §15.6, §16, §17, §18 and §20 say the same, and 33 screenshots are taken again in Gloss Chrome dark on default settings, the Unraid one now showing the Connection tab. About is left out of the manual.

  • Docs
    fourteen strings that had stayed English-only in five languages

    The three tab names, the two lines of the Status page's introduction, the Unraid introduction and its widgets panel, the introduction of Categories, the checking modes' lead, the About and Version texts and the Docker socket hint were changed in English alone; Dutch, German, French, Spanish and Chinese have them now.

  • Docs
    static/data/whats-new/v1.20.1.json and its index entry

    , with the Beszel widgets as the highlight and a picture. whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v345 and DASHBOARD_RELEASE to v1.20.1. README counts forty-six widget kinds and names the Beszel ones. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.20.0 A new default look, and a lot of ways to change it. +43 26 fix Read the post

A new default look, and a lot of ways to change it. A fresh install starts on Confetti with masonry columns and Inter; twenty-four colour-burst themes arrive with three new backdrops; categories and widgets sit on glass, a card or nothing; a category can show tiles; Config and the list views are panes like the dashboard; Statistics gains a Server tab. The keyboard shortcuts sheet is easier to scan and search, and widget titles go back to a plain title over their card.

New defaults

  • New
    a fresh install starts on Confetti

    (look-confetti-dark, its light half for auto dark mode), with masonry columns, a density that follows the screen (auto) and Inter for text; code, addresses and the // stay on the mono face. Category spacing follows its setting. An install that already has a theme keeps it.

  • New
    category headers start small

    The Size of a category header defaults to Small (it was Medium), for a fresh install and, once, for an install still on Medium; one that chose Large keeps it, and so does anyone who goes back to Medium after the pass has run (CategoryHeaderSmallMigrated). Reset all in the look studio puts it back to Small, and the page carries the size from the first paint (data-cat-size on the body) so headers do not jump on load.

  • New
    velvet themes are flat with a soft glow

    Every velvet theme, including the Looks that use it, now ships at depth Flat with glow Soft on glass panes (it was depth Glass, or glow Off). The other characters are set below, under Themes and looks.

  • New
    one-time moves for existing installs

    An install still on the old defaults (compact rows and the default layout; Source Code Pro; type size m) moves once to masonry and auto density, to Inter, and to type size lg. One that chose something else keeps it, and so does anyone who goes back after the pass has run (GridDefaultsMigrated, FontSizeLgMigrated).

  • New
    a one-time card to try Confetti

    Someone with a dashboard already is asked once whether to switch. Try Confetti applies the dark half whatever theme they are on, and the card turns into Go back and Keep Confetti, so trying it costs one click to undo; Not interested is a final answer. Nothing is offered on Confetti itself or with a random theme rotating.

  • New
    a start guide replaces the first-start card and the checklist

    A fresh install opens on the dashboard with its example links; after a moment a Quick start bar slides in at the bottom with a soft pulse, and opens a modal in the middle. The modal holds the choice about the example links (Keep or Start empty, which asks before it removes anything), links to the manual and the theme studio, the language (it changes the dashboard and the guide at once, without a reload), the weather (a city and °C or °F, saved as the same settings Config uses) and nine next steps, in the order a reader would take them: take the tour; import bookmarks and get the browser extension; open the Bookmarks view and the Inbox; add a widget; turn on status checks and set up notifications; open Config → Overview. Three steps show at a time, the rest behind Show more. The modal opens by itself only the first time, three seconds after the bar is up, and from then on when the bar is pressed; Esc, a click outside, Close for now and the answers fold it back into the bar, which glows once so the eye finds it. The bar stays on the dashboard of page 1 (hidden in Config, other views and other pages) until every step is done, then says All set and waits for a click, or until it is closed for good with ×, which asks first. No other corner card is shown while it is there, and the non-essential ones wait fifteen minutes after it is finished (quickStart.completedAt); an Undo for something just done still shows, and the bar steps aside for it.

  • New
    a fresh install does not get cards that the guide already covers

    The Confetti invitation, the clock-and-weather question, the theme-browser invitation and the automatic dashboard tour start answered on a new install; the tour is the guide's first step. An existing install keeps all of them. Config → Reset onboarding starts the guide over, steps included.

  • New
    Config → Containers has a Tour button

    On its band, where Widgets has one: it plays the Containers view's tour, seen or not (data-containers-tour).

  • New
    the dashboard tour starts with the action bar

    A new first slide shows the nine buttons with their keys (+, >, :, ?, /, *, ,, ., !), the bar docked at the edge of the page, where it stands and slides away by default, and how it comes back (' or Shift+O). The tour is eight steps now; the tip id is unchanged, so a reader who has seen it is not shown it again, and it plays from Config → Help or Shift+K.

  • New
    the start card has two more buttons

    Show me the manual first opens nextdash.cc/docs in a new window and Open the theme studio opens the theme browser. Neither answers the card, which stays until a choice is made.

  • Fix
    the mobile info banners are gone

    from the dashboard and from config.

  • Fix
    config no longer greets a fresh install with a keyboard tip

    The In config: j/k… tip that popped up the first time config opened is gone; the same tip stays in Help → Tips.

  • Fix
    Space between columns applies to the default layout

    The default layout kept its own 1.5rem column gap, so Airy (and Confetti, which follows the theme to airy) moved only a wide category's inner columns and left them off the grid. The gap now follows the setting.

  • Fix
    Space between columns is not shown as changed on a fresh install

    Its default is Follow the theme; Config → Appearance compared it with Balanced and put it first in the folded summary.

  • Fix
    the terminal layout hides the category handle again

    under the clean header styles, where the grip drew back in and caught Tab.

Themes and looks

  • New
    twenty-four colour-burst theme families

    , a collection named Looks (look-ember to look-holo), added to the New set. The theme browser gains a New segment next to All, Favourites, Light, Dark and Yours.

  • New
    three backdrops: burst, splash and leak

    A burst fans the theme's colours round one point, a splash is four large soft blots, a leak is light coming in from an edge. They are loud, so each is drawn over a scrim floor of theme tint (0.24, 0.22 and 0.2) that the reader's own Theme tint can raise but never go below. The hash that picks a backdrop for a theme still covers only the original 26, so no existing theme moves; the new three are reached by naming them.

  • New
    categories and widgets sit on glass, a card or open

    Appearance → Surfaces → Category surface (and the theme studio's Surface tab) chooses what a category and a widget stand on: a see-through pane, a solid card, or nothing at all. Follow the theme lets each theme bring its own, as with depth and glow; flat depth defaults to open. It has its own ↺ and ℹ like depth and glow.

  • New
    Widget background

    On an open category surface nothing framed a widget any more, and it looked like a category with another title. Appearance → Surfaces → Widget background (and the theme studio's Surface tab) chooses whether a widget draws a background of its own: Automatic (the default) makes it a card exactly where nothing else frames it, on open: a faint fill, a hairline and a shadow round the widget, and its title on a strip of its own with a line under it, the // inside it; Background always, also on glass and card (where the pane is the card and only the title strip comes); None never. Automatic follows the surface the page is drawn with, not a list of themes, so whatever makes a theme open (its own answer, paper, velvet or terminal, flat depth, or a surface you choose for one theme or for all) gives its widgets the frame; a category given a pane of its own card glass is framed already, and automatic steps back. The answer reaches the first paint from the server (data-widget-bg), and settings.widgetSurface is auto | background | none Widget opacity, a slider next to it, sets how solid that card is, from 0 to 100% of the theme's surface colour, 50% by default: the card is mostly solid, so a widget reads as a card on any backdrop, and the title strip is a little more solid still (settings.widgetOpacity, --widget-bg)..

  • Fix
    the // stands in the title again

    A category hung its // in the gutter left of the column, where a neighbouring column's // ran over the edge of a widget's card; with four columns or more that was most widgets. The // is back in the title's row, for categories and widgets alike, and the card no longer has to keep clear of anything.

  • Fix
    a widget's title strip runs to the edge of its card

    The strip and the body sat inside the category's side padding, so the card's border showed as a gap round the strip. Both now run to the edge, and the text lines up with the title.

  • New
    Slate is rich and open

    The default theme, Slate (dark and light), now has rich depth and an open category surface, so a fresh install shows categories without panes and widgets as cards. A reader who chose a depth or surface for Slate keeps it.

  • New
    Backups & data reads top to bottom

    Config → Data & backups → Backups & data opens on a status (Your data is backed up, or No backup yet, or that the last automatic run failed) with Back up now and Download beside it and four figures under it: how many are stored, the size of the newest, what they take on disk and the bookmarks in it. Under that three groups, nothing folded away: Protect (automatic backups with their interval, local copies of pages, tokens and passwords), Restore (from a file, and the stored backups with Restore, Download and Delete) and Move (bookmarks as HTML or CSV or from a browser, and settings as JSON). The explanation that used to sit under each control is behind an ℹ on it.

  • Fix
    pointing at a category or widget header tints all of it

    The tint covered only the part inside the block's side padding, so on a pane or a widget card a strip of the header stayed untinted, and a widget's title strip lost its fill and shrank from the left. The tint now runs from one edge of the block to the other, up to its top edge on a pane (which has padding above the title), a widget's strip keeps its fill and gets a little lighter and on a pane sits flush with the top of the card, and the text and the accent tab on the rule stay where they are.

  • New
    Gloss Chrome and Gloss Amber open on an open surface

    Both (dark and light) now start with glass depth, an open category surface and glow off, so their categories sit without panes and their widgets are cards. A reader who chose a depth, surface or glow for them keeps it; the other Gloss themes are unchanged.

  • New
    the Health and Trend widgets of a new install sit at the bottom

    A fresh dashboard opened on two widgets above the links. They now close the page, below the categories, and the example note takes the top right, so the first thing seen is what the dashboard is for. Existing installs keep their own order.

  • Fix
    the Appearance settings line up

    In Theme & type every row now ends on one edge: the theme picker with its button, Quick mode, the toggle, Random theme and the theme editor, and the ℹ column stands in one place. In Surfaces Widget background and Widget opacity sit in the same control column as Depth, Glow and Effects; they started further right, and the opacity note stood beside the slider instead of under it. The button next to the theme picker is now Open theme studio.

  • New
    a widget is told from a category on glass

    On a glass or card surface a widget and a category were the same pane under a different title. A widget's title now sits on a lighter strip with a line under it, flush with the top of its pane; its handle is a small panel instead of the two slashes. Categories keep their slashes. Appearance → Surfaces → Widget background is Background (the default) or None now, because Automatic only ever differed on glass and card, and a stored Automatic reads as Background; on an open surface the widget is still a card as well. A collapsed widget closes to nothing again, strip aside. A plain page load also puts the answer on the body now, where the stylesheet reads it: until a setting was touched, the strip was not drawn.

  • Docs
    the manual follows v1.20.0

    First launch describes the Quick start bar and guide, the ten example links in the inbox and the new example page layout; Surfaces gets Widget background and Widget opacity; Layout gets Space between columns; Commands lists the new palette words; Data & backups is rewritten for the new tab; the tour has eight steps. New and retaken screenshots: the first launch and the guide, Backups & data, Surfaces, Layout spacing, Appearance, the Server tab and every widget tile. The texts that still named the quick-start card or its checklist (the Show quick start again button and its hint, three Help panels) are corrected in all six languages.

  • Docs
    Config → Help and the translations are up to date

    Seventy strings that only had an English fallback (the start guide, Backups & data, Widget background and opacity, the Containers tour hint) are in en.json and translated into Dutch, German, French, Spanish and Chinese, and Browse… beside the theme picker reads Open theme studio in every language. Help describes the Quick start bar and guide, Open theme studio and the Surfaces settings (widget background and opacity), Space between columns, the new Backups & data tab, the widget's strip and handle, the new palette commands and the example links in the inbox (locales/).

  • New
    a new install has ten links waiting in its Inbox

    The Inbox was an empty view with a count of zero on day one. It now holds ten unread links to read, keep, promote or throw away (Caddy, Healthchecks, restic, Syncthing, Paperless-ngx, Immich, the Twelve-Factor App, SQLite, systemd and Julia Evans), with their preview text written in, so the list reads well without the network. None of them is on the starter pages. Start with an empty page in the start guide takes them away with the example links, except one you have already read or put to sleep; Reset all data puts them back; the minimal seed and the demo have none.

  • New
    a card points to the theme studio

    A one-time card in the corner names Shift + A and the two tabs a reader most often wants, Surface and Layout, and opens the studio on request. Everyone is asked once. A new install is not greeted on its first day: the card waits a day from the moment the settings file was written (firstRunAt), and an install without that stamp is asked at the next quiet moment. The card is translated into all six languages and has a spec of its own.

  • New
    the Quick start grows out of its bar

    On a first visit the guide opens by itself, three seconds after the bar is up, and only that once in a browser. Opening the guide, the window now grows from the bar in the corner to the middle of the page, and Close for now, Esc or a click outside folds it back into the bar the same way. With reduced motion, or animations off, it opens and closes at once.

  • New
    Confetti draws its category headers clean

    Category header → Style is one setting for the install, and on Follow the theme a theme may now state a header of its own: Confetti (dark and light) shows the name alone. Every other theme keeps the header it had, and a style you pick yourself is never replaced. Switching theme moves the header with it, and the first paint has it.

  • New
    Confetti is airy between columns

    Space between columns has a new first choice, Follow the theme, and it is the default: balanced everywhere, except on Confetti (dark and light), which draws its columns airy. A spacing you pick yourself is never replaced. Space between categories already reads balanced there, so it is unchanged.

  • New
    Confetti is airy between categories too

    Space between categories gets the same first choice, Follow the theme, as its default: balanced everywhere, airy on Confetti.

  • Fix
    Page margins now move the columns

    The columns stop growing at a width and a wide window centres them, so Snug, Balanced and Airy only moved the page title. Snug now lets a column grow to 460 px, Balanced keeps 360 px, Airy pulls them in to 300 px.

  • Changed
    A fresh install starts on medium type

    The default font size is M instead of Large medium; an install that has a size keeps it.

  • New
    Space between columns

    Appearance → Layout gets a second spacing setting beside Space between categories: Snug, Balanced (the default) or Airy for the room across the page, between one column and the next (12, 24 and 40 px). Space between categories only ever set the room down the page, and across it a masonry page had a fixed 1 rem. It is in the theme studio's Layout tab as well, and :columngap in the palette sets it. The default is 24 px, so the columns of a page that never chose move 8 px apart (settings.columnSpacing, data-column-spacing).

  • New
    the Surfaces settings in the palette

    :surface (Category surface), :effects, :widgetbg (Widget background) and :widgetopacity join :depth and :glow under Look & layout, so every setting in Appearance → Surfaces can be set from the keyboard.

  • New
    defaults per theme character

    Every built-in theme of a character ships with the same surface settings: aurora with glow Off, opacity 20% and glass panes; paper with open panes, opacity 20% and the glass depth (glow Off); carbon with the glass depth, glass panes and effects Off; ink and neon with the glass depth, glass panes and opacity 20%; enamel at opacity 20%; lacquer with the glass depth, glass panes and opacity 35% (the Looks that use it keep 20%). They are the theme's own defaults: a theme file already saved on disk keeps the values it has.

  • Fix
    a row's highlight strength shows when it is chosen

    Changing the row highlight strength lights the first visible bookmark row for a moment in the strength just picked, so the choice is seen without moving the pointer off the panel.

Categories and widgets

  • New
    tiles per category

    A category's menu has Show as tiles / Show as rows. Tiles draw the bookmarks as a grid: a large icon, the name under it, the status as a dot on the corner and the response time small below the name. The DOM is the row's, so drag, the context menu, the keyboard and inline editing work as in a row. Terminal and launcher keep their own designs.

  • New
    icons live in titles

    A category used to have an icon field; the icon is part of the title now. An emoji typed in the name is text; an app icon is written :file.svg: (a file in data/icons/), drawn as the image it names, and the category menu has Insert icon…. Categories and widgets are titled the same way, and only the words are lower-cased, so a file name keeps its case.

  • New
    Settings from a widget opens that widget's settings

    Its row opens and every other row is closed, the search is cleared and the list moves to the widget's page, so it is clear which widget the fields belong to.

  • Fix
    a category title starts where a widget's does
  • Fix
    the + that adds a category now shows where the name goes

    It opened a name row at the end of the grid and hid itself, so on a long page the click seemed to do nothing. The row is scrolled into view, for the c key as well.

  • Fix
    a popover answers from the moment it opens

    The outside-click and Escape handlers of the action popovers (row tags, move, delete, and the multi-select Tags one) were bound on a 0ms timer, and a click or key a few milliseconds after the popover appeared was handled before they listened, leaving it open. They bind at once and skip the event that opened the popover by its time stamp (_bindActionPopoverOutsideClose).

Config

  • New
    Config and the list views are panes

    Config drew flat rectangles and left its tables bare, so it read as another application. Its panels, overview cards and tables now take the pane the dashboard draws, the same glass, card or open (open keeps a light frame); selects and inputs stay fields. The tag view, inbox, containers view and bookmarks view are one pane each, and the header of a list view is the top of its pane at rest, turning solid when rows scroll behind it. Config has two arrangements: loose panes (the default) and one pane round everything (data-config-panes="one"). The opening text of a tab is a pane too.

  • New
    Help tabs in labelled groups, one row

    The fifteen tabs sat on one scrolling line, hiding most of them. The row keeps Basics; Dashboard, Status & checks and Data are a menu under More topics.

  • Fix
    room under field notes

    The gap between a control and the sentence under it is one token, --config-note-gap (it had been a −4px margin against a 4px row gap, which left nothing).

  • Fix
    Share this page and Import a page are themed buttons

    in the page-template modal.

  • Fix
    the rows of a widget list no longer sit on a lighter band

    The rows of Health, its trend and the forecast were filled 9% lighter than the pane, so a few lines of text looked to have another background. They are unfilled now, with a hairline between them and a light wash when pointed at; the figures of a stats widget keep a faint chip (4%).

  • Fix
    a click on a row in a widget leaves no ring round it

    The keyboard cursor follows focus, and a click focuses the row it hit, so the cursor's 2px ring appeared round every clicked row. The ring now shows only when the cursor got there by key.

Statistics

  • New
    a Server tab

    Six figures and panels for the machine behind the dashboard: containers running, unhealthy and waiting for an update, crashes over thirty days, container trouble and updates per day, the most restless containers, memory and CPU now with the total, Docker disk use by images, volumes, build cache and stopped containers (and what could be freed), the Unraid array, disks with temperature and read errors, parity, VMs, UPS and notices, automatic backups and container updates. A panel without a connection says what is missing and links to where to set it up. Overview's Needs attention gains server lines: unhealthy containers, waiting updates, an Unraid disk with errors, disabled, missing, hot or full, and a late or missing automatic backup.

  • New
    a Notifications panel on Health

    open alerts and how long they have been down, what is held in quiet hours, push devices, webhooks, the alert service and the last weekly digest. How many were sent is not recorded.

  • New
    widgets by kind and per page on Collection
  • New
    one route for every container's last thirty days

    GET /api/docker/history returns the fleet's events, update history and last disk measurement in one read, instead of asking the drawer's route once per container. Nothing new is stored.

Keyboard shortcuts sheet

  • New
    two columns

    The sections sit side by side (one column below 40rem) instead of in one long column, so the sheet fits a window without scrolling past every section (.cheat-sheet-groups).

  • New
    find by key or section

    The filter also matches the key chips and the section name, and ignores spaces, so shift + y finds Shift+Y and tag view shows the whole Tag view section.

  • New
    topics

    A row of chips under the filter narrows the sheet to Navigation, Bookmarks, Views, Search and commands, or Other, and opens every section of that topic. Typing in the filter still searches all topics.

  • New
    the view's own section leads

    Opened from a view with a section of its own, that section moves to the top and spans the full width instead of sitting somewhere in the grid.

  • New
    / jumps to the filter

    , next to Ctrl/Cmd+F. The filter stays at the top while the sections scroll.

  • Fix
    easier to read

    Section titles are larger and no longer all lowercase, each shows how many shortcuts it holds, and the rows have more room.

Dashboard titles

  • Fix
    widgets are not headers

    v1.19.10 made a widget's title a strip on the card's own surface, joined to it. That is gone: the title is a title over the card again, as a category's is over its list (.dashboard-widget >.category-title and its collapsed-state rule are removed).

  • Fix
    the // sat in two places

    A category hung it in the gutter left of the column and a widget kept it in the row, so a page with both had two columns of them. Both hang it at the same place now, 24.4px left of the block (.category-reorder-handle, one rule for both). The row's own start padding moved from the label to the icon and the name, which is what lets the // sit alike.

  • New
    a widget's name starts on its card's content

    The card's border and padding in (1px + --space-3), where the first line of the card starts; a category's name starts in the same place, so a page of both keeps one left edge for titles.

  • Fix
    a title jumped when pointed at

    The general hover grew the title 4px to the left (padding and a negative margin) and painted it with the background shorthand, which also took the accent tab off the rule under it. Pointing at a title now tints it where it is, with a background colour, and the tab stays. The old tint was never drawn on the dashboard at all: it read --hover-bg, which only exists inside Config. It is --text-primary at 7% now.

App discovery

  • Fix
    Remove on the ignored list sticks when a run is going

    A discovery run copies what it knows before it probes and saved that copy back afterwards, so a Remove made in those seconds was undone and the app was never offered again. The run now leaves out names taken away while it probed.

  • Fix
    Undo all on the notice can be tried again

    When one of several undos failed, a second click hit the ones already taken back and stayed on Could not take it back. Undo now counts those as done, retries only the rest and ignores a second click while it runs; Move keeps the notice when it cannot find the new bookmark, and a failed refresh is tried again on the next check.

  • Fix
    the question about new apps opens once

    The start timer and a return to the tab could both open it; the second now waits for the first.

  • Fix
    a double click on Promote makes one category

    Promoting an app proposal from the Inbox looks up its category first; a second click in that moment created it twice.

  • Docs
    two new tests guard these fixes

    TestDiscoveryUnignoreDuringRunSticks does a Remove in the middle of a run (through discoveryBeforeSaveHook), and Undo all on the notice tries again only what a failed Undo left in tests/app-discovery.spec.js fails the second of two undos; both fail without their fix. go generate refreshed asset_hashes_gen.go.

Docs

  • Docs
    147 interface strings that only existed as English fallbacks in the code are now in all six locale files

    (the Confetti card, the category menu, Statistics → Server, Notifications and Widgets, the Help tab groups, the category surface), translated into nl, de, fr, zh and es; validate:locale-parity could not see them because the keys were missing everywhere, not in one file.

  • Docs
    Config → Help follows this release

    188 theme families and the Looks collection, Confetti as the starting theme, 29 backdrops, the category surface, six Statistics tabs with Server, tiles and icons in titles, in six languages; the matching tips carry the new counts.

  • Docs
    static/data/whats-new/v1.20.0.json and its index entry

    , with two highlights (Confetti and the new Looks, the Server tab) and their pictures under static/data/whats-new/media/; whats-new-stub.js moved DASHBOARD_RELEASE to v1.20.0, which leads the window again, and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v342. v1.19.10 and v1.19.11 lose their hideFromModal, so every release shows in the window again. tests/whats-new-hidden-release.spec.js names v1.20.0 and expects nothing held back.

  • Docs
    static/data/whats-new/v1.19.11.json and its index entry

    (hideFromModal); whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v341, DASHBOARD_RELEASE stays on v1.19.9. tests/dashboard-title-alignment.spec.js covers the // position for a category and a widget, the missing strip and the hover (it fails on v1.19.10's CSS); tests/whats-new-hidden-release.spec.js names v1.19.11 as held back next to v1.19.10. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.19.10 Category and widget titles are redrawn: they keep their size, line up with the bookmarks under them and outrank them, and a widget's title becomes the head of its card. +3 4 fix

Category and widget titles are redrawn: they keep their size, line up with the bookmarks under them and outrank them, and a widget's title becomes the head of its card. One Config button loses a stray underline. Held back from the What's new window (hideFromModal) like v1.19.1–v1.19.2, so v1.19.9 keeps leading it.

Dashboard titles

  • Fix
    a category title shrank for no reason

    dashboard-category-title-fit.js read the label's overhead as label.clientWidth − name.clientWidth, but .category-title-label is flex: 1 1 auto and stretches over every free pixel, so the empty room counted as overhead and even a three-letter name "missed by a pixel" at full size and was stepped down (vps ended at 15 px under 16 px bookmarks). The label is now measured shrunk to its content (readLabelOverhead), the title's own padding is taken off the room, and the label's negative margin is given back. The bug dates from 23 September (4802f509), when the fit started to work at all.

  • Fix
    the //, the icon and the name sat on three different lines

    .category-title-name is an inline-block with overflow: hidden, which rests on its bottom edge instead of its text, so it rode about 5 px above the // and the icon and left that much empty room before the rule. The label is now a flex row with align-items: baseline; the icon keeps the space after it (white-space: pre), and so does the terminal layout's $ . A title is 5 px shorter (34.1 → 29.1 px) with 5.6 px between the text and its rule.

  • New
    a title lines up with the bookmarks under it

    The // now hangs in the gutter left of the column (still the drag handle, still reached by Tab), the icon sits on the bookmarks' icon column and the name starts on their text, with or without an icon. Default and masonry layouts with the theme's own header style, from 601 px; the other header styles, the terminal layout and anything below 601 px keep the // in the row, because their grips are drawn differently or the page edge is nearer than the hang. The // is a real box (1.6em, given back by a negative margin) so it can still be pointed at and picked up, and a wider icon keeps its own width (min-width).

  • Fix
    a click on the // could move the block

    Hanging in the gutter put the handle on the seam between two columns, so a press that jiggled a couple of pixels dropped the block there. A press that does not travel 6 px is now a click and drops nothing.

  • New
    a title outranks the bookmarks under it

    The title takes the primary text colour and a short accent tab on its rule (not at flat depth, which draws no rule); bookmark names go from semibold to regular. Slate, the default theme, asks for a title weight of 700 (LabelWeight); every other theme keeps its own --theme-label-weight.

  • New
    a widget's title heads its card

    In the default and masonry layouts the title is a strip on the card's own surface, joined to it with no gap, with the card's top corners square; a collapsed widget closes the strip's bottom edge (.category-title[aria-expanded="false"]). The // stays in the row there.

Config

  • Fix
    Status page → Open was underlined

    It is an <a class="config-btn"> next to two buttons, and .config-btn never reset text-decoration. It does now, which also covers any other link drawn as a button.

Docs

  • Docs
    static/data/whats-new/v1.19.10.json and its index entry

    (hideFromModal); whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v340, DASHBOARD_RELEASE stays on v1.19.9. tests/whats-new-hidden-release.spec.js names v1.19.10 as the held-back release, and the reference fit in tests/category-title-fit-batched.spec.js reads the label's overhead the way the fit now does. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.19.9 Changes in App discovery, First start, Themes, Appearance, Search, Import and Inbox. +10 19 fix

Changes in App discovery, First start, Themes, Appearance, Search, Import and Inbox.

App discovery

  • New
    nextDash finds the apps running in your Docker containers and offers them as bookmarks

    A container counts when it answers with a web page or a login, probed from where the server itself reaches. The address comes from the nextdash.url label, a reverse-proxy label on the container or a published port, and a port link follows the host you opened nextDash on. Each app gets a kind (Media, Downloads, Monitoring and so on), an icon, a status check and a link to its container. Discovery talks only to the Docker socket and its own probes, never to a proxy's or another container's API.

  • New
    the "apps found" card

    On a dashboard with the Docker integration, a card in the middle of the screen lists what was found, grouped by kind and all ticked. Add puts the ticked apps on the page: new categories go to the top and light up, and a notice offers Show, Undo and Done. An optional "Replace the starter links" box is off by default. The card comes last: after the first-start card, the checklist, the dashboard tour and every corner card that can show, and never alongside a modal.

  • New
    a new container later is asked about first

    The same card asks with Add, Ignore and Not now (POST /api/discovery/accept). Config → Containers → View has two other choices under New apps: Add straight away, with an Undo, Move and Done notice, or Propose in the Inbox, where Promote fills in the bookmark form and Ignore keeps the app away (discoveryNewApps).

  • New
    Config → Containers → View: Suggest new apps, New apps, and the ignored apps

    each with Remove, so nextDash notices that app again (discoverApps, discoveryIgnored).

  • New
    container labels steer it

    nextdash.url sets the address and wins over everything else, nextdash.name the name, nextdash.category the category, nextdash.icon an icon-set name or image URL, and nextdash.hide=true keeps a container out.

  • Fix
    new means never seen

    A container that was already there when discovery first looked is not proposed again as new, and a container that already has a bookmark is matched on the server the same way the browser matches it. A settings save from a browser no longer overwrites what the server wrote (discoveryCardDone, discoveryIgnored, dockerHostSeen). Undo also works while the quick start is open.

  • Fix
    the New apps panel no longer offers Reset panel on a fresh install

    An unset choice reached the browser empty, which differs from its default of Ask first, so the panel counted as changed and Config → Overview listed it. The server now sends ask for an empty or unknown value (normalizeDockerSettings, TestDiscoveryNewAppsChoices).

  • Fix
    the page goes quiet on the network after it loads

    The host the dashboard was opened on is reported once per load, and that request's answer was never read, so Chromium kept it open (reportHostSeen).

First start

  • New
    a fresh install starts with 98 English-language links on two pages

    Main holds Development, Docker, Unraid, Self-hosted, Tools and Daily, with the health, trend and notes widgets; news holds tech news, dev blogs, security, communities, homelab videos and a few general news sites. nextDash is in it twice: nextdash.cc and the GitHub repository. Today shows on main only. Existing installs are untouched, and a data folder that already has a page never gets the second one. The e2e server and the Go suite keep the old one-page set with NEXTDASH_SEED=minimal.

  • New
    the first-start card asks what you want: keep the example links, or start empty

    Starting empty takes the starter links off main and removes the news page, as long as nobody changed it; the page tabs follow without a reload (POST /api/onboarding/start-empty, isUntouchedSeedPage). The bundled templates are now only in the import dialog.

  • Fix
    starter icons are fetched for every starter link

    The first-start icon round stopped at the first batch where no fetch succeeded, and ran into the shared outbound limit after about thirty links, so most of a larger set stayed letter tiles. It now steps past links without an icon, waits for room in the limit, and retries a batch the limit refused (prefetchStarterPageIcons).

  • Fix
    corner cards wait for the move intro

    A card such as Clock and weather or analytics could take the corner a few seconds after load, and the intro that shows how to move categories and widgets then waited behind it. While the intro is still to play in this visit, the cards hold back, and they come once it is answered or gives up (DashboardBlockMoveIntro.isPending, cornerIsFree).

  • Fix
    after "Try it" on the move intro the page answers the mouse again

    Try it picks the block up with the keyboard, and the "Moving a block" card then let every click through, as it does under a dragged block, so Got it could not be pressed and the // could not be dragged; the grabbing hand showed all over the page. While a block is held with the keyboard the card now takes clicks, Got it puts the block back and closes the card, a press on a // starts an ordinary drag, and the grabbing hand shows only while the mouse holds a block (showCoach, is-moving-block-by-pointer).

Themes

  • New
    Slate is the theme a fresh install starts on

    Blue-grey stone behind a pane of glass, drawn at glass with a soft glow; auto dark mode switches to Slate [light]. Existing dashboards keep their theme. Server and first paint agree (defaultThemeID, defaultThemeLightID, ThemeLoader.DEFAULT_THEME); MANUAL §16.1 and Config → Help name it.

Appearance

  • Fix
    code, addresses and shortcuts use Source Code Pro

    Text set in the mono font (code, URLs, shortcut chips, the terminal layout) fell back to the system's monospace, such as Menlo, because --font-family-mono was never defined. It now defaults to Source Code Pro. A mono font you or a look pick (JetBrains Mono, IBM Plex Mono) carries it along; a sans font such as Inter keeps code on Source Code Pro.

Search

  • Fix
    clicking the "Press / to search names" hint runs that search

    The click kept its own copy of what Enter does and had no branch for the hint, so it closed search and threw. A click on any row now goes through the same dispatch as Enter, and Ctrl/Cmd+click opens a bookmark in a new tab everywhere (SearchComponent._activateMatchAt).

  • Fix
    Tab and Shift+Tab leave the scope's own prefix behind

    Shift+Tab from tags opened finders on ?tag:, and Tab from a finder line turned the finder's shortcut into a tag filter (_scopeWord).

  • Fix
    the bookmarks heading counts bookmarks

    It counted rows, group headings and filter completions included, and missed what a closed or capped group holds (_resultCount).

  • Fix
    a shortcut that opens as you type it is not kept as a search

    It filled Recent searches and the search picks with the shortcut.

  • New
    status: completes untagged, tagged, noted and unnoted

    The filter knew them; the completions and the filter hints did not, and the empty state and the inline hints described status with different lists (filterHintText, one list for both).

  • Fix
    the screen-reader position ("3 of 12") is translatable

    (dashboard.searchAnnouncePosition).

Import

  • New
    an import asks where the bookmarks go: onto the dashboard, or into the inbox first

    A browser file, a CSV and a source round all show the same choice, with what each answer would add and skip. Into the inbox, a folder becomes a tag instead of a category, and a link the dashboard already holds is skipped. Restoring a backup does not ask. The dry run counts both answers (ImportPreview.inbox); ?inbox=1 sends the round to the inbox (importRowsToInbox, AddInboxLinks, one write for the whole file).

Inbox

  • Fix
    a found app reads on one row

    Its name stands in the title column with a found on this server pill and its kind under it, and Promote and Ignore take the tags column, with a green edge on the row. The source, kind and buttons had fallen into the narrow first column and wrapped word by word.

  • Fix
    Clear filters clears the address too

    It reset the view without going through applyViewChange, so ib_q, ib_domain and ib_tag stayed in the URL and a reload put the filters back.

  • Fix
    read and unread follow the server again

    A mark unread here, then read on another device, stayed unread in this tab until a reload, and the other way round. The local override now lasts only until a list read that started after the write (_rememberReadState).

  • Fix
    an emptied "With a tag suggestion" filter no longer says Inbox zero

    It has its own empty state.

  • Fix
    applying suggested tags no longer overwrites tags written in between

    One batch per tag adds on the server, instead of a PATCH per link with the whole list (applySuggestions).

  • Fix
    opening a link that is already read sends no new read mark
  • Fix
    an import in the demo names the links it pushed out

    Only the demo has an inbox limit (demoInboxLimit); elsewhere nothing changes.

Docs

  • Docs
    the page switcher picture in the manual is larger and centred

    It was a small crop floated beside the text; it is now taken at twice the pixels and shown centred at 560 px.

  • Docs
    Config → Help and its tips cover this release, in all six languages

    A new Containers panel, Apps nextDash finds on its own (helpContainersDiscoveryBody), covers the first card, what happens to a container that turns up later, the ignored apps and the labels. Getting started describes the new first-start card, Themes names Slate and Source Code Pro, Backups, import & export describes the import's destination question, and Config → Containers lists the View tab's two new panels. Three new tips: tipHostDiscovery, tipHostDiscoveryLabels and tipAddImportDestination.

  • Docs
    every manual screenshot is taken in Gloss Chrome dark

    SHOT_THEME puts the theme into each copy of the demo data; the demo keeps its own. Three scenes that broke since the last run were fixed (the More menu around the character chips, the new first-start card, the tag view's offers).

  • Docs
    the manual as a website

    site/ builds nextdash.cc/docs/ with VitePress from MANUAL.md: one page per chapter, the Mermaid flowcharts drawn, a reading layout with captioned figures, a Pagefind search index and a deploy script. site/ stays off main and out of the Docker image (PRUNE_DIRS, .dockerignore).

  • Docs
    nextdash.cc on its own WordPress theme, Werkbank

    In the docs' colours and type: a homepage that moves, News with the releases, a features overview with pages for the media widgets, tags and appearance, a theme gallery on Theme studio, one search box over the docs (Pagefind) and the site, and light and dark following the system, one choice for site and docs. New logo files from the app's >_ icon and a new share image. Searches count once in Umami, docs included.

  • Docs
    nextdash.cc has an App discovery page and a compare page

    The feature pages for Install, Containers, Inbox and Data carry this release's changes, and the compare page sets nextDash next to six other dashboards, linked from the homepage, the footer and the features index.

  • Docs
    the manual covers app discovery

    A new §14.10, Apps it finds on its own, with three screenshots (the apps card, the card for one new container, and Config → Containers' New apps and Ignored apps), the New apps choices and the nextdash.* labels; the self-hosted guide, first launch, §13.1, §17.7, the troubleshooting chapter (No apps are offered) and the glossary point to it. §19.1 describes the import's destination question, and §16.4 the mono typeface for code.

  • Docs
    the manual's first launch describes the new start

    the "what do you want?" card, with its screenshot retaken on a fresh install.

  • Docs
    the manual explains installing on Unraid from Community Applications

    in a new section of the install chapter.

  • Docs
    the v1.19.4 Jellyfin recording in What's new is retaken from a real server

    Its plan finds the widget by its type, and the manual's dashboard screenshots wait for the media widgets to load.

Tests

  • Tests
    health_badge_test.go seeds the uptime history oldest first

    , the order the history file keeps it in. Newest first, the badge counted samples twice whenever the span crossed UTC midnight, and the test failed around that hour.

  • Tests
    dashboard-block-move-intro.spec.js no longer depends on test order

    Answering the intro used up the day's tip and the locked-layout test left the layout locked on the shared server, so "Try it" and "a key press during the animation" failed after them. The helper lifts the tip limit, and the new corner-card test unlocks the layout first.

  • Tests
    the specs follow this release

    app-discovery.spec.js finds a placed link outside Today, which now shows a link added today on main, and finds an inbox proposal by its heading, since the row shows the app's name; config-containers-tabs.spec.js knows the New apps and Ignored apps panels; config-info-reset.spec.js lets the New apps pair explain itself through its panel note; whats-new-hidden-release.spec.js has v1.19.9 leading. Seven fixed waits that check something does not happen say so (validate:test-waits), and default_seed.go is gofmt'd.

  • Tests
    widget-theme-tint.spec.js measures on the theme it was written for

    The meter track takes a share of the theme's ink, and Slate's blue-grey one pulled the brown test page just under the floor; the spec applies matrix-bluepill-dark in its own page, without saving it.

  • Tests
    "Got it" in dashboard-block-move-intro.spec.js checks the reload for real

    The spec's init script asked for the intro again on the reload, so the fixture took the tip out of what the server sent and the intro played again; the test passed only while its card came later than the six-second wait. After the answer the reload asks for nothing, and the test also checks that the intro is not running.

Only docs and tests changed in this release.

v1.19.8 Changes in Dashboard, Widgets, Tags and Settings. +25 10 fix

Changes in Dashboard, Widgets, Tags and Settings.

Dashboard

  • New
    the page filter stays at the top on a phone

    Shift+F narrows the page you are on, and a phone has no Shift+F, so the phone layout keeps the filter bar above the bookmarks from the first paint. It does not take focus, so the keyboard stays down until you tap it; the × and Escape empty it rather than close it, and the × only shows while there is something to clear. Full width, 44px tall and 16px text, so iOS does not zoom in on focus. Leaving the phone layout drops an empty bar and keeps one that is still filtering.

Widgets

  • New
    Jellyfin: now playing

    A second Jellyfin tile shows who is watching what right now and how far along they are; it refreshes every 10 seconds by default.

  • New
    Emby widgets

    Emby (what was added lately, with the real posters) and Emby — now playing, read through the same client as Jellyfin: Emby is where Jellyfin came from, so only its paths differ.

  • New
    Plex widgets

    Plex (what was added lately) and Plex — now playing, read through Tautulli: its API key only reads, where Plex's own token opens the whole account. Pictures come through the server, so the key never sits in a page.

  • Fix
    media tiles refresh on every beat, without the loading line

    A media tile showed Loading… between readings and, kept a TTL from its answer, refreshed only every other beat; it now redraws in place each time.

Tags

  • New
    self-hosted apps are recognised by name

    A Sonarr at 192.168.1.20:8989 or sonarr.home.lan sits at an address no catalogue can list, so 217 self-hosted and local apps are now known by what they are called: the host's first label, a whole word in the bookmark's name or the page title, and on a private address the app's default port. Each gets #self-hosted and one tag for what it does (#media-server, #usenet, #smart-home, #networking, #monitoring, #nas and so on). An everyday word (Flood, Element) or a generic label (cloud, chat) only counts on the home network, and a port two apps share with different tags counts for nothing. One row and one refusal per app; the chip says Recognised as Sonarr. The list is internal/app/tag_apps.json, served with the catalogue.

  • New
    seven subjects

    ai, nas, files, downloads, productivity, reading and 3d-printing, with 98 sites between them. torrent and usenet now sit under downloads, rss and read-later under reading, the notes and task subjects under productivity. They live in scripts/tag-catalogue/subjects.json, written in by apply.cjs.

  • New
    40 more sites for subjects that missed them

    the cloud consoles and app platforms under cloud, the language registries and container registries under package-manager, and the guides and lists self-hosters read under self-hosted.

  • New
    the broad subjects split into finer ones

    The nineteen biggest subjects held most of the catalogue's 56,000 sites, so a tag said little. Their sites now move, by what Wikidata says each one is, to 58 finer subjects under them: airports and airlines under flights, newspaper, online-news and news-agency under news, municipality and police under government, game-studios and video-games under games, car-brands, tv-series, college, medical-school, the big football leagues and many more. 16,288 sites moved; schools, museums, casinos and restaurants that sat under charities or hotels went where they belong. Whoever already tags the broad subject keeps being offered it. split-facts.cjs shows what a subject is made of, split.cjs asks Wikidata per class and writes manual/splits.json, and splits.json says which class goes where.

  • New
    tech, internet, science and social

    New subjects tech, tech-news, hardware, smartphones, internet, infosec-news and science-news, with some 140 sites. The well-known tech sites had been filed under online news, magazines or, in one case, fan fiction. The big social networks are under social. android, ios, macos, linux, windows and electronics now sit under tech.

  • New
    a section of a site can have its own subject

    The catalogue can name a host plus its first path segment, so youtube.com/@veritasium is science while YouTube itself is video. 65 tech, homelab and science channels are in, each checked to exist; a bookmark on a channel is not also offered the site's subject.

  • New
    dev and tech in depth

    65 developer subjects with their official sites: languages (typescript, kotlin, elixir, zig …), frameworks (react, vue, svelte, django, rails, laravel …), databases (postgres, mysql, sqlite, redis …), clouds and ops tools (aws, azure, gcp, cloudflare, terraform, ansible, nix), editors (vim, vscode, jetbrains), game engines (unity, godot, unreal), and cybersecurity with ctf and osint. 16 tech subjects, among them electronics-diy, arduino, esp32, mechanical-keyboards, audio-gear, semiconductors, apple, google, linux-distros, open-source, homelab and mobile-apps. 85 GitHub organisations as sections (github.com/rust-lang is rust, github.com/home-assistant smart-home).

  • New
    4,200 well-known tech sites from Wikidata

    import-classes.cjs takes every item of 86 classes — software and technology companies, open-source and free software, programming languages, libraries and frameworks, Linux distributions, browsers, editors and IDEs, database systems, mobile apps, game studios, messengers, chip makers, telecom operators and more — that has an official website and enough Wikipedia articles to be well known, and files it under its subject. It leaves alone what the handwork decides (and the subdomains under it), sites already under two subjects, and domains many different products share. It writes manual/classes.json.

  • New
    tech companies by industry, and more tech news

    Most big tech companies are on Wikidata only as a company with an industry, so the import also takes items by industry (P452): software, IT, internet, computer hardware, electronics, semiconductors, telecom, video games, computer security and AI. 1,350 more sites, bringing the import to 5,560. By hand: some 75 of the best-known tech companies, phone makers and network brands under tech, and 45 more tech news sites in English, Dutch, German, French and Spanish under tech-news, sections such as nu.nl/tech and reuters.com/technology among them.

  • New
    sites from curated lists and self-hosted directories

    harvest-awesome.cjs reads awesome-sysadmin, awesome-devops, awesome-privacy, awesome-docker, Awesome-Linux-Software, awesome-mac and the engineering-blogs feed list, plus awesome-selfhosted-data, whose projects with 100 stars or more get self-hosted. Self-hosted apps listed by selfh.st, selfhostedworld.com, selfhostlist.org and learnwithhasan.com (50 stars or more) went in the same way. Only a link's host is used. A list's broad default is dropped where it was too mixed: the Linux and Mac lists name Linux and Mac only for window managers, desktop environments, menu-bar tools and the like, not for cross-platform apps; a company engineering blog is filed as its /blog section, not as the company. About 2,900 sites; samples judged after each pass, the last at 92% right of the sites that could be judged.

  • New
    15 subjects

    dev-blogs, fediverse, no-code, erp, mcp, pastebin, url-shortener, iptv, inventory, server-management, forms, ebooks-server, distributed-systems, formal-methods and osdev, with their best-known sites. Apps that had a vague second tag get the specific one: NocoDB is no-code, not database; Shlink url-shortener, not internet.

  • New
    sites from GitHub topics, app stores, DEV.to and Lobsters

    harvest-github-topics.cjs reads the homepages of popular repos under 162 topics; a topic counts only for what a project is (monitoring, self-hosted, ai), not what it is built with (vue, mysql, aws), and a host whose repos spread over many topics gets none. harvest-app-indexes.cjs reads F-Droid, Flathub and Homebrew: android and desktop-apps with the store's category, never macos, since most casks are cross-platform. harvest-devto.cjs files developer blogs that cross-post to DEV.to as dev-blogs plus their main topic, and harvest-lobsters.cjs files sites by the tags of the Lobsters stories that link them, with Hacker News popularity (harvest-hn.cjs) lowering the bar from three stories to two. Some 11,000 sites, the catalogue now near 79,000; samples judged per source at 85–95% right. Placeholder domains such as example.com are never filed.

  • New
    425 more self-hosted apps

    Some 1,500 apps in the selfhostedworld.com directory list no homepage; their detail pages do, so those are read too. Each is filed as self-hosted plus the subject of its first category only, since the later ones are loose (an IRC client also lists video calls).

  • New
    sports by sport, kept short

    ice-hockey, rugby, cricket, motorsport, martial-arts and athletics; federations and leagues of the sports the catalogue knew go to those.

  • Fix
    15 more misfiled sites

    among them the best-known assistant sites filed under geopolitics, language and parenting; they now sit under ai alone.

  • Fix
    Find tags offers what it finds, and shows which bookmarks it means

    A round put its tags on straight away and said only "N bookmarks got a tag"; which ones was nowhere to be seen. It now leaves an offer on each row — the dashed chip, click to add, × to turn down — and the list it ran from keeps to the rows with one: With a tag suggestion in the Bookmarks view's views and the tag view's rail, removable like any filter. Add what it finds straight away still does the old thing, now off unless switched on; the choice is one per browser for every view (TagSuggestLive.applyNow, cleanup filter offered).

  • New
    Find tags in the inbox

    The inbox's ⋯ menu runs the round for its links, and a With a tag suggestion filter keeps the list to the ones it found a tag for; run from the Tag suggestions tab, the toast's Show opens it there (showSuggested, filter suggested).

  • New
    what you turned down, from where you turned it down

    The refusals were only at the foot of Config → Bookmarks → Tag suggestions, folded shut. The Bookmarks view, the tag view and the inbox now say N turned down beside their offers, and it opens that list with Turned down open, each refusal with Offer again; in the tab itself, the line N turned down, never offered again at the top now takes you down to it. Past ten refusals the list has a field to find one by site or tag, which holds through the redraw after each one (TagSuggestLive.openRefused, TagOfferRow.refusedLink).

  • Fix
    the arrows walk the tag cloud in reading order

    They jumped to whichever tag sat nearest in the arrow's direction, so where you landed depended on how the word sizes broke the rows. Now every arrow steps through the cloud like a list on the dashboard: Down and Right to the next tag, Up and Left to the one before, wrapping at either end.

  • Fix
    the best-known sites checked one by one

    The 8,000 best-known sites the catalogue had filed itself (by the Tranco ranking) were each checked against their subjects, and 1,743 were wrong: Google Forms under video games, NIST under radio, Hyatt under gambling. They now carry the right subject, or none when the catalogue has no fitting one.

  • Fix
    three rules that filed whole groups wrongly

    A TV channel's site is no longer a tv-series because its shows link to it (350 sites), and a university's site no longer a business school, medical school or research institute because its faculties share it (331 sites). A software company's site is no longer desktop-apps (293 sites), and Wikidata's mobile app class is no longer used, since nearly every service has an app (152 sites).

  • Fix
    Add what it finds straight away is a setting

    Find tags kept the answer in the browser, so another browser or device answered it again. It is now kept with the other settings on the server, or in the browser for whoever keeps settings per device, and stays off unless switched on; an answer of on given before carries over (tagSearchApplyNow).

  • New
    the tag view of every bookmark (#tags)

    Shift+T with no row in hand opens the tag view with no tag picked: every bookmark from every page, N without tags in the header, a Without tags filter at the top of the rail and the tags in use under it, one click from their own view (Back returns here). With a row in hand Shift+T still opens its Tags popover.

  • Fix
    every tag suggestion in a row can be seen

    The line over the list counted 23 suggestions while a narrow Tags column hid most of their chips. The suggestion now comes first and the row's own tags fold into +n around it. A row with more than one suggestion shows +N beside its chip, which opens all of them, each to add or turn down; +n for the row's own tags opens the list of them. The same in the Bookmarks view, the inbox and the tag view (TagOfferRow), where the tag view's rows used to show up to three chips without fitting them.

  • Fix
    Find tags in the tag view offers the same choices as in the Bookmarks view

    Bookmarks without tags (N) of the rows shown, the rows shown, and reading their pages, with Add what it finds straight away in the same words.

  • New
    the cheat sheet lists Shift+T

    The keyboard cheat sheet, the printed sheet (nextDash-cheatsheet.pdf) and its generator now name Shift+T with no bookmark focused (tag view of every bookmark), alongside Shift+K for the dashboard tour and a for the suggested tags in the tag view.

  • New
    1,688 more self-hosted apps known by name, and a home address is #self-hosted

    On a bookmark at home (a private IP, .lan, a Tailscale name) the app list now also knows the long tail: every project in awesome-selfhosted and every self-hosted site the catalogue holds (phpMyAdmin, Tracearr, LazyLibrarian, Houndarr), by host label or by a word in the bookmark's name, so adguard-1 on an IP is AdGuard Home. A public domain where two or more of your apps live (jellyfin.example.cc, radarr.example.cc) counts as home too. Whatever else sits at a home address gets one row offering #self-hosted (on your home network). On the public web none of these new names count.

  • New
    2,298 well-known sites the catalogue lacked

    Of the 10,000 best-known sites (by the Tranco ranking), some 5,700 were in no subject, among them mail.ru, qq.com, sharepoint.com and azure.com. Each was filed under one or two subjects, or left out when it is not a site anyone bookmarks: CDNs, trackers, DNS and API hosts, link shorteners.

  • New
    an adult subject, with 8,915 sites

    396 adult sites from the 10,000 best-known (video and cam sites, creator platforms, adult comics, escort listings) were checked one by one; the rest of the Tranco top million is filed by name alone (porn, xxx, hentai, a cam brand), with the few ordinary words those hide in fenced off. Aliases nsfw, porn, xxx. They were left out or offered as anime, manga or streaming before.

Settings

  • Fix
    "Keep settings on this device only" keeps them on this device

    Every save still sent the whole copy to the server, so a theme or toggle set on the phone turned up in every other browser. In that mode only the settings that stay server-wide (alerts, backups, containers, saved searches and the like) go to the server now; the rest stays in this browser (saveSettings sends GLOBAL_SERVER_SETTING_KEYS only).

Docs

  • Docs
    Help, tips and the manual follow the tag work

    , in six languages: Help → Tags explains where suggestions come from and the +n/+N lists, Help → Keyboard and the tag view tip name Shift + T with nothing selected, Help → Widget kinds counts forty-two kinds with Emby, Plex and the now-playing tiles, and MANUAL §10.4 describes how tag suggestions work. The tag view of every bookmark, the row popovers and On your home network get their own strings in every language.

  • Docs
    translations of the tag suggestion strings

    which still showed their English text in nl, de, fr, zh and es: the With a tag suggestion filters, the Tag suggestions group, the inbox note and Find tags hint, the 1 bookmark has a tag suggestion lines, Show, N turned down with its hint, and the search field for what you turned down — 13 keys.

  • Docs
    the manual and the README follow the release

    Shift + T and the tag view of every bookmark in §7.1 and §10.2, Emby, Plex and the now playing tiles in §15 and the README (forty-two kinds), and the page filter on a phone in §22.

  • Docs
    Config → Overview gains six items for v1.19.5 to v1.19.8

    (the media widgets, the tag view and the tag view of every bookmark, Home Assistant, Appearance in three groups, and now playing for Jellyfin, Emby and Plex), in all six languages.

  • Docs
    static/data/whats-new/v1.19.8.json and its index entry

    with four highlights and their pictures under static/data/whats-new/media/; whats-new-stub.js moves DASHBOARD_RELEASE to v1.19.8 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v338, and tests/whats-new-hidden-release.spec.js names v1.19.8 as the release that leads.

  • Docs
    the Unraid template

    lists the v1.19.6 and v1.19.7 changes, the same as the copy Community Applications reads.

Only docs and tests changed in this release.

v1.19.7 Changes in Appearance and Tags. +13 12 fix

Changes in Appearance and Tags.

Appearance

  • New
    Appearance groups its tabs

    Nine tabs under three labels — Look (Theme & type, Background, Surfaces), Bookmarks (Layout, Rows, Link previews) and Header & bars (Header, Action bar, Date & weather) — and link preview cards have a tab of their own. Look, Surface and Grid are renamed Theme & type, Surfaces and Layout; the old ids and words still open them (APPEARANCE_TAB_GROUPS, previews, renderSectionTabStrip).

  • New
    settings moved to where they belong

    Clock placement leads Date & weather instead of sitting on Header; Show favicons, the offline colour and favicon harmonisation are one Favicons panel on Rows; the browser tab title, custom title and favicon upload are one Browser tab & branding panel on Header.

  • New
    label and control side by side

    Appearance rows put the label and a one-line explanation on the left and the control on the right, in one shared column; a longer explanation is cut with an ellipsis and stays whole in its tooltip and the ℹ. Under 600px the control goes under its label.

  • New
    Fine-tune folds

    The seven Backdrop sliders and the Card glass opacity and blur sit under Fine-tune, folded until opened; the fold says how many of its settings differ from the default and keeps its state across a repaint. The filter, Only changed and Find settings open the fold they land in. The separate Backdrop settings panel is gone; its sliders are in the Backdrop panel (renderFineFold, schema control fine).

  • Fix
    the settings filter survives a repaint of Background and Surface

    applyDomSettingsFilter looked for the body inside the container it was handed, and a repaint hands it the body itself.

  • New
    chip groups

    Runs of Show the … button switches are one row of chips: the action bar (9), the header buttons (4), the category header extras (3), the row status (3) and the date line (2). Each chip is still its own setting; the group has one ↺ for the chips that differ and one ℹ that lists what each chip does. The link preview fields and the Bookmarks view's columns and rail blocks use the same chips over their one list (schema control chips, setChip helper).

  • Fix
    the filter finds a single chip

    Typing one chip's name hid its group's label row, and with it the whole panel; the label row now reads its chips too (applyDomSettingsFilter).

  • New
    panels fold, and say what they are set to

    On every Appearance tab the first panel is open and the rest fold to a header with one line of their current values, changed values first; a panel opened or folded by hand stays that way, per tab, in this browser. The filter, Only changed, Find settings and a link to #config/appearance/<tab>/<panel> open the panel they land in, and Reset panel in a folded header does not open it (applyAppearanceFolds, PANEL_SUMMARY_BY_TYPE, openConfigPanel e2e helper).

  • New
    a list of panels on long tabs

    A tab with more than three panels lists them above the preview; choosing one opens it and scrolls to it, and the panel in view is marked. The filter narrows the list with the panels; under 900px it is left out (renderAppearancePanelIndex).

  • Fix
    Date & time starts with a capital

    like the other panel titles.

  • Fix
    the Appearance tabs wrap instead of scrolling

    On one scrolling line half of the nine tabs sat past the edge; now a group that does not fit moves to the next line whole, its label over its tabs, so every tab is on screen down to phone width.

  • New
    the action bar animation is a dropdown

    Picking a style plays it on the real bar at once, so the six cards that each played it again are gone and the panel is about half as tall.

  • New
    Show the action buttons leads the action bar settings

    above where the bar stands and how large its buttons are: it decides whether any of the rest matters.

  • New
    five action bar button sizes

    Button size in Appearance → Action bar runs from extra small to extra large; medium is the default, one step up from the 28px squares the bar had, which are now small. An install from before the setting gets medium (actionBarSize).

  • New
    the key chips on the action buttons start off

    for new installs too; turn them on in Appearance and they stay (showActionKeys).

  • Fix
    the header destinations follow the button size

    Bookmarks, Inbox, the page tabs and the header links stayed 40px tall at every action bar size, so beside medium and larger buttons they stood shorter than the group next to them; they now measure the button size plus its surround.

  • Fix
    the theme field shows a whole theme name

    Its control was capped at 300px, which cut most names of up to 25 characters; it now has room for them on one line.

  • Fix
    a tab reached through Find settings stays put

    Arriving on Appearance from another section through Find settings, a tile or a link, the Random theme promo pulled the reader back to Theme & type half a second later; only a click on the tab strip counted as a choice. Every way into a tab does now (switchAppearanceTab).

  • Fix
    a docked action bar no longer slides into place on a load

    Its slide ran on the first placement too, sweeping a side column some 200px up the screen as the page appeared; it now only slides when it goes into its edge and comes back.

  • Fix
    Save as theme opens the editor without a wait

    The saved theme brings the look on screen, and picking it put that same look back, redrawing the header bar and the dashboard twice; on a slow machine the page froze for seconds. A look's parts that are already in place are now left alone (applyLookAnswers).

  • Fix
    the Media detail card uses the app's colours

    It sits on <body>, outside every widget, so it named variables that were not there: it was transparent, in the corner and with unstyled buttons. It now takes the app's background, text and border, sits in the middle, and has its own buttons.

Tags

  • New
    subjects in a tree

    A subject can name a broader parent (kubernetes under containers under dev, broker under investing under finance); 247 of the 471 now do. A suggestion comes in the reader's own words, now up the tree: whoever tags #finance but never #broker is offered #finance on a broker's site. Turning a broader tag down on a site turns down what sits under it there too. Catalogue schema v3; the parents live in scripts/tag-catalogue/parents.json and are written in by merge.cjs or, without a rebuild, apply.cjs.

  • New
    a quiet lookup for new links

    A bookmark or inbox link that arrives after this browser first looked has its site looked up on Wikidata without a button, an overlay or a notice, and what comes back is offered as a chip. It never writes a tag. Only links newer than the first look count, a host is tried once per thirty days, a round takes at most twenty hosts and waits behind the reader's own Find tags; Look up unknown sites on Wikidata off turns it off.

  • Fix
    the answers of a Find tags round land on the rows as they arrive

    What the catalogue already knew is on screen at once, before the first answer from Wikidata, and a burst of answers redraws a view once instead of once per batch (TagCatalogue.onChange with wait).

  • Fix
    135 misfiled catalogue sites

    Telecom operators under electronics, flight search under search, amazon.co.jp under streaming, yahoo.com under television, drinks brands under containers, three bare IP addresses and more: 126 are refiled and 9 dropped. The fixes sit in scripts/tag-catalogue/manual/cleanup.json, which a rebuild reads as handwork, so they hold.

Only docs and tests changed in this release.

v1.19.6 A tag gets a page of its own. +25 28 fix

A tag gets a page of its own. The tag cloud is quieter — three sizes, counts, type to find — and picking a tag opens its tag view: every bookmark with that tag from every page, in one table with related tags, bulk actions and rename, merge or remove for the tag. Tag suggestions now draw on a catalogue of some 51,000 sites and ask Wikidata about the rest, and they show up in the rows of the tag view, the Bookmarks view and the inbox with Add all. A Home Assistant widget switches lights and scenes from the dashboard. The tours are short, views and modals rise in at a speed you choose, and a run of fixes keeps saves from one device from undoing work done on another.

Tags

  • New
    a quieter tag cloud

    Three sizes by rank instead of a size per count, each tag with its count beside it and A–Z within a size; the # glyph, the tilt and the drift are gone. Typing dims the tags that do not match and selects the first match; Backspace and Escape undo the typing first. Shift+click or Shift + Enter stacks tags, and every other tag then shows +N, how many bookmarks it would add. The cloud opens centred and animates into the tag view. Sizes, order and counts come from static/js/shared/tag-cloud-model.js, which the Config tags tab uses too.

  • New
    the tag view

    A table view on #tag/<tag> (several joined with +) replaces the grid tag filter: every bookmark with the tag, from all pages. The header carries the figures (bookmarks, pages, last and most opened, broken), Open all, Copy links and Manage tag (rename, merge into another tag, remove from all bookmarks, each with undo). The rail lists related tags, pages and a health filter; the toolbar has a search box, a count and a sort menu. Rows show the favicon, the dashboard's row menu and its Shift keys, an i side panel, x/Alt/Shift selection with Open, Move to…, Delete and Clear, and Escape lets go of one thing at a time before it leaves the view. t, :filter <tag> and the cloud open it.

  • New
    the tag filter reaches every page

    Before the tag view replaced it, the filter read only the page on screen, so a tag that lived on another page showed an empty grid. It now reads the same pool as the cloud, loading allBookmarks when the cloud opens if startup skipped it; delete and move act on each bookmark's own page, and Move to… offers categories only when every match is on one page.

  • New
    tag chips on dashboard rows are labels only

    The cloud, t and :filter are the ways into a tag; :filter clear is gone with the grid filter.

  • Fix
    / with the header's tag button off

    opened the cloud inside a hidden wrap.

  • Fix
    a tag change in the tag popover renamed every bookmark in memory

    that shared the old tag list; the rewrite now touches only the bookmark edited.

  • Fix
    Move to… for a bookmark on another page

    offered the current page's categories; it now offers pages.

  • Fix
    no preview card left over the tag view

    A tag picked in the cloud with the pointer coming to rest on a dashboard row opened the view before that row's hover delay was up; the row went without a mouseleave, its timer still fired, and the card of a bookmark no longer on screen stayed over the table. showBookmarkPreviewCard now refuses a row that is gone or hidden.

Tag suggestions

  • New
    a catalogue of some 51,000 sites and 471 subjects

    up from 463 subjects in a hand-written list. The catalogue moves from static/data/tag-patterns.json to internal/app/tag_catalogue.json and is served by GET/POST /api/tags/catalogue with exact host matching; search now means search engines. It is built offline from CrUX candidates, Wikidata per class and per country, and hand-written blocks (scripts/tag-catalogue/), with derived hosts read beside the hand-written ones.

  • New
    unknown sites are looked up on Wikidata

    POST /api/tags/lookup asks Wikidata's query service, one query at a time and at least a second apart, which class a host belongs to. Only the host name leaves the server, and only for hosts that resolve to the public internet. Answers live in tag-lookup-cache.json (90 days for a found site, 30 for an unknown one; a cache, not in backups). On by default; Look up unknown sites on Wikidata in the tags tab's menu switches it off.

  • New
    a tag taken off by hand stays turned down

    A bookmark save that removes a tag records the refusal on the server, and the response hands it back in X-NextDash-Refused-Tags / X-NextDash-Wanted-Tags so the tab's own settings do not write an older list over it. An undo (X-NextDash-Undo) is not counted as a refusal. The list is capped; the oldest refusals give way.

  • New
    suggestions in the rows

    The tag view and the Bookmarks view show a dashed chip after a row's tags (click to add, × to turn down), a line N tag suggestions · Add all over the list, and Find tags to ask the catalogue and Wikidata, or read the pages, for the rows shown. Opening a view never goes online by itself. In the tag view, a adds the focused row's suggestions.

  • New
    Find tags from the side panel and the Bookmarks view

    with one row per tag in the suggestions panel instead of one per bookmark.

  • New
    the tag popover looks the site up when it opens

    and offers Read page when nothing is found; the bookmark form does the same when there are no suggestions.

  • New
    words read from pages count everywhere once loaded

    not only in the panel that read them.

  • New
    catalogue: Dutch handwork sites, and hackaday as electronics
  • Fix
    the suggestions panel stays in place after Apply

    instead of jumping back to the top.

  • Fix
    Turned down stays open when the suggestions redraw

    Offer again on one of several refusals folded the list shut.

  • Fix
    the bookmarks panel looks tags up online again when opened
  • New
    tag suggestions in the inbox rows

    The inbox gains a Tags column, as the Bookmarks view has: the row's own tags, +n for what does not fit, and a dashed chip with the tag on offer (click to add, × to turn down, the source as its tooltip). A line N tag suggestions in this list · Add all sits over the column heads, and a adds the offer of the row under the cursor; every add offers Undo. Opening the inbox now also loads the words read from pages, as the Bookmarks view does.

  • Fix
    the inbox shows links added since it was last read

    Opening it drew the list the header badge had read at start-up, so a link saved from the extension or another tab was missing until something else redrew the view; a read in the background reached the list but not the screen. The view now reads again as it opens, and any read that changes the list redraws an open inbox.

  • New
    one row-offer chip for both views

    The chip, the count line, the fitting of the Tags column and the source label move out of the Bookmarks view into shared/tag-offer-row.js and tag-offer.css, which the inbox uses too.

Widgets

  • New
    a Home Assistant widget

    Fill in the address and a long-lived access token and press Connect; the server lists your entities, searchable and narrowed by kind, and you pick up to 60 in your own order. Lay them out as a list of loose items or a strip with a tab per room, grouped by room, kind or nothing, with when each last changed. Lights, switches, fans, scenes and scripts switch from the tile; locks, covers, doors and sensors only report. Whether the reader may switch is decided per request and never cached. Entity ids are checked before they go into the room template that runs in Home Assistant. It rides on the shared media cache and tile, redraws after a scene and carries the New badge.

  • Fix
    a media tile's tab of lines stacks

    instead of taking the poster columns.

  • Fix
    a calendar fetch is no longer cancelled by the reader leaving

    A reload mid-fetch made it fail, and the failure was cached for every other calendar widget for a minute; calendarFetchTimeout still bounds it.

Dashboard

  • New
    the key legend under the grid

    Three lines, shown on the dashboard view only; Shift + Z switches it off and on, and it stays off after a reload. It is on for new installs and stays off on existing ones unless switched on. Translated in all six languages.

  • New
    Shift + K replays the dashboard tour

    and the legend names it.

  • New
    the Shift + F filter bar in the prompt style

    a mode pill like SEARCH and COMMANDS, a line saying what Escape does, and the match marked in the names that are left. Widgets hide while it filters, and the first-start card stays above the bar.

  • Fix
    a page switch no longer patches another page's grid

    Every new page has a category called others, so the incremental path matched the structure and kept the old page's folded categories, icons and sort controls; the grid now records which page it is.

  • Fix
    a page switch that gets no blocks clears the last page's widgets

    instead of leaving them on screen.

  • Fix
    an older all-bookmarks answer no longer overwrites a newer one

    Two loads in flight could land in the wrong order and drop a bookmark just added.

Config

  • Fix
    a new page id comes from the server's page list

    A page made on another device since the tab loaded was missing from dash.pages, its id was handed out again, and the duplicate wrote its bookmarks over that page.

  • Fix
    a pages save keeps names changed on another device

    The whole list goes to the server; it is re-read first, and only the pages this save is about keep this tab's version.

  • Fix
    a page whose save fails is dropped from the list

    instead of staying as if it existed.

  • Fix
    a category save keeps categories made on another device

    and a finder save keeps finders made elsewhere.

  • Fix
    deleting the page on screen leaves it

    for the first page left; it used to stay, every edit a 404, until a reload.

  • New
    a short description under the Containers tabs

Bookmarks

  • Fix
    two adds of the same URL at once

    no longer both land: the duplicate check is repeated under the store lock and answers as the first check does.

  • Fix
    preview text in the all-pages read

    had its HTML entities left undecoded.

  • Fix
    the default page order is by id

    not Go's random map order, which shuffled the tabs and saved them that way.

  • Fix
    the Bookmarks view draws when it opens before the inbox has loaded

    :health refresh (and an old #health link) opened it with the header half drawn and no fresh scan: the tag counts read inbox.items through the inbox's lazy loader, which handed back a function, and .filter on it threw. The loader now answers items with an empty list until the module is there.

Health

  • Fix
    auto-heal refuses a URL already on the page

    Two old links redirecting to one home page both healed onto it, and the page then refused every save as a duplicate.

  • Fix
    a panicking report build releases its flag

    Without the deferred release, every later report request waited for good.

  • Fix
    the longest-unchecked monitors go first

    In page order the same tail was dropped past each round's deadline, so a slow host's last services never got a sample or an alert.

  • Fix
    maintenance window times stay on the wall clock across DST

    midnight plus a duration was an hour off on the day the clocks change.

  • Fix
    a delete in Work through that is not a page's last row is counted

    The report renumbers rows after a delete, so the next row took the key and the delete went uncounted; it is now matched by page and URL.

Tours, tips and motion

  • New
    shorter tours that cover the main features

    The dashboard tour drops from twenty steps to seven, the Bookmarks view tour from ten to five, Containers from fifteen to six, the Inbox to four; Widgets is shorter too. View tours are offered once on a first visit and play again from their Tour button. About 3,300 lines of tour code and strings are gone.

  • New
    the Fresh and Spread walkthroughs are removed

    Fresh keeps its guide in Help.

  • Fix
    the bookmark form, the notes window and the container logs let go of their opening animation

    once it ends; a forwards fill kept a finished animation holding the dialog's transform for as long as it was open.

  • New
    animation speed, and a switch for animations in views and modals

    Appearance → Text and motion gains Animations in views and modals (on by default, also on existing installs) and Animation speed (slow, normal, fast). The Bookmarks, Inbox, Containers and tag views rise in like the tag view, and the modals and action-bar modals rise in like the add-bookmark form. Enable animations off still wins.

  • New
    at most one tip per 24 hours

    counted across devices and never over a modal.

  • New
    the install count card waits two days after the analytics question

    so the two privacy cards never arrive in one visit.

  • New
    usage counts for containers, widgets, inbox triage, category sort and the tag filter and view

    through the existing analytics when it is switched on (nextdashTrack). Only the widget type and whether a link or button was hit go out, never an address or a label.

Docs

  • New
    MANUAL, Help, tips and the cheat sheet cover the tag cloud and tag view, tag suggestions in the rows and Wikidata, Home Assistant, the animation settings and the shorter tours

    with new screenshots. The cheat sheet gains a Tag view section; the printed PDF is regenerated.

  • Fix
    110 strings showed in English in every language

    the suggestion chips and Add all in the rows, Find tags and the Wikidata lookup, the tag view's find-and-read menu, the Home Assistant entity picker and the inbox's new tag column were drawn from their code fallbacks, with no key in any locale. They are in en.json now and translated into the other five, with the inbox legend's a row and its cheat-sheet line (ivAddOffer), which failed validate:cheatsheet-registry.

  • Docs
    static/data/whats-new/v1.19.6.json and its index entry

    with three highlights (the tag view, suggestions in the rows, Home Assistant) and their pictures from tests/fixtures/whats-new-media/v1.19.6.js; whats-new-stub.js moves DASHBOARD_RELEASE to v1.19.6 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v336.

Only docs and tests changed in this release.

v1.19.5 Five more media widgets join Jellyfin on one shared base: Sonarr and Radarr show what is coming and what is in the queue, Seerr shows requests with who asked and whether they arrived, and qBittorrent and SABnzbd show what is downloading with progress, speed and time left. +6 2 fix

Five more media widgets join Jellyfin on one shared base: Sonarr and Radarr show what is coming and what is in the queue, Seerr shows requests with who asked and whether they arrived, and qBittorrent and SABnzbd show what is downloading with progress, speed and time left. Adding a widget opens a picker you can search, with the kind you are on shown beside the list, and the kinds new in this release carry a New badge and a strip of their own in the Catalogue.

Widgets

  • New
    Sonarr and Radarr widgets

    The episodes and films coming up in the next days (a week by default, up to 30) and what is downloading, each with its poster. The same four layouts as Jellyfin; in the strip, Upcoming and Queue are the tabs. Show picks what is coming, what is downloading, or both.

  • New
    a Seerr widget

    Requests in Overseerr or Jellyseerr under Pending, Approved and Available, with who asked and the poster. Show every request or one state, films, series or both, from everyone or one person. Posters come from TMDB, which the server fetches without a key; a key copied without its trailing == is mended.

  • New
    qBittorrent and SABnzbd widgets

    What is downloading, paused and finished, with progress, speed and time left, and the client's speeds and counts on top. One list or a tab per part, in the order you choose (newest, furthest along or fastest), refreshed as often as every 15 seconds. qBittorrent signs in with a username and password, or with an API key from 5.2 on, and can be narrowed to one category.

  • New
    the media tiles share one base

    Jellyfin and the five new kinds use one cache per widget on its own TTL, one picture proxy and one tile with the list, strip, hero and grid layouts. Set-up is the same for all of them: the address, the key and Connect, which says Connected to with the version and fills the choices below. Posters now live in data/media-images/, shared by all media tiles (up to 200 MB, oldest out first, not in backups); the data/jellyfin-images/ folder of v1.19.4 is removed the first time a poster is stored.

  • New
    a picker for Add a widget

    Type to search the kinds by name or by what they show, ↑ ↓ to choose and Enter to add; the pane beside the list shows the kind you are on. The first Escape empties the search, the next closes the picker. The list is a listbox the field drives, so focus stays in the field.

  • New
    a New badge on the kinds added in this release

    in the picker and the Catalogue, with a New chip and strip at the top of the Catalogue. The badge stays through v1.20 and goes away by itself from v1.21 on.

Translations

  • Fix
    eight strings of the widget picker and the New badge

    were missing from every locale and showed in English; they are now in all six languages.

  • Fix
    three keys the Inbox and re-check messages were missing

    are added in all six languages.

Docs

  • New
    Help, MANUAL and README cover Sonarr, Radarr, Seerr, qBittorrent and SABnzbd

    with where to find each key, and the widget picker in §15.2.

Only docs and tests changed in this release.

v1.19.4 The headline is the Jellyfin widget: connect it once and it shows what was added to your media server lately with the real posters and backdrops from Jellyfin itself, so a dashboard tile looks like your library. +14 19 fix

The headline is the Jellyfin widget: connect it once and it shows what was added to your media server lately with the real posters and backdrops from Jellyfin itself, so a dashboard tile looks like your library. Config → Widgets is one panel with three tabs — Your widgets, Catalogue and Custom widget — and on a wide screen the list and the open widget stand side by side. The What's new window gives a release's highlight a spotlight and opens every release since your last visit, and the weekly digest gains a part for the week's nextDash releases. A weekly digest sums up what needs you once a week: links that broke, certificates running out, container updates and bookmarks nobody opens. Status & alerts leaves Behavior for a section of its own, Config → Monitoring, with three tabs. A pasted link shows what it is before you choose where it goes. v1.19.3 leads the What's new window and brings v1.19.2, v1.19.1 and v1.18.4.1, held back before, in under it. It also carries everything prepared for v1.19.3, which was never tagged: the weekly digest and Config → Monitoring.

Monitoring

  • New
    a weekly digest

    Once a week the server builds one message from the health report, the container update check and usage: newly and still broken links, certificates running out, container updates (held ones left out), most opened, never opened, not opened for the stale threshold, and the Inbox count. It goes to browser notifications and the downtime alert service, on Monday at 08:00 by default in the quiet-hours zone. It waits for quiet hours to end instead of going through quietGate, and a week with nothing to say sends nothing. The due slot is the latest configured weekday and time at or before now, so a restart, a late start and a double tick all give the same answer; a digest missed while the server was off goes out once, and the very first tick only records the slot so an upgrade does not push last Monday's digest at once. State and the latest snapshot live in data/digest.json; GET /api/digest/latest serves the snapshot and POST /api/digest/test, behind the write token, sends a proof digest without moving the week's slot.

  • New
    the digest on the dashboard: a card, a window and a bar

    The card, Your week in nextDash, names the one or two things that matter most; Read the digest opens a window with a part per subject — what it means, the names behind the count, and a button to the view where it is dealt with (Open in Bookmarks, Work through for the broken links, Open Containers, Review, Open Inbox). After a button the digest shrinks to a bar in the corner with its progress and Next; it holds the corner so other cards wait, comes back after a reload, and goes once every part is opened or with ×. The push lands on /#digest, which opens the same window. On the day of a digest the daily review card waits (DigestNotice.holdsTheWeek). digest-notice.js, digest.css.

  • New
    Config → Monitoring

    Status & alerts was split into Checks and Notifications, then moved out of Behavior into a section of its own with three tabs: Checks (in this browser, on the server, how monitored bookmarks stand out), Notifications (downtime alerts, browser notifications, reminders, the weekly digest) and Schedules (maintenance windows and quiet hours). MONITORING_FROM_BEHAVIOR sends an old #config/behavior/status, checks or notifications address, a saved location, a news entry and the behaviorTab setter to the matching Monitoring tab; the loader's copy of that map is gone. The bookmarks tour, the status page hints, the Health tutorial and the container notice say Monitoring instead of Behavior → Status & alerts.

  • New
    Monitoring → Notifications → Weekly digest

    : send it or not, the day, the hour, which parts go in, Show for the latest digest and Send for a proof one. The settings default to on (digestEnabled, digestHealth, digestUpdates, digestUsage), with missing-key entries so an existing install gets them on too.

  • Fix
    digest.json stays out of backups

    . It had no backup policy, which TestEveryDataFileHasABackupPolicy caught. A restore has no use for last week's digest: without the file, the next tick only records the week's slot and sends nothing.

  • Fix
    Send a weekly digest has an ℹ

    that says what the digest holds and where it goes, in six languages (digestEnabledInfoTitle, digestEnabledInfoMessage).

  • New
    the weekly digest names the week's nextDash releases

    A New in nextDash part, made from the same files the What's new window reads, lists every release that came out in the digest's week with the items marked as a highlight, or the release's one-line lead when nothing is marked. Its button opens What's new; it is news, so it does not count as something to work through. On by default.

  • Fix
    one busy host no longer starves the other checks

    A monitor check took one of the round's eight slots before it waited on its host's gate, so twenty services on one IP held all eight while queued behind each other, and every other host waited; with that server offline, a large round could run past its ten minutes and drop the checks it had not reached. The host gate now comes first.

  • Fix
    the server log's age limit gets past a stack trace

    The lines under http: panic serving carry no timestamp, so they had no age, stopped the prune once they reached the head of the ring, and kept every line behind them past the window. An unstamped line now takes the time of the line before it.

Widgets

  • Fix
    a label typed right after Save is no longer wiped

    Save repainted the panel, then redrew it once more when the dashboard's blocks came back, replacing what was typed in between; that second redraw is skipped while config is on screen.

  • New
    a Jellyfin widget with the real posters from your server

    The tile shows what was added lately the way Jellyfin itself does: each film and series with its own poster, an episode under its series poster (an episode's own still is 16:9 and reads badly in a 2:3 frame), and in the hero layout the newest item large on its backdrop. The pictures are the ones in your library, fetched from Jellyfin by the server at quality 85 and the width the tile needs, so the tile looks like a shelf of your own media rather than a list of titles.

  • New
    the Jellyfin set-up connects first and asks after

    Fill in the address and the API key and press Connect (POST /api/widgets/jellyfin/setup, denied in demo mode): the server tries both and says Connected to {name} ({version}), then fills the choices below it with who the tile reads as and the libraries that exist, so nothing has to be typed by id. Then pick the libraries (anime is usually a library of its own, so libraries rather than item types), a layout — list, strip, hero or grid — whether a click opens the item in Jellyfin or a detail view, whether watched items are hidden, how many rows and how often it refreshes (a minute at least). How wide the tile is comes from a container query, so a two-column tile on a phone reads as the one-column version. The API key is an ordinary widget credential (X-Emby-Token) and never comes back to the browser: the server fetches the list (GET /api/widgets/jellyfin) and the posters (GET /api/widgets/jellyfin/image), which only proxies a picture the last answer named. One answer per widget on its own TTL; a failure keeps the last good answer and says how old it is. Posters are kept in data/jellyfin-images/, named by server, item, kind and tag, capped at 200 MB and trimmed oldest-first (evictImagesIn, shared with the preview cache), and left out of backups. A page template carries the server address as a variable and drops the user and libraries, which name nobody on another server.

  • New
    Config → Widgets has three tabs: Your widgets, Catalogue and Custom widget

    The Catalogue is every kind on one page with a small drawing of what it shows, made of example figures rather than a live render so it opens fast; group chips narrow the cards without a refetch. The Custom widget tab explains the one kind that is a capability rather than a report. A widget added from either lands on Your widgets to be filled in.

  • New
    the Types tab folds into the Catalogue

    A stored or linked types tab lands on the Catalogue; the Unraid section's Add opens the catalogue on that kind, and the widgets tutorial and search commands say so. The orphaned Types strings are gone from all six locales.

  • New
    Your widgets is one panel of one-line rows with a shared detail view

    One function draws a widget's detail for both places it can stand, so the two can never offer different controls.

  • New
    list and detail side by side on a wide screen

    Wide or narrow is measured on the section's own width, not the window's, with 40 px of slack so a width on the line does not flip back and forth; it repaints only when the answer changes. Wide, one widget is always open beside the list — the chosen one, or the first shown once that one is gone after a delete, move or search. Moving between the layouts keeps the field being typed in, with its uncommitted value.

  • Fix
    renaming a widget no longer takes the caret away

    A rename fires when you leave the title, so the config redraw that followed took the caret out of the field you had just moved to; the dashboard's blocks now refresh with keepConfig.

  • Fix
    a negative size or line speed scales like a positive one

    A custom widget's Size and Rate formats stepped on the value rather than its magnitude, so a negative change read -5000000 B without a decimals setting and -4.77 MB with one (formatByteSize, formatBitRate).

Config

  • Fix
    the sub-tab strips stay on one line and scroll

    A section with many tabs wrapped them onto a second row on a narrow screen. The strip now scrolls sideways, keeps the active tab in view and fades the side where there is more.

  • Fix
    Structure is no longer marked new in the section list
  • Fix
    the new badge moves from Containers and Unraid to Widgets

    (NEW_SECTIONS).

  • Fix
    a redraw keeps the focus on the control it replaced

    Appearance draws again by itself when the colour document or the surface meta arrives, and each redraw swapped the focused control for a copy and left the focus on the page. A settings jump that had just reached its control lost it, and the tab strip stopped answering the arrow keys. The redraw now hands the focus to the matching control in the new markup.

  • Fix
    a link to a section waits for the section before drawing it

    An address such as #config/widgets drew the section before its file had loaded, so the heading changed while the body of the previous section stayed under it. It now waits for the file, as picking the section from the list already did.

Dashboard

  • New
    the paste choice shows what the pasted link is

    While you choose between bookmark and Inbox, a card shows the site's favicon, domain, title, description and picture, from the same /api/bookmark-preview answer the hover card draws, with the local copy of the picture. A slow answer never lands in a later modal, and a missing picture is asked for once more.

  • Fix
    four corner cards are gone

    : the Widgets layout invitation, the Fresh offer, the pointer to the feature overview and the offer to check unchecked bookmarks. Fresh, its tutorial and POST /api/health/check-mode-all stay.

  • Fix
    a block's grip can be dragged with the mouse again under a header style other than the theme's

    The grip was sized in em against a font size of 0, so it was zero wide and the icon after it took every click.

  • Fix
    cancelling a block move no longer takes the focus back from the title

    Escape on a block you were carrying put the focus back on its handle two frames later, whatever you had done in between, so Shift+Tab to the title and Enter folded nothing. The focus now returns only when the redraw dropped it.

Containers

  • Fix
    the disk prune questions use the singular for one

    Remove 1 stopped container, 1 untagged image, 1 image no container uses, in six languages.

  • Fix
    a recreated container answers what the old one announced

    docker compose up --force-recreate (or a pull) destroys the container and starts a new one under the same name; the destroy event wiped the notifier's memory of the unhealthy or stopped unexpectedly it had sent, so no healthy again / running again followed, the open alert stayed in notify-open.json and reminders said still has a problem about a container that ran fine. The watch is now kept while a notice is outstanding.

What's new

  • New
    a spotlight for the highlight

    An item a release marks as highlight gets room at the top: its picture or a short silent looping recording (the still with motion turned down), a short title of its own, the explanation and a button to where the change lives (link, linkLabel, a hash route such as #config/monitoring/notifications). Other new changes are one row each with their section in front and the detail folded; fixes are one line each, opened with a native disclosure; shortcuts keep their own block. When the release the window opens on marks nothing, its first new change stands in. Media lives under static/data/whats-new/media/. v1.19.3's weekly digest is the first spotlight, with a screenshot and a recording.

  • New
    every release since your last visit opens

    The window opens each release newer than the last one you saw, the newest with the big version as its headline, and says Since your last visit: n releases, x new and y fixed. Older releases stay as rows under Earlier.

Bookmarks

  • Fix
    the icon menu marks what was saved while the panel has focus

    A Use letter save that landed while the pencil had the focus left the menu marking Automatic until the panel was redrawn for another reason. The panel that is kept on a redraw now has its icon menu brought up to date in place.

Tag suggestions

  • Fix
    the catalogue also knows a subdomain by its parent domain

    docs.docker.com, wiki.archlinux.org and en.wikipedia.org were passed over because the shipped file names docker.com, archlinux.org and wikipedia.org; the lookup now tries the host and then each parent down to two labels. A domain and its subdomains are one row under the catalogue's site, so turning it down holds for all of them.

Docs

  • Docs
    Help follows v1.19.4

    , in six languages: Widgets → Adding one names the three tabs and the side-by-side layout, The kinds counts thirty-one and adds What is new to watch? with Jellyfin, Weekly digest names the New in nextDash part and its switch, and Version describes the spotlight and every release since your last visit. Checks & health and the tipMaintBulkCheck tip no longer point at the removed corner card; they send unchecked bookmarks through the Bookmarks view instead.

  • Docs
    MANUAL §4, §12.1, §12.4, §15.1, §15.2, §15.3, §17.1, §17.7 and §17.8

    : the four removed corner cards are gone from the list, Config → Widgets has its three tabs and the wide layout, Jellyfin has a row and a set-up paragraph, the digest has its news part, and What's new its spotlight, the releases since your last visit and the All / New only / section chips.

  • Docs
    translations

    of the v1.19.4 strings, which only had an English fallback in the code: the Widgets tabs and Catalogue, the Custom widget tab, the Jellyfin settings and tile, the digest's New in nextDash part and its switch, and the What's new window's spotlight, chips and Ko-fi card — 100 keys in en.json, nl, de, fr, es and zh. The Jellyfin set-up errors now have fixed keys (widgetJellyfinError*) instead of one built from the server's error text.

  • Docs
    README and MANUAL

    : the README names the Jellyfin widget and counts thirty-one widget kinds, the Unraid screenshot caption points at Widgets → Catalogue, and the MANUAL's Find settings picture is described under Monitoring › Schedules.

  • Docs
    498 unused locale strings removed

    from en, nl, de, fr, es and zh (366 in dashboard, 132 in config): keys no file, template or test names in any form. Nothing on screen changes.

  • Docs
    Help → Config gets a Monitoring panel and Help → Monitoring a Weekly digest panel

    , in six languages; Help → Behavior lists four tabs, and every Help panel and tip that named Behavior → Status & alerts names the Monitoring tab now. Help → Config says the tab strips scroll on a narrow screen.

  • Docs
    both new Help articles open with a picture

    like every other: the config map with its tabs for Monitoring, and a week becoming one message on your devices for the weekly digest.

  • Docs
    MANUAL §12.1, §12.4, §12.5, §12.8, §14.9, §17.1, §17.2 and §17.5

    describe Monitoring and its three tabs, and §12.4 the weekly digest; Get told mentions it. §5.3 describes the preview in the paste choice, and the README's alerts line mentions the weekly digest.

  • Docs
    translations

    of the weekly digest card, window, bar and settings, and of the five strings that pointed to Behavior → Status & alerts (the Health tutorial, the bookmarks tour, two status page hints and the container notice), in nl, de, fr, es and zh. The orphaned config.behaviorTabStatusAlerts is gone from those five, so validate:locale-parity is green again.

  • Docs
    Config → Overview and About → News & features

    gain two v1.19.4 entries, the weekly digest and the Monitoring section, in six languages.

Tests

  • Tests
    digest_test.go, digest_build_test.go and digest_settings_test.go

    cover the due slot, the first tick, quiet hours, an empty week and the snapshot; tests/digest-notice.spec.js the card, window and bar; tests/digest-config.spec.js the settings panel. tests/config-tabs.spec.js covers the Monitoring tabs, old Behavior addresses and saved places, and the scrolling strips; the specs that opened Behavior → Status & alerts open Monitoring. tests/dashboard-paste-preview.spec.js, tests/dashboard-block-move.spec.js and tests/docker-disk.spec.js cover the preview, the grip and the singular questions.

  • Tests
    tests/config-widget-panel.spec.js

    waits on signals instead of a 6 s sleep, which was hiding the Save race. tests/config-help-health.spec.js counts ten panels on Help → Monitoring.

  • Tests
    the specs that still opened Behavior → Status & alerts open Monitoring

    config-new-sections, config-push-notifications, config-checkbox-rows and config-backups lost their Monitoring paths when the condition-wait commits were rebased under them; they are back, with the waits kept. config-info-reset checks the three Monitoring tabs and lists the digest's five follow-on fields, config-settings-jump-index lands the uptime webhook on Monitoring. All sixteen failed in CI on the first v1.19.3 push.

  • Tests
    tests/dashboard-widget-jellyfin.spec.js

    and widgets_jellyfin_test.go, widgets_jellyfin_config_test.go, widgets_jellyfin_images_test.go and page_template_test.go cover the tile, its layouts, the setup, the cache, the image proxy and the template. tests/config-widgets-tabs.spec.js, tests/config-widgets-tab.spec.js and tests/config-widgets-wide.spec.js cover the three tabs, the rows and the side-by-side layout; widget-secret-reveal, widget-preset-address, config-widget-panel and config-unraid follow the new panel.

  • Tests
    tests/whats-new-spotlight.spec.js

    covers the spotlight and the releases since the last visit; digest_news_test.go and tests/digest-notice.spec.js the digest's news part.

  • Tests
    tests/whats-new-media.spec.js

    takes the What's new pictures and recordings through the real UI, one release at a time against a copy of the demo data, from a plan in tests/fixtures/whats-new-media/<tag>.js. The shared steps moved out of manual-screenshots.spec.js into tests/helpers/manual-shot-kit.js.

  • Tests
    TestContainerNotifierRecreateAnswersWhatWasTold, TestRunDueMonitorsOneSlowHostDoesNotStarveTheOthers, TestServerLogRetentionPassesUnstampedLines

    and two negative cases in TestCustomWidgetFormatting cover the four fixes above; each fails without its fix.

  • Tests
    tests/config-tag-suggestions.spec.js

    also covers the catalogue matching a subdomain through its parent domain, as one row.

  • Tests
    fixed sleeps became condition waits

    About six hundred waitForTimeout calls in the e2e suite wait for the state they were really waiting for: a tab's aria-selected, a save's response, a polled value. scripts/validate-test-waits.cjs, run in CI, fails a sleep that does not say with a // comment why the clock and not a condition. A few specs that raced the What's new window, the wall clock or the scroll lock were fixed on the way, and CI keeps the Playwright browser between runs.

  • Release
    release-to-main.sh refuses a dev HEAD without green CI

    The script scanned for vulnerabilities but ran no tests, so a red, still running or never pushed HEAD went to main as it was. It now asks gh for the CI run on that exact commit and stops unless it completed successfully; --skip-ci is the way past it, like --skip-scan.

Only docs and tests changed in this release.

v1.19.2 Config forgets the tab you had open once five minutes have passed, in every section, and a whole Tag suggestions row opens its group. 4 fix

Config forgets the tab you had open once five minutes have passed, in every section, and a whole Tag suggestions row opens its group. Held back from the What's new window (hideFromModal) like v1.19.1, so v1.19.0 keeps leading it.

Config

  • Fix
    a remembered tab expires after five minutes, like the config location

    Appearance, Behavior, Inbox, Containers, Status page and Unraid kept the tab you used last for good, so a tab picked once weeks ago still greeted you. nextdash:config-tab-v1 now stores { tab, savedAt } per section and counts a bare string from before as stale; time spent on a tab keeps it fresh, not only choosing it. The other sections, which kept their tab only for the life of the page, expire the same way against when config last showed them (resetExpiredTab, markTabSeen). A link or jump that names a tab still wins.

  • Fix
    a link to Status page or Unraid names its first tab too

    Both remember their tab, so a bare #config/status-page would land on a different tab for each reader; the address now always says which one is shown, as it already did for Appearance, Behavior, Inbox and Containers.

  • Fix
    the comments in dashboard-config.js

    say five minutes for the config location, not fifteen.

Bookmarks

  • Fix
    a click anywhere on a Tag suggestions row opens its group

    not only on the count. Its buttons, links and checkboxes keep their own action; the row shows a pointer.

Tests

  • Tests
    tests/config-tabs.spec.js

    covers a remembered tab expiring after five minutes, a tab expiring while the page stays open, and time spent reading a tab keeping it fresh; tests/config-tag-suggestions.spec.js opens a group by clicking the row's tag and its reason. tests/help-current-features.spec.js looks for the new Help → Config wording, the tab you had open; it still asked for the tab you used last and failed in CI.

Help and docs

  • Docs
    MANUAL §10.4, §16 and §17

    and Help → Config, Appearance and Behavior say a tab is kept for five minutes and a section opens on its first tab after that, in six languages; §10.4 says the whole row opens a proposal.

  • Docs
    the README

    links the demo at demo.nextdash.cc in place of the developer blog.

  • Docs
    the Unraid template

    lists v1.19.2 and keeps the last five releases, the same as the copy Community Applications reads.

Docs

  • Docs
    static/data/whats-new/v1.19.2.json and its index entry

    , held back from the What's new window (hideFromModal); whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v331, DASHBOARD_RELEASE stays on v1.19.0. tests/whats-new-hidden-release.spec.js names v1.19.2 as held back. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.19.1 Container updates show what they are doing while they run, and an update of a selection takes only the containers that have one and says why one failed. +3 3 fix

Container updates show what they are doing while they run, and an update of a selection takes only the containers that have one and says why one failed. The Bookmarks view gets its own row height, as tall as a row in Inbox and Containers by default. Held back from the What's new window (hideFromModal) like v1.18.4.1, so v1.19.0 keeps leading it.

Containers

  • New
    an update or rollback shows its steps and a log while it runs

    The page used to guess the phase with a timer. dockerRecreate and the rollback now report each step (check, pull, compare, tag, stop, rename, create, connect, start, remove, and restore when it puts the old container back) as it starts and ends, plus one log line per finished pull layer, to a sink on the context; without one — the nightly auto-update, the tests — nothing is sent. The action route streams them as NDJSON on ?stream=1, with the route's usual answer as the last line, so the page handles a streamed update exactly as a plain one. The progress window lists each container with its steps and the last 200 log lines; a finished one folds up with Done in N s or Already current, a failed one stays open on the step that broke with the reason, and the window waits for Close (ProgressOverlay.detail() and settle()). Specs: docker_progress_test.go, tests/docker-update-progress.spec.js.

  • Fix
    updating a selection takes only the containers with an update on offer

    It left out skipped and held ones but pulled the rest anyway and counted them as updated. The question now names the ones left out for having no update, says so and stops when none has one, and the closing notice counts already current apart. Skipped and held containers are left out without being named, since that was the reader's own choice.

  • Fix
    a bulk update names each container that failed, and why

    It ended on a bare 1 failed. explain() returns the reason it shows, a rolled-back update carries its own, and the notice lists them per container.

  • Fix
    a new run in the progress window is no longer hidden by the previous one finishing

    finish() hid the window 600 ms later on an untracked timer, which also closed a run that started in that gap; the timer is now cleared by show() and by the next finish().

Bookmarks

  • New
    row height is a setting under Config → Bookmarks → View

    Compact (the default) is 38 px, the height of a row in Containers and Inbox, so the three list views line up; Comfortable is the 46 px row the view had before. It replaces the toolbar's density buttons: the app-wide density no longer sizes these rows. bmViewRowHeight in the settings, is-rows-comfortable on the workbench; tests/bookmarks-view-settings.spec.js.

Config

  • New
    Config → Unraid's How it works says what the widgets can do

    refresh as often as you set, show as many rows as you choose, open the page in Unraid on a click, show more when wide, and send alerts for a stopped array, disk or parity errors and Unraid's own notifications (config.unraidHowWidgets).

Tests

  • Tests
    tests/config-bookmarks-redesign.spec.js

    expects the 38 px Compact row, as tall as an Inbox row; it still asked for the 46 px row the view had before and failed in CI.

Help and docs

  • Docs
    Help no longer says the Bookmarks view follows the app-wide density

    The everyday tip (tipEverydayDensity), Help → Bookmarks view, Help → Bookmarks view settings and Help → Appearance pointed at toolbar buttons that are gone; all four say where row height and density live now, in six languages.

  • Docs
    MANUAL §11.2, §14.2, §14.5, §16.6, §17.4, §17.7 and the quick reference

    describe the row height setting, the update progress window, what a bulk update takes and the Unraid explanation. The README's Containers list mentions the steps and log.

  • Docs
    translations

    of the update steps, the bulk update notices, the row height setting and the Unraid text in nl, de, fr, es and zh.

  • Docs
    the Unraid template

    lists the v1.19.0 and v1.19.1 changes and is dated 10 October, the same as the copy Community Applications reads; v1.19.0 had not reached it.

Docs

  • Docs
    static/data/whats-new/v1.19.1.json and its index entry

    , held back from the What's new window (hideFromModal); whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v330, DASHBOARD_RELEASE stays on v1.19.0. tests/whats-new-hidden-release.spec.js names v1.19.1 as held back. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.19.0 A status page for the people who use your services: a read-only page behind a secret link, set up under Config → Status page. +9 9 fix

A status page for the people who use your services: a read-only page behind a secret link, set up under Config → Status page. Around it, Config gets tabs for Unraid and a "new" mark in the section list, Bookmarks and the category titles draw faster with many bookmarks and containers, two theme fixes, and the build now checks for known vulnerabilities before anything is released.

Status page

  • New
    a page at /s/<token> for the people who use your services, with its data at /s/<token>/data.json

    It shows an overall line, a banner for planned maintenance, and groups of services, each with its state, since when it is down, 30 day bars, response time and uptime. The visitor's device picks the language and light or dark; the page refreshes every minute and pauses while the tab is hidden. It never shows error details, container images or internal addresses unless Link is switched on for a service. Config and token live in the store; every wrong address answers the same 404, /s/* allows 60 requests a minute per visitor (counted by the real client address behind a proxy), "Only from the home network" lets in private addresses the install can identify, and the token is kept out of the request log. The owner API sits behind the write token. Specs: tests/status-page-visitor.spec.js and the status_page_*_test.go files.

  • New
    Config → Status page

    Five tabs, All and then one per card: Link and access (turn it on, Copy, Open, a QR code, New link… which retires the old link at once), Top of the page, Groups and services (a picker offers a linked bookmark and container as one service) and Maintenance (windows per group). Sub-tabs and ℹ modals as on the other sections. Spec: tests/config-status-page.spec.js.

  • Fix
    editing a maintenance window under Behavior no longer drops the groups it is linked to

    The window was saved from the form's fields alone, and the link to the status page's groups is not one of them.

  • New
    the status page and Config → Status page speak all six languages

    The visitor page picked the language from Accept-Language, but its 32 strings had no statusPage.* keys in locales/, so every visitor read English; Config → Status page's 78 strings and the four Unraid tab names existed only as English fallbacks too. All of them are in locales/{en,nl,de,fr,es,zh}.json now.

  • Fix
    the command palette offers Config → Status page

    _CONFIG_SECTIONS in search-commands.js had no row for it, so typing config status found nothing. commands.configStatusPage is its label in six languages; tests/dashboard-command-palette-config.spec.js compares the palette against DashboardConfig.SECTIONS and failed without it.

Config

  • New
    Unraid has tabs

    All, Connection, How it works and What you get, as on the other sections; a tab hides cards instead of redrawing them, so the page no longer jumps when you move between sections. tests/config-unraid.spec.js covers it.

  • New
    a small "new" behind Structure, Containers, Unraid and Status page in the section list

    DashboardConfig.NEW_SECTIONS names them, and the mark is drawn from an attribute with empty alt text so the tabs keep their accessible names. Clear the list once the release is no longer recent.

Performance

  • Fix
    containers are matched to bookmarks once, not once per row

    containersFor ran bookmarkFor for every container on every row, so the work grew as rows × containers × bookmarks, and each call parsed addresses with new URL. docker-search-index.js now keeps the answer for every container until the container list, the bookmarks, the links set by hand or the host address change, and parses each address once. tests/docker-bookmark-link.spec.js fails without it.

  • Fix
    category titles are fitted together, not one at a time

    Each title was reset, measured and resized in turn, and every measurement forced a layout. dashboard-category-title-fit.js now fits all of them in a fixed number of layouts, however many there are. tests/category-title-fit-batched.spec.js counts the layouts.

  • Fix
    the Bookmarks list looks up its URL keys and its rows once when health lands

    The canonical key of an address is cached by the address as given (it depends on the string alone, so it cannot go stale), and the health repaint builds one lookup for all rows instead of walking the library for each. tests/bookmarks-health-repaint-cost.spec.js covers it.

Themes

  • Fix
    the newest theme stylesheet wins, and older ones go

    Two refreshes in a row (Use theme runs one inside applyThemeChoice and one after it) left two /api/theme.css links loading, and the second was put after the first only by position, so the older copy could come last, win the cascade and never be removed. visual-settings.js now replaces the last link and removes every link before the new one. tests/theme-css-reload.spec.js covers it.

  • Fix
    with several custom themes, the theme stylesheet has the same bytes every time

    Custom themes came out in map order, so with two or more of them every render after any data write hashed differently and the browser fetched the 600 KB file again. They are sorted now, as the built-in themes are. TestThemeCSSSameThemesSameBytes fails without it.

Inbox

  • Fix
    pasting a link the Inbox already holds opens a styled Inbox

    The answer to a duplicate is to open the view on the existing item, and that went straight to DashboardInbox.openInboxView, past the loader's, which was the only one to fetch the views stylesheet bundle. On a fresh dashboard the list then drew as bare markup. The module's openInboxView now awaits ViewStyles.ensureViewStyles itself, which also covers triage started from the dashboard. tests/dashboard-paste-choice-style.spec.js pastes a duplicate and checks the Inbox's rules have arrived.

Build and security

  • New
    Go 1.26 and a current golang.org/x/net

    govulncheck on Go 1.24 reported 29 advisories in the standard library, which this moves past. The Dockerfile builds with golang:1.26-alpine and runs on Alpine 3.24, and CI takes its Go version from go.mod.

  • New
    CI runs govulncheck on every push

    , pinned to v1.1.4 so a new release of the tool cannot change what passes.

  • New
    the release image is scanned with Trivy before it is pushed

    , in docker-publish.yml, which dev now tracks too.

  • New
    release-to-main.sh runs the same two checks first

    , through scripts/release-preflight.sh: govulncheck, and a Trivy scan of an image built on this machine. It needs Docker running, and --skip-scan skips it for an emergency. A finding in docker-publish.yml would leave a release with no image and no way out but a new patch version; this finds it before anything is merged, tagged or pushed.

  • Fix
    the browser extension's copy of bookmark-url-utils.js carries the URL key cache too

    The cache went into static/js/bookmark-form/ only, and CI's check-extension-bookmark-form.sh failed on the drift; sync-extension-bookmark-form.sh brought the copy level.

Tests

  • Tests
    tests/config-help-health.spec.js

    counts nine panels on Help → Monitoring, with the two for the status page. tests/whats-new-hidden-release.spec.js names v1.19.0 as the release the modal leads with.

Help and docs

  • Docs
    Help → Config lists Unraid and Status page

    among the sections and explains the "new" mark and the tabs they share with Inbox and Containers. config.sectionStatusPage was missing, so its label fell back to English in every language; it exists in all six now.

  • Docs
    MANUAL §12.8 and §23.10 and Help → Monitoring describe the status page

    , how to share it over the internet (proxy only /s/ and /static/status/, NEXTDASH_TRUSTED_PROXIES) and what to restore. The README lists it under Health and monitoring.

  • Docs
    Help → Monitoring's two status page panels open with a drawing and read in six languages

    Every Help article opens with one: a working and a down service for The status page, and the two paths a proxy should pass for Sharing the status page safely (HELP_PANEL_ART). Their bodies were English fallbacks in the code; config.helpStatusPage* now has them in every language, and the "new" mark in the section list (config.sectionNewBadge) is translated too.

  • Docs
    Config → Overview and About → News & features carry the status page

    , dated v1.19.0, in six languages.

Docs

  • Docs
    static/data/whats-new/v1.19.0.json and its index entry

    ; whats-new-stub.js moved DASHBOARD_RELEASE to 2026.10-dashboard-release-v1.19.0 and NEXTDASH_WHATS_NEW_DATA_VERSION one step. The Inbox fix above was listed under v1.18.4.1 after that release went out; it ships here, so it moved. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.18.4.1 Bookmarks opens sooner and the same way from the key as from the button. 8 fix

Bookmarks opens sooner and the same way from the key as from the button. Shift+H now lands on the whole list instead of the Broken filter, loading starts as the pointer reaches the button, the list is laid out and drawn once instead of several times, config no longer carries Appearance and the widget editor into Bookmarks, and a view opens with half the fade. Held back from the What's new window (hideFromModal) like v1.18.1, so v1.18.4 keeps leading it.

Bookmarks

  • Fix
    Shift+H opens the whole Bookmarks list, the same as its header button

    The key went through openHealthView, which landed on the Broken filter — the old Health view's front page — and did nothing at all with health checks off, so the key and the button opened two different things. dashboard-setup.js now calls config.openLibraryView, with no filter and nothing selected; :health and /#health still land on Broken. tests/bookmarks-shift-h.spec.js covers it.

Performance

  • Fix
    Bookmarks and Config start loading when the pointer reaches their button

    The first open after a page load waited on the whole module, a 1.7 MB script to fetch, parse and run — about 500 ms over a VPN. DashboardConfigLoader._bindIntentPrewarm listens once, delegated, for a pointer, a focus or a touch on either button and calls prewarm(), which loads the module, the help translations, the view styles and (with checks on) the health module without opening anything; a failure stays silent and the real open reports it. tests/config-lazy-load.spec.js covers the hover.

  • Fix
    the health loader no longer preloads scripts the page already has

    Two of its six dependencies ride in the dashboard bundle, but v1.18.4's side-by-side preload fetched them again. DashboardHealthLoader.DEPENDENCIES lists each script with its own readiness test, and only the missing ones are preloaded and loaded, still in order. tests/health-lazy-load.spec.js checks that every preloaded script is one that then runs.

  • Fix
    a view opens with a 100 ms fade instead of 200 ms of fade and slide

    Opening Config, Bookmarks, Inbox or Containers is a jump to another place, not a turn of the page, and the list is usually drawn within a frame; the animation was most of what made Bookmarks feel slow. dashboard.css gives those layouts dashboardViewFade; page switches on the dashboard keep the slide.

  • Fix
    opening Bookmarks no longer lays the empty view out first

    bookmarkRowWindow read the list's position and scroll offset while the shell was fresh, which made the browser lay out the whole view before a single row was in — and again once they were. A list of 120 items or fewer is drawn whole and is no longer measured at all; a longer one opened afresh takes its first window from a scroll of 0 and the window's height, and is measured one frame later, redrawn only if that differs. tests/config-bookmarks-window.spec.js covers the fresh open.

  • Fix
    Bookmarks no longer waits on Appearance's files, or on its own one at a time

    The config loader fetched the look, the studio and the theme editor (about 105 KB) with config itself, so opening Bookmarks parsed them before the list; they are now DashboardConfig.SECTION_MODULES.appearance, a chain fetched side by side and run in order when Appearance, the theme browser or a theme's look needs them, and on idle otherwise. A stand-in applyThemeLookAndSave on config loads them first, so :theme still brings a theme's look. The list's eleven scripts, which ensureBookmarkRenderers loads one after another, are preloaded with config by DashboardConfigLoader.preloadBookmarkScripts. Rows on a cold cache: 861 → 331 ms at 50 ms latency, 1130 → 605 ms at 4× CPU; warm, 340 → 323 ms. tests/config-lazy-load.spec.js checks that no Appearance file is fetched before the rows, and that Appearance and the theme browser still open.

  • Fix
    the widget editor is its own file, so Bookmarks no longer parses it

    The Widgets section's 98 methods (about 200 KB) moved unchanged from dashboard-config.js to dashboard-config-widgets.js, loaded as DashboardConfig.SECTION_MODULES.widgets when that section opens and on idle otherwise. The type tables and the helpers other sections share — the folds, secretEyeIcon, widgetTypeName — stay on the class. Config itself is 1.48 MB instead of 1.68 MB; Bookmarks' rows at 4× CPU: 308 → 292 ms warm, 593 → 575 ms cold. tests/config-lazy-load.spec.js checks that the file is not fetched before the rows.

  • Fix
    opening Bookmarks draws the list once instead of four times

    Every draw rebuilt the rows and measured their tag chips, which forces a layout. ensureBookmarkCategoriesForFilter and prefetchAllBookmarkCategories redrew the list whenever they finished, even with every name already cached; they now say whether anything was fetched, and only then is it redrawn — so a first open in a session redraws once when the names land, and every later one not at all. Two callers asking for the same page's categories share one request. The first draw takes a screenful (bmInitialLimit) when the page size is smaller, so fillBookmarkListToScreen no longer adds a page a frame later. The band's height is published from the last one and corrected by its ResizeObserver, instead of read mid-render; and the modal scroll lock no longer wakes on a child added to <body>, only on an attribute that could show a modal. Painted at 4× CPU: 323 → 274 ms; at 1×: 79 → 70 ms; cold, unchanged. tests/bookmarks-open-draws-once.spec.js counts the draws.

Tests

  • Tests
    tests/health-view-redirect.spec.js

    waits for #bookmarks after Shift+H instead of reading the address the moment the view switches: through openLibraryView the view switches first and its first render writes the address.

Help and docs

  • Docs
    the key is described as it now works

    MANUAL §7's key table and §11's opening line, the cheat sheet (navHealthView, which now shows with checks off too), the everyday-views tip (tipEverydayViews) and Help → Keyboard (helpKeyboardBody), in all six languages.

  • Docs
    the Unraid template

    lists the v1.18.4 changes, the same as the copy Community Applications reads.

Docs

  • Docs
    static/data/whats-new/v1.18.4.1.json and its index entry

    , held back from the What's new window (hideFromModal); whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v328, DASHBOARD_RELEASE stays on v1.18.4. tests/whats-new-hidden-release.spec.js names v1.18.4.1 as held back. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.18.4 The action bar's intro animation gets a choice of five styles, each shown on its own card in config. +2 7 fix

The action bar's intro animation gets a choice of five styles, each shown on its own card in config. The dashboard loads faster — the theme stylesheet is cached instead of inlined, a view's lazy scripts are fetched side by side, and a page-wide restyle while the grid renders is gone — and icons that went missing come back.

Dashboard

  • New
    five ways for the action bar's buttons to come into view

    Config → Appearance → The action bar → Animate the buttons as the bar appears is now a set of cards instead of an on/off switch: off, swell (left to right, from the middle, or together), unfold and accordion. Each card plays its own animation while it has the pointer or the focus, and a card you pick plays on the bar itself at once, without a reload. An install that had the animation on keeps it as swell.

Performance

  • Fix
    the theme stylesheet is linked by the hash of its content instead of inlined

    Inlining put ~600 KB into every HTML response and had it parsed on each load. templates/dashboard.html now links /api/theme.css?v=<hash> (themeCSSURL); a request carrying the current hash is served immutable for a year, anything else (a refresh after a theme change, a previewed backdrop roll) stays no-store. reloadThemeCSS in visual-settings.js swaps the link and still handles the inline form for a tab left open from before.

  • Fix
    the theme stylesheet is rendered once per change on the server

    Rendering walks every theme (331 blocks) and the page needs it twice per load, for the hash and for the fetch. themeCSSMemo keeps the last result, keyed by data revision and backdrop seed.

  • Fix
    asset bundles are gzipped once per bundle, not once per request

    The script bundle cost ~40 ms of gzip on every uncached load; ServeAssetBundle now keeps the compressed bytes per path and hash (gzippedBundle, default level — best was 0.4% smaller and half a second slower for the first visitor after a restart).

  • Fix
    a view's lazy scripts are fetched side by side

    The config and Health loaders run their scripts in order, and used to fetch them in order too: one round trip per file, a visible wait over a VPN. LazyScript.preloadScripts adds <link rel="preload"> for the whole chain; loadScriptOnce still runs them in the same order.

  • Fix
    no more page-wide restyle while the grid renders

    A .feed-row-actions:has(...) > * rule made Chrome restyle the whole page on every DOM change (16x the style work during render); feed-row.css lets the children out through the --feed-row-actions-child-overflow variable instead. The scroll lock's MutationObserver only re-checks when a batch touches a modal candidate, instead of forcing layout 36 times during load.

Icons

  • Fix
    icon-set SVGs that are only a wrapped PNG are served as the set's PNG

    The sanitiser turned them away, so the icon was a 404 and the row showed a letter. serveIconSetFile falls back to the .png of the same icon, and the index records which sets have one (iconSetEntry.PNG).

  • Fix
    Inbox items whose icon file is gone fetch it again

    An older cleanup removed icons while inbox.json could not be read; the items kept the name and every load asked for a missing file. inboxItemNeedsIconFetch now also picks up such items, and the startup backfill replaces the name, or clears it so the row shows its glyph.

Help and docs

  • New
    Config → Overview has a news item for the styles

    Five ways for the buttons to come into view, dated v1.18.4 and opening Appearance → Action bar.

  • Docs
    Help → Appearance

    names the styles on the Action bar tab, and MANUAL §4 has Buttons that come into view — the five styles, the playing cards, the pick that plays at once, when it plays and that reduced motion skips it; §16's tab line follows.

  • Docs
    the Unraid template

    has the Inbox under Bookmarks → Unsorted and Health inside the Bookmarks view, in its feature list and its v1.18.3 changes, the same as the copy Community Applications reads.

Tests

  • Tests
    internal/app/perf_cache_test.go

    covers the hashed theme link and its cache headers, the theme memo and the gzipped bundle cache; icon_sets_cache_test.go and inbox_icon_backfill_test.go cover the two icon fixes; tests/config-custom-themes.spec.js follows the linked stylesheet.

  • Tests
    tests/action-bar-autohide.spec.js

    plays each style on the bar, picks a card in config and checks its drawing plays on hover and that a second pick plays on the bar without a reload; the setting off draws no intro. internal/app/settings_action_bar_test.go keeps the five styles, turns anything else off, and moves v1.18.3's switch to swell.

Docs

  • Docs
    static/data/whats-new/v1.18.4.json and its index entry

    , leading the What's new window; whats-new-stub.js moves DASHBOARD_RELEASE to v1.18.4 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v327. tests/whats-new-hidden-release.spec.js names v1.18.4 as the release the modal leads with.

  • Docs
    locale keys

    actionBarIntroOff, actionBarIntroSwell, actionBarIntroSwellMiddle, actionBarIntroSwellTogether, actionBarIntroUnfold, actionBarIntroAccordion with their …Body lines and the five overviewNewFeatureActionBarStyles* keys in all six languages; actionBarIntroLabel, actionBarIntroInfoTitle, actionBarIntroInfoMessage and helpAppearanceBody updated in all six. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.18.3 A bug fix round from a review of the v1.18.0–v1.18.2 work. +3 34 fix

A bug fix round from a review of the v1.18.0–v1.18.2 work. The public demo no longer reaches the host's own network in its start-up window, and its capture routes are held to its write limit. Reverse proxies that add their own X-Forwarded-For line no longer let a visitor pick their rate-limit bucket. Two read errors that could lose data are closed: a page cached as empty, and icons deleted while inbox.json could not be read. On the dashboard, moving a block to another page is safe against a page switch and a second press. The inbox is now always on, and Structure and Behavior sit above it in the config rail.

Demo

  • Fix
    the start-up window no longer reaches the host's own network

    The window that fetches the seed's favicons and previews was open to every request, and visitors are served by then: /api/bookmark-preview could fetch a private or link-local address. In demo mode ssrfSafeDialContext now refuses local addresses whatever AllowLocalBookmarks says.

  • Fix
    GET /share and GET /add count as writes

    They write the inbox on a GET, so they skipped the write limit and the reset hold.

  • Fix
    a write cannot land in the middle of a reset

    Writes hold demo.writes shared while they run and resetDemo takes it whole, so a write that passed the gate just before the reset no longer survives it or mixes into the reseed.

  • Fix
    usage counters no longer arm the idle reset

    /api/track-* posts from a visitor who only reads set the idle clock and spent the write limit.

  • Fix
    the kept favicons are the seed's only

    A bookmark a visitor added or changed during the start-up window was kept and put back on every reset (fetchDemoIconsOnce).

  • Fix
    a removed demo container leaves the container order

    which otherwise grew by one id per recreate until the next reset.

  • Fix
    the start-up window is the seed round's, not the visitors'

    It was one global switch, so for the minutes the round took any visitor could make the server fetch a public address of their choosing, through a preview or a tag scan. Every request a visitor makes now carries a mark the dialer refuses whatever the window, and while the window is open a visitor's write is answered The demo is starting; try again in a minute, since the favicon and preview it would set off run on a context without the mark.

  • Fix
    a write during a waiting reset is turned away, not held

    The guard took the shared lock before it looked at the reset flag, and a reset waiting for the lock blocks new readers: a write arriving then hung until the reset was done and ran against the fresh seed, where a delete by index took another bookmark than the one on screen. The guard now tries the lock and answers 503 when it cannot have it (TryRLock in demoGuard).

  • Fix
    the demo's Docker refuses a name in use

    on create and on rename, as the real daemon does. Two containers answered to one name, and actions by that name hit either.

  • Fix
    a failed reset no longer has every open tab asking every three seconds

    The bar polled closely while the reset time was near or past; past by more than a minute it goes back to its 30-second round. The demo is starting is shown like the demo's other answers.

  • Fix
    the demo bar no longer carries the recording notice

    on a line of its own; Config → Privacy still says what the demo records.

Data

  • Fix
    a page that fails to read is not cached as empty

    GetBookmarksByPage held the empty result until the next write, and a save from a reader who saw it replaced the whole page. Only a missing file is cached as empty; GetAllBookmarks no longer marks itself complete when a page failed.

  • Fix
    icons are not deleted while inbox.json or a page cannot be read

    The cleanup after a delete took a failed read for an empty inbox and removed every icon only an inbox item used. iconReferenced and removeUnusedIconFiles now skip when either store did not read in full.

  • Fix
    X-Forwarded-For is read across every header line

    and an entry with a port or IPv6 brackets is still an address. A proxy that adds its own line (HAProxy option forwardfor) left the first line entirely the client's.

  • Fix
    Health's re-check past the cap puts rows without a URL key last

    Their result is never stored, so they stayed "never checked" and took a slot on every run.

Dashboard

  • New
    the action bar's buttons can swell into view

    Config → Appearance → The action bar → Animate the buttons as the bar appears, off by default. On, the buttons grow past their size one after the other and settle back each time the bar comes into view: after a load, once no modal, card or tour covers the screen, and on its way back from the edge it slid into.

  • Fix
    moving a block to another page no longer draws the old page's widgets on the new one

    A page switch while the move waited on the server set dash.widgets and blockOrder to the page left behind, and a later widget save wrote them over the new page. The source write now uses the stored list, and the dashboard is only touched while it still shows that page.

  • Fix
    one move to another page at a time

    A double press or held Shift + Alt + ←/→ ran two moves that could land a widget twice; the second is ignored, and so is key repeat.

  • Fix
    a picked-up block lets go when you type in a field

    Arrows, Enter and W went to the block while the search box had focus.

  • Fix
    Undo of a move puts nothing back after a background reload

    of the page, which would have undone what another device changed since; it says so instead (blockMoveUndoStale).

  • Fix
    moving a tag collection to another page answers at once

    Its "follows its tag" notice queued behind the 5-second Moved … Undo of a move just before and showed about five seconds after the key; it now takes that toast's place.

  • Fix
    the settings search reaches a setting in Containers, Inbox, Unraid or Logs on a first visit

    Those sections load their script on demand, and a jump into one that had not arrived yet switched to its tab before it was drawn and threw (renderContainersSection is not a function), so the focus never reached the control. activateSettingsJumpEntry now waits for ensureSection.

  • Fix
    Show in list (was Show in Health) draws a styled Bookmarks view

    From a bookmark's menu or Shift + R on a fresh load, the Bookmarks view came up without its stylesheet: openLibraryOnBookmark reached the module past the loader, which is what fetched views.css. openLibraryView and openConfigView now fetch it themselves. The entry is renamed now that Health lives in the Bookmarks view, with ▤ for ♥; Shift + R is unchanged. The bookmark menu sizes to its content, so no key chip is cut off any more — Shift+C beside Checking (Periodic)… read "Shi…". In Statistics, Open Health and Open in Health are now Open in Bookmarks, and so is the Open Health action on the health, trend, uptime, certificates, archive, unchecked and duplicates widgets.

  • Fix
    resetting spread counts only what was saved

    and puts the spread back on a category whose save failed.

  • Fix
    moving a collection to another page keeps it on its other pages

    A collection shown on pages 1 and 3, moved from 1 to 2, was left on page 2 only: the move set its page list to the one page it went to. It now swaps the page it left for the one it went to; a collection on every page still goes to that one page.

  • Fix
    a collection's width that cannot be saved is reported once

    The settings save says so itself, and the move said it again.

  • Fix
    the action bar's swell stops waiting when it cannot play

    With the bar in the menu, the swell switched off, or the screen busy for two minutes, it watched every change on the page for the rest of the session.

Bookmarks

  • Fix
    merging categories in the Structure modal cannot save an empty list

    A reload during the confirmation forgot the lists, and the merge posted [] for the page, removing every category (mergeCategoryInto).

  • Fix
    deleting a category in Structure finds it again after the confirmation

    so a reload meanwhile no longer gives a Category deleted. for a category still there.

  • Fix
    a bulk move to another page removes the moved rows by identity

    not by indexes taken before the requests, and leaves the list alone when you went to another page meanwhile.

  • Fix
    the script loader finds a failed tag

    The selector used the camelCase dataset key, which never matched the attribute, so the failed-load check never ran.

Inbox

  • Fix
    bulk Keep runs once at a time

    a double click reported links as still in the Inbox that were not.

  • Fix
    bulk promote says when an entry could not leave the Inbox

    and keeps those out of its count and its Undo.

  • Fix
    a quick second key in triage acts on the next card

    r, d or Shift+K pressed while the card before was still being written was dropped, since the card was still claimed; it now waits and runs on the card after. Open is left out: a tab opened after the wait is a popup the browser may block. Seen as inbox-triage-piles.spec.js:96 failing in CI run 619.

  • New
    the inbox is always on

    Config → Inbox → Enable the inbox is gone; the server sets inboxEnabled to true on every read and save, so an install that had turned it off gets the inbox back. Paste-to-inbox, the 0 key and :inbox follow. Its four inboxEnabled* strings are gone from the locale files.

  • New
    Structure and Behavior sit above Inbox in the config rail

    The order is now Overview, Appearance, Bookmarks, Structure, Behavior, Inbox (DashboardConfig.SECTIONS, and the copy in DashboardConfigLoader.SECTIONS that reads a deep link before the module loads).

What's new

  • Fix
    the section menu filters the headline release only

    not the older releases opened below it.

Only docs and tests changed in this release.

v1.18.2 The public demo gets statistics of its own, kept apart from those of real installs, and its Privacy & sync tab is locked. +3 27 fix

The public demo gets statistics of its own, kept apart from those of real installs, and its Privacy & sync tab is locked. A fix for installs behind a reverse proxy, the public demo among them: a visitor can no longer choose the address the write and fetch limits count them under. Also a round of bug fixes across the dashboard, Bookmarks, Inbox and Health: two paths that could empty a page or the inbox after a read error, lost updates between a save and a background write, and a set of keyboard, triage and edit-form edge cases. v1.18.2 leads the What's new window, and v1.18.1, held back when it shipped, shows under it.

Demo

  • New
    the demo counts its visits in a website of its own

    NEXTDASH_DEMO_ANALYTICS_ID names a separate Umami website; in demo mode only that id is ever written into the page, never the one real installs use, and a real install never gets the demo id. Snapshots stay off and the install ping is off in demo mode. recorder.js loads for heatmaps and replays, with data-do-not-track on both scripts, and the demo bar says so. Every event carries mode: 'demo', and demo:refused, demo:cta, demo:reset-seen, demo:intro and demo:session-depth (in bands) show what visitors try.

  • New
    typed text stays out of the demo's addresses

    The tracker sends only path and view (data-exclude-search, data-before-send), and in demo mode the Inbox and bookmark searches are not written into the URL, so replays and pageviews never carry what a visitor typed. Real installs keep their search deep links.

  • New
    Config → Behavior → Privacy & sync is locked in the demo

    Every panel on the tab is disabled with the lock chip, :telemetry is locked in the palette, and the server keeps the stored values for the tab's fields when the demo saves settings.

  • Tests
    telemetry_test.go

    covers which website id lands on the page in every mode and that the demo keeps the Privacy & sync values; tests/demo-analytics.spec.js checks the script tags, the events, that no typed text reaches an address in the demo (and does on an ordinary install), and the locked tab.

Data

  • Fix
    a page file that cannot be read is no longer saved as an empty page

    SavePage treated any read error as "new page", so one failed read while pages were renamed or reordered wrote that page back with no bookmarks. Only a missing file is new now; any other error is returned.

  • Fix
    an unreadable inbox.json is no longer overwritten

    A read or decode error gave an empty inbox, and the next add — from the extension, say — saved that over the file. Every inbox write now reads through readInboxDataForWriteLocked and stops on the error; the list still reads as empty.

  • Fix
    saving a page keeps opens and check results written meanwhile

    SaveBookmarks copied the server-owned fields from a read taken outside the store lock, so an open or a monitor result landing in between was lost. The copy and the write share one lock now (SaveBookmarksByPageCarrying).

  • Fix
    merging duplicates no longer writes back older copies of the pages

    MergeDuplicates read, cut and saved whole pages outside the lock; it runs inside MutateBookmarkPages, and a request that does not match the stored pages still answers 400.

Dashboard

  • Fix
    Shift + Alt + ←/→ moves a bookmark into the category beside it

    It asked renderCore for a method only the dashboard has, so the move never ran.

  • Fix
    the walk hints beside the page strip keep working after a page is added or deleted

    The click handler kept the page list from its first call; it reads d.pages now.

  • Fix
    a background reload no longer cancels a page you just clicked

    The revision check on window focus shared the load id with page switches, so the click's load gave up and the old page was drawn again. Quiet loads skip while a load you started is running.

  • Fix
    keyboard moves skip what is hidden

    Alt + ↑/↓ swapped with rows behind show more or hidden by a filter, and the arrow keys in the page tabs landed on tabs folded away, leaving the tab list without a tab stop.

  • Fix
    Alt + → on the // leaves the focus on the //

    not the title, so the next Space picks the block up instead of folding it.

  • Fix
    a failed category rename or icon change is put back

    saveCategoryOrder swallowed its own failure, so the rollbacks around it never ran; it answers true or false now.

  • Fix
    the peek card goes with the rows it belongs to

    on a full render, and a malformed #docker/… address no longer replaces the dashboard with the error page.

Bookmarks

  • Fix
    editing a URL and moving the bookmark to another page no longer leaves a duplicate

    Picking a page reset the form's baseline to the edited values, so the delete on the old page used the new URL and missed. A place change now re-baselines only page and category, which also keeps Esc from dropping earlier edits without asking.

  • Fix
    a shortcut used on another page is caught in the form

    whatever global shortcuts says. The server refuses it either way, and caught only there the form had already closed with the edits in it.

  • Fix
    bulk delete and move act on the rows as they are after the dialog

    A refresh while the confirm or Move popover was open left old indexes behind, and the delete removed other bookmarks. The page move passes its rows in instead of swapping the tag filter's reader for the duration.

  • Fix
    right-click and ; recover from a failed module load

    The failed script tag stayed and every later try waited on it until a reload.

  • Fix
    smaller ones

    the multi-select mark survives a smart-collection refresh and a cancelled edit; the duplicate check in the form uses the server's URL key; the Bookmarks panel's shortcut field keeps letters only.

Inbox

  • Fix
    one failed refresh no longer empties the list

    The inbox showed No links yet and every keep or delete after it failed (loadItems).

  • Fix
    no double actions

    Open and mark read in triage, and Keep and Delete in the side panel and the right-click menu, run once per card while one is pending; a held or double press opened a link twice or skipped a card unseen.

  • Fix
    after d, K or z the next card is the current copy

    with its preview; Keep from the old copy saved the bookmark with the domain for a name.

  • Fix
    a keep whose inbox cleanup fails says so

    instead of Kept, and the card stays; bulk Keep counts and undoes only what the batch removed.

  • Fix
    two tag suggestions clicked quickly both stick

    added on the server instead of each sending the whole list.

  • Fix
    fetched titles and descriptions are capped like typed ones

    and an icon fetched for a link deleted meanwhile is removed.

Health

  • Fix
    Retest all past 250 bookmarks takes the least recently checked first

    It took the same first 250 in page order on every run, and the rest were never re-checked.

  • Fix
    a write during a report build no longer leaves a stale report for three minutes

    an invalidation during the build keeps it unmarked (healthReportInvalidations).

  • Fix
    a re-check that could not be saved or was refused says so

    The status write was not checked, so a failure still showed Reachable again; p in the review session drops no result; a refresh asked for during another one runs once more after it.

  • Fix
    skipped in a batch status update counts URLs

    and is no longer negative when a URL is on two rows.

Security

  • Fix
    the client address behind a named proxy comes from the right of X-Forwarded-For

    A proxy such as Traefik or nginx appends the address it saw and keeps whatever the request already carried, and clientIP() took the first entry: a visitor who sent their own X-Forwarded-For picked a fresh rate-limit bucket on every request, which emptied the demo's 120 writes a minute per address and the limits on /api/bookmark-preview, /api/icon/from-url and /api/ping. The header is now read from the right: each address inside NEXTDASH_TRUSTED_PROXIES is skipped and the first one before them is the client; garbage on the way still falls back to the peer.

Tests

  • Tests
    TestClientIPIgnoresWhatTheClientPutBeforeTheProxy

    sends fifty requests through a named proxy, each with a made-up address in front of the real one, and expects one bucket; a chain of two proxies gives the address before them. It fails on the old first-entry read.

  • Tests
    TestInboxAddRefusesUnreadableInbox, TestSavePageRefusesUnreadablePageFile and TestRetestAllOverCapTakesOldestChecked

    and two Playwright tests: Shift+Alt+ArrowRight in tests/dashboard-alt-move-bookmark.spec.js and the walk hints after a page is added in tests/dashboard-page-strip.spec.js. Each fails without its fix.

Docs

  • Docs
    static/data/whats-new/v1.18.2.json and its index entry

    ; whats-new-stub.js moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v324 and DASHBOARD_RELEASE to v1.18.2, so the What's new window opens again. v1.18.1 loses its hideFromModal, and tests/whats-new-hidden-release.spec.js expects v1.18.2 to lead with v1.18.1 under it. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.18.1 Moving a block with the keyboard works without a Home key and without opening a bookmark on the way: the up arrow reaches a block's title, Tab its //, and Space there picks the block up. +4 5 fix

Moving a block with the keyboard works without a Home key and without opening a bookmark on the way: the up arrow reaches a block's title, Tab its //, and Space there picks the block up. Focus on a title and on its // wears the selected row's tint. Help has a panel of its own on moving categories and widgets, with drawings that move, and the dashboard tour, tips, cheat sheet and manual follow. Held back from the What's new window (hideFromModal), so v1.18.0 keeps leading it.

Dashboard

  • New
    ↑ on the top row of a block steps onto its title

    Shift + Home was the only key that reached a title, and most Mac keyboards have no Home. On the top row of a category, collection or widget — every column's top row in a spread category — ↑ now focuses the title and leaves the cursor on the row; ↓ goes back to that row and ↑ again goes on to the block above. ← and → keep walking the columns, also from a title.

  • Fix
    Tab on a title reaches its //

    With the grid cursor on, Tab walked to the next row and stepped past the handle, so the keyboard pick-up the intro and Help describe could only be reached by tabbing through every bookmark before it. Tab on a title now goes to its //, and Shift+Tab on the // back to the title; where the terminal layout hides the //, Tab falls through as before.

  • Fix
    Space on the // and Enter on a title no longer open a bookmark

    The cursor stays on its row while the focus is on the title, and the grid's own keydown, which runs first, opened that row in a new tab before the block was picked up or folded. Enter and Space are left to the title and the mover while one of them has the focus.

  • Fix
    widget rows only a wide tile shows are no longer cursor stops

    A narrow Health tile kept them in the DOM, drawn as nothing, so ↓ put the cursor on a row nobody could see and ↑ found one "above" the top row (_isNavigableWidgetElement now asks for client rects).

  • Fix
    after a keyboard drop the focus stays on the //

    redrawKeepingPlace put it back on the title on every settle frame, so the next Space no longer reached the block just placed; it now restores the element that had it.

  • Fix
    focus on a title and on its // in the row tint

    A focused title wears the selected row's tint (--bookmark-row-selected-bg) instead of a 2px ring, and a focused // a small chip of it around the two slashes, which now sit in a span of their own. The ring around the handle took the space after // and the title's letter spacing along, and .category-title-label's overflow: hidden cut it to its top and right sides. The header styles that draw a grip tint the grip the same way.

Help and docs

  • New
    Help → Structure & bookmarks → Moving categories and widgets

    A panel of its own, opened by three looping drawings — the landing box, the column line that makes a block wide, and a block sent to another page — and the keys from a bookmark without the mouse. The drawings rest on where the block ended up, so with animations off or reduced motion they show the result. The three bullets on moving in the Structure panel became a pointer to it.

  • New
    the dashboard tour opens on moving a block

    A first step, New: move categories and widgets where you want them, carries a category from one column to the next with the dashed box ahead of it and the keys beside it; the tour has 21 steps. Its tip id is unchanged, so readers who finished the tour are not shown it again.

  • New
    a tip for moving without a mouse

    (tipEditMoveBlockKeys), and the cheat sheet has Tab on block title, with ↑ beside Shift + Home on the category and widget header rows; nextDash-cheatsheet.pdf is regenerated.

  • Docs
    MANUAL

    §7.4 has ↑ and Tab, and §9.2 the keyboard route and an animated drawing of the three moves (screenshots/manual.md/09-move-block.svg).

Tests

  • Tests
    tests/dashboard-block-move-keyboard.spec.js

    drives the keys: arrows and Shift+Home to a title, Tab and Shift+Tab, Space, arrows and Enter, from a row lower in the block; ↑ from a top row and ↓ back to the same row; → from a title to the next column; Space on the // and Enter on a title with no page or tab opened; the focus tint on the // in all six header styles and on a title. Each fails without its change.

  • Tests
    tests/config-help-move.spec.js

    opens Help on the panel, finds the three drawings and the keys, checks the loop runs, and that with reduced motion the block rests where it landed. tests/dashboard-tutorial.spec.js and tests/dashboard-tutorial-contrast.spec.js follow the 21 steps.

Docs

  • Docs
    static/data/whats-new/v1.18.1.json and its index entry

    with hideFromModal; whats-new-stub.js moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v323 and leaves DASHBOARD_RELEASE on v1.18.0. tests/whats-new-hidden-release.spec.js names v1.18.1 as held back.

  • Docs
    locale keys

    helpMoveTitle, helpMoveBody, helpArtMovePlace, helpArtMoveWide, helpArtMovePage, helpArtMoveKeys, tipEditMoveBlockKeys, cheatsheet.bmTitleToHandle and the eight dashTourMove* keys in all six languages; helpKeyboardBody, helpWorkspaceBody, cheatsheet.navCategoryHeader and cheatsheet.wgHeader updated in all six. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.18.0 Categories, widgets and collections move on the dashboard itself: a landing box shows where a block will land, the column line makes it wide, the keyboard can carry it, and it can go to another page with Undo. +13 9 fix Read the post

Categories, widgets and collections move on the dashboard itself: a landing box shows where a block will land, the column line makes it wide, the keyboard can carry it, and it can go to another page with Undo. Structure → Categories becomes one grouped table for every page. The What's new window is rebuilt around cards, the theme browser gets More filters and Reset all, and a demo mode runs the public demo. v1.18.0 leads the What's new window.

Dashboard

  • New
    move a block with a landing box

    Dragging the // before a category, widget or collection title no longer reflows the page under the pointer: the page holds still and a dashed box shows where the block lands, with a label (after Media · 2 columns). Dropping on the line between two columns makes it wide; W or Shift while dragging switches. Categories, widgets and collections share one path and one order.

  • New
    move a block with the keyboard

    Space on the // picks it up; the arrows move the landing box a place sideways or a row up or down, W switches one column and wide, Enter drops and Esc cancels, with each step announced. Alt + ←/→ on a title still moves it one place.

  • New
    move a block to another page

    Move to page ▸ in the right-click menu of a category, widget or collection, or Shift + Alt + ←/→ on its title, sends it to the end of that page. A category takes its bookmarks along; when some are already on that page, only the others move and the notice says the category is on both pages. A tag collection is not offered, since it shows wherever its tag is, and Lock layout blocks every move with a notice saying where to turn it off.

  • New
    undo a block move

    The notice after a move has Undo, and Ctrl/Cmd + Z does the same while it shows, on this page or across pages.

  • New
    a one-time intro and a first-move card

    Once, a see-through copy of the first category glides to its next place with the real landing box and back, and a card under its // offers Try it; nothing on the page moves or is saved. The first pick-up shows a card beside the landing box with the keys, until Got it or Escape. Both are remembered server-side as tips, so Replay tours and tips brings them back.

  • New
    the cheat sheet lists the block keys

    under Bookmarks, and the printed sheet carries them too.

  • Fix
    a collection keeps its place and width

    A collection's id in the block order was dropped on save unless it was a category or widget, so a collection moved among the categories jumped back to the end after a reload, and a collection made two columns wide went back to one. Collection ids now survive the order merge, and collectionColumns and a user collection's page list survive a save and a read.

  • New
    new categories spread across columns by default

    DefaultCategorySpread is true in both defaults blocks, and GetSettings sets it for a settings file without the key; a stored false stays.

Structure

  • New
    one grouped categories table

    Structure → Categories lists every page's categories in one table, grouped by page; a page's row folds its group for the session. Chips above it narrow the table to pages and to a view (All, Spread, With broken links, Empty), the summary counts categories, bookmarks, spread ones and broken links, and the sort adds Most bookmarks and Most broken. The order of categories is set on the dashboard, so the rows no longer carry move buttons. Pages, Finders and Collections take the same list-view look with column heads; a collection row reads its rules as one line.

  • Fix
    the Spread heading fits

    Its column was a fixed 4rem, so the Dutch Uitgespreid ran into Kapot; the column now grows to its heading (minmax(max-content, 4rem)).

Themes

  • New
    Reset all in the look studio

    Beside Reset tab, Reset all puts backdrop, surface, headers and looks back to a fresh install's answers for every theme; Layout and the theme itself stay. The server serves those defaults so the client never guesses them.

  • New
    More filters in the theme browser

    The character and collection chips fold under More filters. Folded, the filters that are on show as removable chips and the button counts them, and the In use line ends with 18 of 165 · 3 ★.

  • Fix
    the page scrollbar follows the theme

    --hairline-strong lives on body but the page scrollbar is styled from html, where the property was invalid, so the browser's own scrollbar showed: a white strip down every dark theme with always show scrollbars on. The scrollbar now mixes from the border colour html has, with the track in the page colour.

What's new

  • New
    a roomier window

    The modal is wider and taller. A release reads as a digest: new changes first as cards with their explanation, fixes after them as one line each with the explanation in a native disclosure, shortcuts in their own group. One section menu replaces the row of tabs that ran off the right edge; it narrows both lists and is left out for a release with one section.

  • Fix
    the footer keeps its height on a narrow screen

    Stacked, the 12rem basis meant for the row became a height.

Bookmarks view

  • Fix
    the header band is see-through at rest and nearly solid once scrolled

    so rows and tiles no longer show through it while they pass behind.

Browser extension

  • Fix
    a first setup lists pages and categories

    right after Save Settings, from the address in the field, without reopening the popup.

  • Fix
    a second quick save keeps its badge mark

    The first save's timeout cleared the badge of a save made within 3.5 seconds; one badge now has one timer.

  • Fix
    icons at their real sizes

    16, 48, 128 and 256 px, drawn from the app logo (extension/icons/).

  • Fix
    the unused confirmation dialog is gone

    from the popup, with its strings in all six languages.

  • New
    server-access messages

    when the browser has not granted access to the nextDash address (msgServerAccessDenied, msgServerAccessNeeded, in all six languages).

Server

  • New
    demo mode

    NEXTDASH_DEMO=1 runs the public demo: seeded from the three bundled templates with dates relative to the reset, a month of health and feed history, three kept links and link previews fetched once, a fake Docker daemon with its own registry and changelog, and a fake Unraid server. It resets every NEXTDASH_DEMO_RESET_MINUTES (default 30) and after NEXTDASH_DEMO_IDLE_MINUTES (default 10) without a write, checks no site and reaches no other host, refuses what would replace data, upload or send, bounds request bodies and the inbox, and shows a demo bar and no What's new by itself. It needs NEXTDASH_DATA_DIR set to a directory of its own and refuses one that holds data without its .nextdash-demo marker.

Tests

  • Tests
    block moving

    tests/dashboard-block-move.spec.js, -keyboard, -page, -coach, tests/dashboard-block-move-intro.spec.js, tests/dashboard-collection-move.spec.js and tests/block-move-model.test.cjs; collection_block_test.go saves and reads collection ids, widths and page lists.

  • Tests
    tests/config-structure-categories-grouped.spec.js

    covers the grouped table, its chips and folding; config-structure-table.spec.js and config-pages-tags.spec.js follow the new rows.

  • Tests
    category_spread_default_test.go

    : a fresh install and a file without the key spread, a stored false stays.

  • Tests
    tests/theme-browser-more-filters.spec.js

    , tests/look-studio-reset-all.spec.js and look_defaults_test.go; tests/whats-new-modal.spec.js follows the digest.

  • Tests
    demo_test.go

    covers the marker refusal, the reset and the refused routes; tests/extension-popup.spec.js covers a first setup.

  • Tests
    tests/whats-new-hidden-release.spec.js

    names v1.18.0 as the release the modal leads with.

  • Tests
    three specs follow this release

    dashboard-widget-keyboard.spec.js focuses a widget row rather than the first button, which is now the // move handle; dashboard-alt-move-bookmark.spec.js expects Alt+→ to pass the next block, which can be a collection now that collections keep their place in the order; list-view-header-surface.spec.js lets the band be see-through at rest and expects it nearly solid once the page has scrolled.

  • Tests
    two races in specs, found by this release's CI

    bookmarks-structure-modal.spec.js (Move all bookmarks to… brings their categories along) waited for as many posted category ids as the source page had, but the body also carries what the target page already holds, so the count could be reached before the last category was posted; it now waits for the categories by name. config-bookmarks-fetch.spec.js (fetching previews walks the selection) read the button's count while the side panel's own preview request was still out; when that answer landed first the row had a preview and the sweep skipped it, asking one where the button said two, or none and showing no bar. The panel's requests are now held until the sweep has started.

Docs

  • Docs
    Help, tips, MANUAL and README

    cover moving blocks, the grouped categories table, spreading by default, More filters, Reset all and the new What's new window; MANUAL §23.9 and the README variable table describe the demo variables.

  • Docs
    translations

    the 97 strings added since v1.17.5 in all five languages, eight theme browser and look studio strings that were missing from every locale, the two extension server-access messages, and the two Overview spotlights below.

  • Docs
    static/data/whats-new/v1.18.0.json and its index entry

    ; whats-new-stub.js moves DASHBOARD_RELEASE to 2026.10-dashboard-release-v1.18.0 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v322. Two spotlights in overview-features.json with since: "v1.18.0". go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.17.5 Config → Overview names the running version in a panel of its own, with a dot that says whether it is the newest release. +8 23 fix

Config → Overview names the running version in a panel of its own, with a dot that says whether it is the newest release. The update check uses the Containers GitHub token, waits out GitHub's hourly limit and says why it failed. v1.17.5 leads the What's new window, and the five releases held back before it (v1.17.4, v1.17.3, v1.17.1, v1.15.4 and v1.15.1) now show under it.

Config

  • New
    a Version panel on the overview

    It sits between Latest news and New in nextDash and reads You're running v1.x.y of nextDash, with links to the full changelog and the manual on GitHub, each opening in a new window. The text has the same size as the other panels. The panel appears once the update check knows the running version, also when the site's news is switched off.

  • New
    green or red for the running version

    The dot before the panel title is green on the newest release and red when a newer one is out, also after the update notice was dismissed; no dot when GitHub was not asked or could not be reached. When behind, a second line in red says which release is available, its tag a link to the release on GitHub.

  • Fix
    the "Running vX" note under New in nextDash is gone

    the Version panel says it instead.

  • Fix
    the section rail no longer slides under the section band

    Once a long section was scrolled, the sticky band (title, description, Only changed, the settings filter) covered the rail's heading and half of Overview. The rail kept a flat top: 8px from before config had a sticky band; it now sticks at the band's height plus 8px. The band's height is published as --lvs-header-height on .config-view and re-measured when its description wraps.

  • New
    choose the pages Fresh shows on

    Config → Structure → Collections → Collection scope has a “Fresh” pages row beside Today, Recent, Stale and Most used. The dashboard already read smartFreshPageIds, but Settings had no such field, so the save dropped it and Fresh stayed on every page. The field is now in Settings, both defaults blocks and the missing-key handling in GetSettings, and in the client defaults and load normalisation.

  • Fix
    the MCP panel names a script or another tool

    Data & backups → Webhooks called it Assistant access. It is now MCP access, for a script or another tool, and the toggle reads Answer MCP clients at this address.

  • Fix
    Data & backups opens with a line that fits every tab

    The band above the tabs read Back up your data, restore an earlier snapshot, or move it in and out of nextDash. on all six tabs, though only Backups & data does that. It now reads Keep your data safe, move it in and out, and manage what nextDash stores on this disk. (config.dataBackupsIntro, in all six languages).

  • Fix
    the line under a tab strip follows the open tab

    In Data & backups, Bookmarks and Help, switching tabs repainted only the body, so the note under the strip kept describing the tab the section opened on. A shared syncSectionTabNote now swaps, adds or drops the note on every tab switch, as Stats already did.

Update check

  • Fix
    the check no longer runs into GitHub's hourly limit as often

    Without a token GitHub allows 60 requests an hour per public address, shared with the container changelogs, other tools on the network and, behind CGNAT, the neighbours; past it the check failed with "Could not reach GitHub". It now sends the GitHub token from Config → Containers → Updates when one is set (5000 an hour), and asks the release listing with If-None-Match, so an unchanged answer comes back as a 304 that does not count against the limit. A token GitHub refuses is dropped for that request instead of failing the check.

  • Fix
    on GitHub's limit the check waits for the reset

    It reads X-RateLimit-Reset and tries again then, instead of every 15 minutes; Check now and the /releases/latest fallback no longer spend a request to hear the same answer. When nextDash's own outbound limiter turned the request down, it tries again after a minute.

  • New
    a failed check says why

    /api/update-status adds errorCode (rate-limited, local-limit, unreachable, http), retryAt and authenticated. The Version panel and the What's new bar name the reason: the hourly limit with the time of the next try and, without a token, where to set one; GitHub out of reach; or GitHub's own answer.

Widgets

  • New
    choose a widget's page in its settings

    Config → Widgets → Settings has a Page select above Width when there is more than one page. Choosing another page moves the widget there straight away, at the end of that page, with its id, credential and collapsed state; unsaved changes in the panel ask first. It uses the bulk bar's move.

  • Fix
    the Custom widget counts the services it offers

    Config → Widgets → Types said 45 services in four groups: PRESETS.length counted the three retired presets (Readarr, Pi-hole v5, TrueNAS) and qBittorrent's two entries. It now says 41 services in five groups. qbittorrent-key carries variantOf: 'qbittorrent', and a new serviceCount() in dashboard-widget-presets.js leaves out retired presets and variants.

  • Fix
    the widgets tour's preset step said twenty-eight services

    It now says forty-one, names monitoring beside the other kinds, and its chips show Uptime Kuma instead of the retired TrueNAS, with "…and twenty-two more" after them.

Dashboard

  • Fix
    with less motion, the pages and recents panels stay on the strip

    When the system asks for reduced motion, or Animations is off, the reduced-motion rule for every modal and the app-wide no-animations rule cleared transform, and with it the translateX(-50%) that centres a header sheet on the strip: the pages panel (,) ran off the right edge of the window and the recents panel (*) sat half its width to the right. The header sheets are left out of those rules and keep their centring; they still open without animation.

  • Fix
    unticking a notes box right after ticking it is saved

    Ticking saves the line but does not redraw the tile, and the box kept the line as it was drawn; a second click on the same box found no such line, redrew the tile and lost the click, so the box jumped back. After a save the box now holds the line as saved.

  • Fix
    Re-check on the selection bar counts what each check answered

    Every ticked row was counted as re-checked, also when the dashboard's own ping limit (429) or the network refused it, and a refused row was never asked again. recheckIssue now answers ok, skipped, failed or a rate limit with its Retry-After; the dashboard's bar and the Bookmarks view's bulk Re-check pass it to BulkSweep, which waits out the limit and asks once more.

  • Fix
    a tablet shows the time once

    With a touch screen wider than a phone, the header drew the clock and, under it, the mini status line repeating the same time before the page name and bookmark count; a 768px window did the same. The mini status no longer copies the clock and keeps the page name and the count.

  • Fix
    the pages panel opened a second time puts the cursor on your page again

    Closed with Escape and opened again, it came up with the focus on nothing, so the arrow keys and Enter did not reach the list. AppModal focuses a dialog's chosen element two frames after it opens, once; reopened straight after closing, the overlay is still visibility: hidden at that moment and focus() does nothing. The chosen element now gets the same few tries across the fade as the fallback already had, which covers every dialog that names one.

  • Fix
    a setting you change while the dashboard refreshes stays changed

    When another device saves settings, the dashboard reads them again. Changing one here while that read was still on the wire let its answer, taken before your save, replace the settings on screen: the header went back to its old style while the server held the new one, and stayed that way until a reload, because your save had already told the poll there was nothing left to fetch. loadData now looks at when this tab's last settings write left: sent after the read, it reached the server after whatever the read saw and carries the whole object, so the settings on screen are kept; already on its way when the read left, the order is unknown, so it waits for the write and reads again; otherwise the answer is applied. A first try counted any save still running as crossing the read, and backlog-batch-three.spec.js caught it in CI: a save that had already landed before the other device's change kept that change off the screen.

  • Fix
    a spread category keeps its names as wide as a plain one

    The gap between spread columns fell between every track of the repeated row pattern, so the name track lost about two seams per column and Weather radar came out Weather r…. Each row in a spread list now lays out its own tracks inside one track per column.

  • Fix
    a Notes widget you removed stays removed

    The one-time step that puts a Notes widget on the first page recorded itself in a marker that Settings had no field for, so the next settings save dropped it and the widget came back after a restart. NotesWidgetSeeded is now a field and survives a save like the other markers.

Server

  • Fix
    Retry on a stopped feed fetches that feed only

    It reset the feed and then polled every feed on the install while the request waited, up to a minute; a limited round now takes only the reset feeds and leaves the scheduled round's time alone.

  • Fix
    page template imports run one at a time

    A new page's id was read before it was written, and an empty page checked before it was filled, so two imports at once (two tabs) took the same id or filled the same page and the second overwrote the first. The import now holds a lock from those checks to its last write.

  • Fix
    template labels are cut by character

    A host label over 60 bytes was cut mid-character, which showed as � in the file and the import dialog; it is now cut at 60 characters (truncateRunes).

  • Fix
    /api/notify/quiet loads the time zone once

    Working out when the quiet hours end read the zone file once per minute stepped, up to 2880 times a request.

Bookmarks

  • Fix
    Unsorted is called Unsorted, not 999999

    In Bookmarks → Unsorted grouped by page, the group header read 999999 and so did the location line in the side panel. Kept links live on a hidden page that is not in the page list, and pageLabel fell back to its id. It now returns Unsorted (config.bmViewUnsorted) for that page, which also fixes the row crumb, the Usage tab and the bulk category list for kept links.

First start

  • New
    a new install asks what you run

    A card at the top of the first page, before the quick-start checklist, offers three bundled templates — Homelab (Proxmox, a NAS, Pi-hole, Home Assistant, Portainer, Uptime Kuma, Nginx Proxy Manager, the router), Media server (Jellyfin, Jellyseerr, Sonarr, Radarr, Lidarr, Bazarr, Prowlarr, qBittorrent) and Developer (Gitea, Woodpecker CI, a container registry) — or Keep these links. One server address fills in every service with its usual port; More lists them to change one, and a scheme or port typed in the address wins. While main is still the untouched seed the template replaces it, otherwise it comes as a new page; the line under the button says which. The answer is kept in quickStart.templatePicked, and Show quick-start card again clears it.

  • New
    after a template, the first steps use your own services

    The quick-start checklist's first task becomes opening one of them by its shortcut (Open Jellyfin from the dashboard — type j), and the dashboard tour's search and shortcut steps name it as their example.

  • New
    the template import dialog offers the three as well

    Or start from: under Import a page… loads Homelab, Media server or Developer, and for a template whose addresses follow {server}, Where do these run? fills them all from one address; a field you change by hand stops following it.

Inbox

  • Fix
    the inbox keeps every link

    It held 500 by default (inboxMaxItems, a setting only the settings file had), and past that a new link from the extension, a share, the bookmarklet or an undo pushed the oldest one out without a word. An import stopped at the cap and said inbox full. The cap is gone: every way in adds the link and drops nothing, and an import adds every row that is not a duplicate. inboxMaxItems is removed from Settings, its defaults and the missing-key handling.

Tests

  • Tests
    update_check_test.go

    covers the rate-limit wait, the conditional request and the token with its fallback; tests/config-overview-release.spec.js reads the version from the Version panel and covers the behind line and the failure reason.

  • Tests
    tests/config-widgets-tab.spec.js

    moves a widget through its Settings page select and checks it left the source page and landed, same id, on the other.

  • Tests
    tests/config-widgets-tabs.spec.js

    checks the Custom section's count against the offered presets, one per service name, and that it says five groups.

  • Tests
    tests/header-sheet-reduced-motion.spec.js

    opens the pages and recents panels with their keys under reduced motion and with Animations off, and checks that each sits inside the window, on the strip's centre line, without an animation.

  • Tests
    tests/unsorted-page-label.spec.js

    keeps a link from the inbox, opens #unsorted, groups by page and checks that the group header and the side panel's location say Unsorted.

  • Tests
    tests/config-rail-sticky.spec.js

    opens Config → Behavior from the dashboard, scrolls it at 1440 and 800px wide, and checks that the rail starts below the band.

  • Tests
    tests/header-one-clock.spec.js

    counts the visible clocks at 820×1180 with a coarse pointer and at 1440×900 (one each) and at 390×844 (at most one).

  • Tests
    settings_merge_test.go

    saves smartFreshPageIds through the store and reads it back, and loads an old settings file as an empty list; tests/config-collection-scope.spec.js ticks a Fresh page in Collection scope, reloads, and finds it still ticked.

  • Tests
    tests/dashboard-widget-notes.spec.js

    ticks a box and unticks it with two plain clicks, and checks both saves.

  • Tests
    tests/bulk-actions-parity.spec.js

    answers one re-check with a 429 and one with a 502, and checks the first is asked again and the summary says one.

  • Tests
    feeds_retry_test.go

    retries one of two feeds and checks only that one is fetched and LastPoll stays.

  • Tests
    page_template_test.go

    cuts a long label in another script and expects whole characters.

  • Tests
    page_template_test.go

    runs four imports at once and expects four pages.

  • Tests
    tests/page-overview-panel.spec.js

    (no filter with a few pages, a filter with many) failed on every run, in CI and alone: it reopens the panel and expects the cursor on the current page. It passes again with the modal.js fix and fails without it.

  • Tests
    tests/inbox-mark-read-failure.spec.js

    failed now and then in CI with a ten-second wait for its probe row. Its POST went to the server while the dashboard's own inbox read was still on the wire; opening the view joined that read (fetchItems keeps one in flight) and never asked again. A first try waited for a read in flight before the POST, and CI failed it again: the dashboard reads the inbox on its own while the page settles, so a read could leave between that wait and the POST. The spec now reads the list itself after the POST, before the view opens.

  • Tests
    tests/header-button-style.spec.js

    (on a glass theme, plain controls stand on the band) failed three times in one CI run and never locally. Its chooseStyle POSTed the settings by hand and slept 300ms; the dashboard, still settling from the reload before it, had its own save and a revision check on the wire, and the header kept the old style. It now saves through the dashboard's own saveSettings, waits for the header to carry the new style, and polls for the glass.

  • Tests
    tests/config-help-health.spec.js

    expected the inbox's 500 cap in Help; it now checks that Help says the inbox has no limit and no longer mentions dropping links.

  • Tests
    tests/config-bookmarks-unsorted-view.spec.js

    (Delete on a selection in the Unsorted view) timed out once in CI on a checkbox that stayed hidden: the tick shows on hover, and a repaint after the search drew the row anew away from the pointer. It hovers again until the tick takes.

  • Tests
    tests/settings-refresh-race.spec.js

    holds the settings read of a refresh, changes and saves the header style meanwhile, then lets the old answer land, and expects the new style in the settings and on the header. It fails without the loadData change. A second test lets this tab's save land, holds its answer, has another device save after it, and expects the screen to match the server; it fails with the first try.

  • Tests
    tests/first-start-templates.spec.js

    answers the card with each choice and checks what lands on the page; bundled_templates_test.go covers the three files, the address expansion and replace-or-add; notes_marker_test.go saves settings and finds the notes marker still set. tests/fixtures.js answers the card as Keep these links for every other spec, so the grid starts where it did.

  • Tests
    inbox_limits_test.go

    adds a link to a full inbox and an undo, and checks that nothing older is dropped (TestAddInboxItemNeverDropsAnOlderLink, TestUndoPushesNothingOutAndDropsADeadIcon); inbox_capacity_test.go follows; tests/inbox-view-fixes.spec.js imports into an inbox that already holds links and checks every row is added and the old links stay.

  • Tests
    tests/config-tab-note-follows-tab.spec.js

    switches tabs in Data & backups, Bookmarks and Help and checks the note under the strip each time.

  • Tests
    tests/dashboard-spread-name-width.spec.js

    compares a name's width in a spread category with the same category in one column; tests/dashboard-category-width.spec.js follows the new track layout.

Docs

  • Docs
    MCP copy in all six languages

    mcpTitle, mcpSummary, mcpNote, mcpEnabledLabel, mcpAddressLabel, overviewNewFeatureWebhooksHow and overviewNewFeatureWebhooksEnable name a script or another tool.

  • Docs
    locale keys

    overviewVersionLine, overviewVersionHere and overviewVersionTitle in all six languages. The behind line reuses the translated updateCheckModalAvailable. The six update-check reasons (updateCheckRateLimited, updateCheckRateLimitedAt, updateCheckTokenHint, updateCheckLocalLimit, updateCheckUnreachable, updateCheckFailedWith) are in all six languages too. go run scripts/gen-asset-hashes.go refreshed asset_hashes_gen.go.

  • Docs
    locale keys

    widgetPageNote, widgetMoved, widgetMoveDiscardBody and widgetMoveDiscardOk in all six languages; the label reuses the translated widgetsPageLabel.

  • Docs
    preset counts in all six languages

    widgetCustomRefPresetsBody says five groups, and widgetsTutorialStep5Title, widgetsTutorialStep5Body1 and widgetsTutorialPresetsMore give the new numbers and name monitoring.

  • Docs
    Config → Help in all six languages

    helpConfigBody names the Version panel on the overview and that the Containers GitHub token serves the update check too; helpContainersConfigBody says the same under the token; helpWidgetAddingBody names the Page select in a widget's settings; helpVersionBody points to the Version panel and its dot.

  • Docs
    README and MANUAL catch up

    The README's links into the manual carried the section numbers from before the manual was renumbered (§13.4 for Collection health, §11.5 for the Custom widget, and eleven more); they now name the sections they open. The alert list on top names Apprise, and the Unraid widgets list names the overview. MANUAL §15.2 names the Page select in a widget's settings.

  • Docs
    the inbox's limit

    is gone from Config → Help → Inbox (helpInboxSettingsBody, all six languages): the line listing inboxMaxItems among the settings-file-only options, and the paragraph on undo at the cap, where the oldest link made way. MANUAL §13.1 says the inbox has no limit.

  • Docs
    the first-start card in Help and the manual

    Config → Help → Getting started (helpStartBody) has a paragraph on What do you run?, and Structure & bookmarks (helpWorkspaceBody) names the three bundled templates in the import dialog, in all six languages. MANUAL §2 First launch opens with the card and says how the quick-start and the tour change after a template; §9.8 names the three in the import dialog. The card's text, Or start from: and Where do these run? in the import dialog, the two tour lines and the checklist's service task had no locale keys and showed in English in every language; the new firstStart group, config.pageTemplateServer, config.pageTemplateStartFrom, dashboard.dashTourS2Try, dashboard.dashTourS3Try, quickstart.itemOpenService and quickstart.itemOpenServiceHint are in all six languages.

  • Docs
    static/data/whats-new/v1.17.5.json and its index entry

    hideFromModal is gone from v1.17.4, v1.17.3, v1.17.1, v1.15.4 and v1.15.1, so the modal lists every release. whats-new-stub.js: DASHBOARD_RELEASE moved to 2026.10-dashboard-release-v1.17.5, so the window opens once more, and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v321; tests/whats-new-hidden-release.spec.js follows both and expects no held-back release.

  • Docs
    a spotlight for the Version panel

    in overview-features.json with since: "v1.17.5", so it shows in the overview's news and under About → News & features; its five overviewNewFeatureVersionPanel* keys are in all six languages.

  • New
    the manual is easier to find your way in

    Contents with start-here routes and every subsection, a glossary of 100 key terms linked into the text, "in short" notes per chapter, three diagrams and 94 screenshots beside the text they show, element crops and full pages, many folded away, the Custom widget section in full with all 42 presets, and the manual caught up with features up to v1.17.5.

Only docs and tests changed in this release.

v1.17.4 The install count is announced once in the corner, and says when an install runs on Unraid. +2

The install count is announced once in the corner, and says when an install runs on Unraid. Held back from the What's new window (hideFromModal) like v1.17.3 and v1.17.1, so v1.17.2 keeps leading it.

Privacy

  • New
    a corner card announces the install count

    The count is on by default, so the card says once what leaves the server (a random id and the version) and offers Turn it off next to Fine by me; closing it counts as an answer and it does not come back. It is not shown when the count is already off or when DISABLE_TELEMETRY locks it off.

  • New
    the ping says when it runs on Unraid

    Unraid sets HOST_OS=Unraid on every container it starts; when that is present the ping adds the word unraid as the page title, so the project can tell how many installs run there. Other installs send nothing extra. The setting's hint and explanation, the card, Config → Help and the manual say so, in all six languages.

Docs

  • Docs
    static/data/whats-new/v1.17.4.json and its index entry

    , flagged hideFromModal; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v320, and tests/whats-new-hidden-release.spec.js lists v1.17.4 among the held-back releases. The Unraid CA template lists v1.17.4 under <Changes>. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.17.3 The daily install count from v1.17.2 now actually counts. 1 fix

The daily install count from v1.17.2 now actually counts. Held back from the What's new window (hideFromModal) like v1.17.1, so v1.17.2 keeps leading it.

Privacy

  • Fix
    the install count was never counted

    Umami read the request as a bot and dropped it while still answering 200, and it counts visitors from pageviews only, which the ping was not. The ping now identifies itself the way Umami accepts and goes in as a pageview with the version as its path, so installs show up as visitors and per version under Pages. What is sent is unchanged: a random install id and the release tag, once a day. Installs on v1.17.2 start counting once they update.

Docs

  • Docs
    static/data/whats-new/v1.17.3.json and its index entry

    , flagged hideFromModal; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v319, and tests/whats-new-hidden-release.spec.js lists v1.17.3 among the held-back releases. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.17.2 A Notes widget with Markdown and checkboxes, pages that can be shared as template files, quiet hours and reminders for alerts, a Trend tab and more figures in Collection health, a daily anonymous install count (with its own switch), and a corner card and a banner that point at the feature overview. +14 4 fix

A Notes widget with Markdown and checkboxes, pages that can be shared as template files, quiet hours and reminders for alerts, a Trend tab and more figures in Collection health, a daily anonymous install count (with its own switch), and a corner card and a banner that point at the feature overview. Plus uptime badges, a Retry for a stopped feed, and inbox links in search.

Widgets

  • New
    a Notes widget

    . One text of up to 6,000 characters, kept in the widget and read as a small Markdown: headings, bullet and numbered lists, quotes, tables, code, bold, italic and links. A line that starts with [ ] is a checkbox that is ticked on the tile; ticking rewrites that one line and finds it again by its text if the note changed in another tab. Edit opens a plain editor with / commands (date, time, uuid, upper, lower, title, todo, h1, code, table); Open large adds a toolbar and a live preview. Drawn two columns wide the tile shows the length and the tasks done. New installs, and existing ones, get an example note with a checklist on the first page.

  • New
    where notes are processed is a setting

    Config → Behavior → General → Notes widget: On the server (the default, /api/widgets/notes/render and /command) or In the browser, which needs no request while you type. Both engines answer from the same fixtures. When the server cannot be reached the tile shows the plain text and says so.

  • New
    Retry on a stopped feed

    A feed that failed five times is retired until you do something; the Feeds widget now shows it with Retry, which tries it again now (POST /api/feeds/retry) instead of waiting for tomorrow.

Pages

  • New
    a page as a template file

    Share this page… in the page switcher, Save as template… in Structure → Pages, or the palette, writes the layout, categories, widgets and links to a file; Import a page… or Start from a template… on an empty page reads one. Addresses on your own network become names the importer fills in once per service; usage, health, sign-ins and every field not on the allowlist stay out, notes only when ticked, and importing always makes a new page.

Health and alerts

  • New
    Collection health has three tabs

    Overview gains a row of key figures and four cards (Fix first, When last checked, How often opened, Why they fail); Monitors gets a row of fleet figures; the Trend tab holds the 90-day chart with its figures beside it, every monitor per day with its own figures, and uptime by weekday.

  • New
    quiet hours and reminders

    . During a window, notices from monitors, containers, Unraid and backups are held and one summary says what still plays and what recovered when it ends; an expired certificate, a mass outage and a failed backup always pass (a container crash can be added). A monitor or container that stays down gets a reminder after 15 minutes to 4 hours, at most 1 to 5 times, never inside quiet hours. Outgoing webhooks are outside both, and a test counts the callers of the two sinks so a fifth cannot skip the gate.

  • New
    uptime badges

    GET /badge/uptime.svg?url=…&days=7|30 returns a small SVG for monitored addresses; anything else reads no data. Off by default (Behavior → Status & alerts → Checks on the server), because anyone who knows a monitored address can read it.

  • Fix
    background re-checks are on by default

    The setting started off, so a fresh install's Health view only moved when a dashboard was open. It is on for new installs and for existing ones that never set it.

Privacy

  • New
    a daily install count

    Once a day the server sends a random install id (the file install-id in the data folder) and the release tag to stats.nextdash.cc, so the project can say how many installs exist; nothing else. It has its own switch under Behavior → Privacy & sync → Count this install, on by default, and DISABLE_TELEMETRY=true stops it for the whole server.

  • Fix
    the analytics texts no longer say "no request leaves your machine"

    With analytics off the install count is still sent; usageAnalyticsHint and the notice say so, in all six languages.

Dashboard

  • New
    a corner card and a banner for the feature overview

    After eight bookmarks and a short wait, one card points at nextdash.cc/features (it opens in a new tab and is asked once); Config → Overview has a slim banner with the same link.

  • New
    Config lists the corner cards

    Behavior → Privacy & sync → Onboarding shows each card as Answered or Not shown yet, with Show again.

  • New
    search finds links waiting in the inbox

    A name search shows matching inbox items in their own group at the end; snoozed ones stay out.

  • New
    the Inbox icon says how many links are kept

    in its tooltip and label.

  • New
    the Bookmarks view shows which bookmarks run in a container

    A cube follows the title of a bookmark that is a container's web UI, in the container's state — green running, amber paused or restarting, grey stopped — and links to that container's side panel. The match is DockerSearchIndex.containersFor, the one the Containers view and the Details tab's "Runs in" already use; the cubes are filled once the container list is in, and stay away when Containers is switched off or has no socket.

  • Fix
    the Inbox and Containers rails are as wide as the Bookmarks rail

    .

  • Fix
    the selection bars share one list of actions

    The dashboard's bar and the Bookmarks view's drew different buttons for the same bookmarks; both now come from bulk-actions.js, the dashboard's bar gains Fetch icons and Fetch previews, and bulk-sweep.js is the one loop that walks a selection with the progress bar and rate-limit handling.

  • New
    cheat sheet keys for writing in a Notes widget

    (save and cancel).

Docs

  • Docs
    static/data/whats-new/v1.17.2.json and its index entry

    , with the dashboard's selection bar under Dashboard; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v318 and DASHBOARD_RELEASE to v1.17.2, so the window opens once. go generate refreshed asset_hashes_gen.go.

  • Docs
    Config → Help

    helpLibraryBody describes the container cube in the Bookmarks view, helpCollectionHealthBody and helpHealthStatsBody the three tabs, helpWidgetKindsBody the Notes widget and Retry, helpHealthMaintenanceBody quiet hours, reminders and uptime badges, helpWorkspaceBody page templates, helpStatsPrivacyBody the install count, and helpBehaviorBody the corner cards, in all six languages; the Notes widget and the other new settings have their strings in en.json and the five translations.

  • Docs
    Manual and README

    Notes (§15), page templates (§9.8), quiet hours, reminders and uptime badges (§12.5), corner cards and the install count, Collection health's three tabs (§11.8).

  • Docs
    the Unraid theme screenshots left the repository

    screenshots/unraid-themes/ (64 images) is removed and listed in .gitignore; the README keeps its two Unraid screenshots in screenshots/.

Only docs and tests changed in this release.

v1.17.1 Four themes for Unraid users, each in dark and light. +4 83 fix

Four themes for Unraid users, each in dark and light. A widget can be moved to another page from its menu, and a long list of fixes across the Calendar, Health, Containers, Backups, Search, Inbox and the dashboard — held back from the What's new window (hideFromModal) like v1.15.4 and v1.15.1, so v1.17.0 keeps leading it.

Themes

  • New
    Unraid Black and Unraid Azure

    , each light and dark. Black has flat black panels, small uppercase labels and the orange of the Unraid logo; Azure has cool grey panels and a steel-blue accent. Both are marked new, carry a description, a chosen backdrop and a weather scene per variant.

  • New
    Unraid Ember and Unraid Blaze

    , each light and dark. Ember is the logo's orange glowing out of black glass (neon, sunset backdrop); Blaze is its red end, hard-edged lacquer on deep crimson (horizon backdrop). Both are marked new, described and given a weather scene like the other two. Also shortened the Unraid Black card description, which was over the length limit.

  • Fix
    a failed read of the colours no longer wipes your own themes

    When /api/colors could not be read (a server restart, a proxy's 502), loadColorsData kept an empty stand-in for the session, and the next Add custom theme or import posted it: every own theme deleted, both palettes emptied. The stand-in is now marked, read again on the next call, and saveColorsData refuses to post it.

  • Fix
    the order of your own themes is kept

    ↑/↓ in Custom themes lasted until a reload: the server keeps them in a map, which it writes sorted. The order now travels as customOrder.

  • Fix
    a theme made in another tab or on another device draws on this one

    The settings sync noticed the change but never fetched the theme CSS again (no colours at all on a theme picked there) and kept a stale colour document whose next save deleted the theme made elsewhere.

  • Fix
    deleting the light/dark half that Follow system shows draws the other half

    What is on screen is read before the delete; asked afterwards it could never name the half just removed, and the page kept the deleted theme with no colours.

  • Fix
    Automatic on a packaged theme goes back to how it ships

    The server refills an empty field from the shipped theme, so Automatic or ↺ saved and nothing changed.

  • Fix
    :theme draws the half Follow system wants

    with the theme's own Auto background, as the Appearance picker does.

  • Fix
    with Random theme on, the look studio shows the theme you pick

    the page kept the random one.

  • Fix
    a duplicate of a packaged theme is your own

    not filed under that theme's collection.

Widgets

  • New
    Move to page… in the widget menu

    Right-click a widget's header and pick another page, the same move as Config → Widgets. The widget keeps its id, so its sign-in and folded state follow it.

  • Fix
    Move to page… keeps a widget's feeds and address

    The dashboard reads its widgets without the write token, so an RSS widget's feeds and a custom widget's URL and credential are left out of its copy; the move built the widget from that copy and removed the full one. It now reads both pages with the token.

  • Fix
    the Health widget shows the figures you tick

    "Down now" and "Healthy" never matched, so ticking them showed nothing.

  • Fix
    the Unchecked widget counts monitored bookmarks as watched

    .

  • Fix
    six on-by-default options draw ticked

    Disks' bar, Uptime's sparkline, Inbox's source, Feeds' retired, Neglected's never-opened and Backups' list drew unticked while the tile showed them.

  • Fix
    Save in a widget's settings keeps it hidden

    when Shown was unticked on its row meanwhile.

  • Fix
    the Calendar keeps the events coming up soonest

    The 500-event cap was applied in file order, and a feed over 1 MB was cut without a word; it is now cut after sorting, and read up to 4 MB.

  • Fix
    the Calendar ends an all-day event at your midnight

    before it counts the rows. East of UTC, yesterday's all-day event took a row every morning and the tile showed one event short, or nothing.

  • Fix
    the Calendar leaves out cancelled events

    .

  • Fix
    the Calendar reads Outlook's zone names with a colon in them

    such as "(UTC+01:00) Amsterdam, …"; those events were dropped.

  • Fix
    opening a feed's bookmark clears its new count when it is bookmarked twice

    .

  • Fix
    a tile that got no answer says so

    While nextDash restarted, Disks and Docker asked you to set them up again, and Feeds, Sources and Inbox stayed on "Loading…".

  • Fix
    Disks shows how full a disk is the way df does

    without root's reserve; a disk full for every writer read 95%.

  • Fix
    the Weather tile calls today "Today"

    after midnight, and leaves out a day that is over.

Health

  • Fix
    turning monitoring off keeps the uptime history

    The next monitor tick swept the samples and day summaries of every URL that was not monitored, within a minute, while the dialog said the history is kept. The sweep now keeps every bookmark that still exists; retention ages out the rest.

  • Fix
    single-page apps are no longer marked down by soft-404 detection

    An app that serves its one shell document for every path (Sonarr without auth, Uptime Kuma, any try_files setup) answered the not-found probe with that same document, and every page compared equal to it. The probe now also reads the front page and drops the verdict when it is that document; a site's root is never judged not found.

  • Fix
    no "back online" for an outage that was never told

    A failed manual re-check or retest recorded failures without alerting, and the next success sent a lone recovery.

  • Fix
    a dashboard ping is not saved as an outage when it never answered

    The browser gave up after a fixed 3 s whatever Check timeout said, and stored "Unreachable"; it now waits for the check's own budget and stores nothing when no answer came.

  • Fix
    alerts from a long monitor round arrive

    They were sent on the round's expired context, lost, and still marked as sent.

  • Fix
    maintenance windows run in your time zone

    They were read on the container's clock, UTC unless TZ is set; the browser's zone is now saved with them as maintenanceTimeZone.

  • Fix
    a page title with 404 inside a longer number is not a missing page

    "Issue #14042" or "DS1404" read as "Page says it does not exist".

  • Fix
    switching off a window's last day no longer turns it on for every day

    An empty day list means every day, so the row now waits for the next day you pick.

  • Fix
    Turn off all checks clears drift findings too

    as switching one bookmark off does; monitoring again later showed months-old findings at once.

  • Fix
    a long retest no longer says "back online" during an outage that started after its check

    .

  • Fix
    webhook deliveries are logged by host

    so a Home Assistant or n8n secret in the path stays out of the log.

  • Fix
    a credential's query key stays out of the drift baseline

    on the bookmark.

  • Fix
    a soft-404 probe that got no answer is retried after 10 minutes

    not trusted as "behaves normally" for a day, and has its own deadline instead of what a slow page left over.

  • Fix
    Send test alert shows its outcome

    when the field you just typed saves and redraws the panel; "Sent" or the error landed on the line that was replaced.

  • Fix
    a tour you closed stays closed

    when a settings read that left before the close lands after it; the inbox tour could open again over the list.

Containers

  • Fix
    a crash loop is one notice, not two a minute

    Docker's restart backoff grows to a minute, and past the tenth fast crash each wait outlasted the 30 s grace, so every cycle was told as "stopped unexpectedly" and "running again". The grace is now 75 s.

  • Fix
    the nightly update reads each container at its turn

    The run's list can be an hour old by then: a container stopped meanwhile (by hand, or a backup job) was updated, watched as if running, "rolled back" and started again. The update now goes by what the recreate itself found, and a container replaced since the list is left for the next tick instead of failing with a 404 notice.

  • Fix
    an update keeps an anonymous volume listed without a source

    Compose's volumes: [/data] and --mount type=volume,dst=… put the volume in HostConfig.Mounts with no source; sent back that way, Docker gave the new container a fresh, empty volume. The source is filled in from the container's own mounts.

  • Fix
    a stop from outside nextDash during the watch after an automatic update is left alone

    Unraid's Docker tab, the CLI or a backup job stopping it read as a failed update: rolled back, started again and the version skipped.

  • Fix
    a disk measurement that failed waits 30 minutes

    Every poll of the Containers tile started another, so a slow daemon walked its disk back to back.

  • Fix
    s stops a container that keeps restarting

    as its menu says; it tried to start it and nothing happened.

  • Fix
    stopping an image with its own stop signal is no longer told as a crash

    A STOPSIGNAL SIGINT container exiting 130 sent "stopped unexpectedly" and added a crash to its timeline.

  • Fix
    an update keeps per-network links and driver options

    so a compose links: alias still resolves in the new container.

Dashboard

  • Fix
    moving a bookmark to another page from the edit form keeps everything

    The move sent only the fields the form edits, then deleted the source row: opens, created date, preview, check URL, credential, mute and health settings were lost. It now sends the whole row with the edits on top.

  • Fix
    health settings from the Bookmarks view are no longer undone by the next dashboard save

    Expectations, check URL, credential, mute, ignores and accepted drift did not reach the dashboard's copy of the page, and its next drag, pin or delete wrote the old values back. The writes now reload that copy, and these settings move the data revision so other tabs and devices reload too.

  • Fix
    Today no longer prints over the category below it after you open a bookmark

    Opening one repaints the smart sections as new elements, and in packed columns nothing watched them any more, so a height change (an icon arriving) left their row span behind until another category happened to resize. The grid now watches the new elements.

  • Fix
    a page save from an older tab keeps the drift finding and the archive dates

    the checks wrote meanwhile.

  • Fix
    restoring a page from the trash lets go of shortcuts taken since

    as a single bookmark's restore does; both pages refused every save before.

  • Fix
    moving bookmarks to another page without a category brings their categories along

    instead of leaving them under "Unknown category".

  • Fix
    a new address starts over

    Editing a bookmark's URL kept the old address's last check, error and drift baseline, and a drift-watched bookmark then reported "Now redirects to <new host>" until Accept drift. Both the edit form and the Bookmarks view's patch clear them.

  • New
    the bookmark menus are grouped

    The grid's right-click menu now reads open and share, edit and file, checking and health, select, delete, with a line between each; the inbox's and the Bookmarks view's menus and both selection menus follow the same order.

Backups

  • Fix
    a backup with a large local page copy can be restored

    A capture may be up to 52 MB, but a restore refused any file over 32 MB, so every backup taken after one big capture was unusable. The limit per file is now 64 MB, and a refused restore or import says why.

  • Fix
    a large backup can cross the wire

    Backup, download, restore and import get 15 minutes instead of the 30 s / 60 s an API call gets, and /api/import takes up to 1 GB.

  • Fix
    an upload over its limit is refused, not cut

    A 16 MB CJK font was saved as a 10 MB stump and reported applied; fonts may now be 32 MB, and the panel says why one is refused.

  • Fix
    device-only settings leave what the server does alone

    analytics, local bookmarks, backup secrets, the background re-check, feeds, inbox limits and more.

  • Fix
    a backup unzipped and zipped again on a Mac can be restored

    The __MACOSX folder that Compress adds counted as a second folder, and the restore found no pages.

  • Fix
    the list of backups no longer reads every archive whole

    to count its bookmarks; only the index of each ZIP is read.

  • Fix
    Statistics loads its current figures after an update

    One of its scripts was fetched without a version and kept for a day.

  • Fix
    the log viewer starts over after a clear in another tab or a restart

    instead of keeping cleared lines or showing replayed ones twice.

Search

  • Fix
    accented letters can be typed, and either spelling finds a name

    Every key gate was printable ASCII, so "Météo", "Zürich" or anything in Chinese could not be typed, and the matcher did not fold accents.

  • Fix
    the inbox's keys stay out of an open dialog

    Escape cleared the ticks while the bulk-delete dialog stayed open; Enter, Space and d acted on the rows behind a confirm.

  • Fix
    a bookmark's own letter on the grid waits for a longer shortcut

    and for "Enter opens": with "nc" beside "n", typing "nc" after a search opened the bookmark behind "n".

  • Fix
    category: and :open category go by the category's name

    A bookmark holds its category's id, so "category:vps" found nothing and the completions read out raw ids.

  • Fix
    what you type before the search code has loaded arrives whole

    Only the opening key waited, so ":dark" arrived as ":" and a shortcut typed the moment a tab opened did nothing.

  • Fix
    opening a bookmark from a command's list teaches the ranking nothing

    After :tag work, typing "work" ranked that bookmark first for good.

  • Fix
    Ctrl/Cmd+Enter on a name-search result opens a new tab

    as on every other row.

  • Fix
    :save keeps the / of a name search

    recalling it ran a shortcut search instead.

  • Fix
    Show on dashboard, :edit and :move go to the bookmark's own row

    not its copy in Pinned or another smart collection.

  • Fix
    container names that arrive late keep the row you moved to

    Enter opened the first result.

  • Fix
    a tag with a space works as a filter

    Its completion is now tag:"home lab", which reads as one tag instead of a tag and a search word.

  • Fix
    :find stays on when the grid is drawn again

    and ends on another page.

Inbox

  • Fix
    the tag scan keeps a preview it could not read again

    and pauses when the outbound limit runs out instead of marking every page after it as read.

  • Fix
    new inbox links get their picture

    and triage shows a local copy instead of a broken https://data/….

  • Fix
    one odd address in a browser export no longer refuses the whole import

    the row is left out and counted.

  • Fix
    undoing a bulk Promote brings back the Unsorted copy it replaced

    with its note and tags; the copy was deleted outright and Undo left it out.

  • Fix
    a long address is kept whole or refused

    The inbox cut URLs at 2,048 characters, which stored a broken link and defeated the duplicate check; it now keeps up to 8,192 and refuses anything longer.

  • Fix
    links restored in bulk get their icons

    A refusal by the outbound limit was stamped as "this site has no icon", so the startup backfill never asked again.

  • Fix
    a browser folder with a description keeps its name on import

    Its bookmarks were filed one level up.

  • Fix
    sorting by Title follows the title the row shows

    .

  • Fix
    the extension stores a page's icon only when it saves the page

    The popup stored one on every open and every edit of the address, and quick save before its duplicate check, so data/icons filled with files nothing refers to.

  • Fix
    the bookmark form stores a page's icon when you save, not while you type

    Every address typed or changed stored a favicon in data/icons, kept or not; the card now shows the favicon from where it is.

  • Fix
    inbox titles are decoded once

    Every read decoded entities again, so "What is &nbsp;?" lost its text and a URL used as a title turned "&param=" into "¶m=".

  • Fix
    Forget token forgets the token only

    It deleted the whole source, so a new token brought back every item you had removed.

Docs

  • Docs
    README

    the two Unraid themes in the Unraid section, with a screenshot of each (screenshots/nextdash-unraid-black.jpg, nextdash-unraid-azure.jpg).

  • Docs
    static/data/whats-new/v1.17.1.json and its index entry

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v316. go generate refreshed asset_hashes_gen.go.

  • Docs
    Manual and README

    Unraid Ember and Blaze next to Black and Azure (§16.1), Move to page… in the widget's right-click menu (§15.3), and the count of new themes (38).

Only docs and tests changed in this release.

v1.17.0 Containers and bookmarks to self-hosted apps get real app icons from two open icon sets, dashboard-icons and selfh.st/icons. +60 93 fix Read the post

Containers and bookmarks to self-hosted apps get real app icons from two open icon sets, dashboard-icons and selfh.st/icons. A container is matched by its image and name, a bookmark by its host, and the icon follows the theme between its light and dark variant. An icon picker with suggestions sits behind the pencil in the bookmark form and in the container drawer. Nothing is bundled: the server fetches the indexes and the icons, and the browser never talks to the CDN. The Custom widget knows sixteen more services, signs in for a token where a service hands one out, can count entries in an answer, and every preset is now tested against its service's recorded answer. Alerts can go through Apprise, and so to mail, Matrix, Signal and a hundred more. The container drawer's charts move to uPlot, the first of the charts to do so. Seven Unraid widgets read an Unraid server's array, parity, shares, VMs, UPS and notifications, and its alerts reach the same channels as everything else. The search panel can search the web through your own SearXNG or the Brave Search API, the look studio gains a theme editor that saves what is on screen as a theme of your own, the remaining charts in Health and Statistics move to uPlot, Config → Overview becomes panels, and a bookmark can be shown as a QR code to open it on a phone. A third bug hunt fixed 81 bugs across all of it, each with a test that fails without its fix.

App icons

  • New
    two icon sets, read by the server

    icon_sets.go fetches dashboard-icons' metadata.json and selfh.st's index.json from jsDelivr once a week with a conditional GET, keeps the mirrors in data/icon-sets/ and keeps the old copy when a fetch fails or reads as nothing. icon_sets_index.go merges them into one lookup: names first, then display names, then aliases, dashboard-icons before selfh.st in each round, and a variant always from the entry's own set. DISABLE_ICON_SETS=1 switches it all off; NEXTDASH_ICON_SETS_FIXTURE reads a directory instead, for the tests.

  • New
    icons served from a cache of their own

    /data/icon-sets/<set>/<file> fetches a file the index names on first use, through the icon guards (2 MiB, magic bytes, SVG sanitised), and serves it from disk after that, asking again after a week. A name the index does not know never leaves the server; a failed fetch is remembered for an hour; the cache holds at most 3000 files per set, since the route is open without the token; an SVG that wraps a PNG is refused, since sanitising leaves it empty. data/icon-sets/ stays out of backups, like cached previews.

  • New
    matching by name

    : the image's repository name, the container name, both with packaging words taken off (binhex-, -docker, vpn, -agent, …), without trailing digits, then shorter prefixes (jellyfin-newsletter → jellyfin). A container whose tag moved on reports an image ID and matches on its name. Bookmarks match on the leftmost label of a host with three or more labels, on a one-label host, or on two labels with a private suffix (sonarr.lan, plex.local); a match reads names only, aliases are for search and suggestions; github.com and IP addresses keep their favicon, unless the bookmark is linked to a container. icon_match_test.go runs 62 containers from a real Unraid server.

  • New
    the icon follows the theme

    icon-set-auto.js picks the variant for a dark background on a dark theme and the one for a light background on a light theme, from --ink-dir, and swaps it on theme-changed without a reload.

  • New
    an icon picker

    : a search over both sets in a grid, with the variants of the chosen icon underneath. ↓ goes into the grid, the arrows move, Alt+←/→ picks the variant, Enter chooses, Escape closes and gives focus back. Choosing adopts the icon: POST /api/icon-sets/adopt copies it into data/icons/ (sonarr.svg, sonarr-2.svg when the name is taken by other bytes), behind the write token, and from then on it is an ordinary icon of yours. GET /api/icon-sets/search, /suggest and POST /api/icon-sets/match answer the page.

  • New
    credits in About → Colophon

    for dashboard-icons (Apache-2.0) and selfh.st/icons (CC BY 4.0), with links to both and to the licence.

  • Fix
    a loose alias word no longer picks the icon

    An alias such as "maps" or "music" matched any host or container with that word, so maps.google.com got Apple Maps, music.youtube.com Anghami and a container called app Miro, and "Refresh all favicons" then cleared the favicon those bookmarks had. Matching now reads names only (iconSetIndex.aliasKeys); search and the form's suggestions still offer aliases.

  • Fix
    the bookmark form uses the page's own icon

    It read the preview's icon, which is empty on a fresh fetch and a local cached path after it, so every fetch fell back to /favicon.ico; it reads iconSource now.

  • Fix
    a reload no longer leaves set icons as letters for an hour

    A cancelled page load failed every queued icon fetch and stored each as a miss; fetches now run on their own, a cancelled one is not a miss, and different files fetch side by side instead of in one line.

  • Fix
    Refresh all favicons keeps an icon picked in the app-icon picker

    It cleared it on a matched address and overwrote it with the site favicon on any other.

  • Fix
    the picker saves the variant it shows

    In a dark theme the grid drew the light icon and saved the black one; a click also kept the previous item's variant, and an item without it failed with "Could not use this icon".

  • Fix
    no crash before the icon sets are fetched

    The alias fix read the index without checking that there was one.

  • Fix
    an icon the sets cannot deliver lets the favicon through

    The match alone blocked the favicon, so a file the CDN would not give left the row on a letter; a variant that fails falls back to the base drawing first.

  • Fix
    sonarr.lan and plex.local match

    Two-label names on a private suffix count, as three-label ones do.

  • Fix
    the icon cache is capped at 3000 files per set

    The route is open to readers without the token, and a walk over the whole index could fill the disk.

  • Fix
    more than 500 rows, or a failed match request, no longer leave rows on letters

    for the session: asked in batches, and a failed answer is not remembered as "no app".

  • Fix
    two adopts of the same name at once each keep their own drawing
  • Fix
    cached set icons are asked again after a week

    , so a redrawn icon or a sanitiser fix arrives; the old file is served if the CDN does not answer.

Containers

  • New
    an app icon ahead of every container name

    , from the server's icon field on /api/docker/containers; no match shows the letter, and so does an icon that fails to load. nextDash's own container shows the nextDash logo.

  • New
    choose a container's icon in the drawer

    The pencil on the drawer's icon offers Choose app icon…, Use letter and Automatic, stored per container name in Settings.DockerContainerIcons (letter or a file in data/icons/). removeUnusedIconFile keeps a file a container still uses.

  • New
    Config → Containers in four tabs

    Connection, View, Updates and Alerts: the nine panels that stood in one column are grouped by what they are for, with the same strip, keys and memory as Config → Inbox; a setting found by search, a deep link (#config/containers/<tab>) and the buttons that lead here open the right tab. The Notifications note names the tab its CPU-and-memory switch is on, and the host-address check is bound to its field, so a visit to View no longer adds a listener.

Bookmarks

  • New
    a bookmark without an icon shows its app's set icon

    on the dashboard; the rows ask in one batch per render.

  • New
    the set icon wins over a favicon

    When the sets know the address and can deliver its icon, no favicon is fetched: not by the form, the :new modal, the browser extension or the background fill, which no longer counts such a bookmark as missing an icon. /api/bookmark-preview says so in setIcon, worked out per answer and never stored in the preview cache. Fetch again and Refresh all icons drop the favicon a known app had. An icon you chose or uploaded is never replaced.

  • New
    suggestions in the bookmark form

    Up to three app icons appear under the address, one click to choose; the card shows the set icon while the bookmark has none of its own; Choose app icon… heads the pencil menu. The inbox keeps fetching favicons: it does not draw set icons.

  • New
    a bookmark as a QR code, to open it on a phone

    Shift + J on a row, QR code in the right-click menu (an inbox row gives the item's own link, as Share does), and in the Bookmarks view the row menu and Details → Address. The window shows the name, the code and the address, with Copy URL. The code is drawn in the browser by qrcode-generator 1.4.4 (MIT, vendored in static/vendor/qrcode-generator/, lazy-loaded on first use), so the address goes nowhere; it is always black on white with a four-module quiet zone, whatever the theme, and an address too long for a QR code says so.

  • New
    a bookmark's icon has a container's three choices

    A pencil on the icon in the Bookmarks view's side panel opens Choose app icon…, Use letter and Automatic, the one in force ticked — the same pencil and menu as the container drawer's head. Automatic is no icon of its own, as before: the app's set icon, else the favicon. Use letter is a new field, Bookmark.IconMode ("letter", else empty): the dashboard row keeps the letter instead of asking for a set icon, the favicon fill and Refresh all skip it (collectIconCandidates), and the bookmark form shows the letter and fetches no icon unless Fetch again is pressed. An icon of its own always wins: the server drops the mode whenever one is set (normalizeBookmarkIconMode, on every save and patch path). bookmark_icon_mode_test.go, tests/bookmark-icon-mode.spec.js.

  • New
    the side panel's ⋯ menu under headings

    , as the Collection menu has them: Checks (detect redirect, reporting, snooze, merge), Refresh (title, favicon), Copies (archived, local) and Elsewhere (share, show on dashboard), with Delete apart at the foot. A group with nothing in it is left out; Refresh title is there for a bookmark without a finding too (renderBmMoreMenuItems, renderBmHealthActions takes only).

  • Fix
    :remove puts the bookmark in the trash

    The command palette deleted it for good once the toast closed, and its undo posted the page as it was before, so a bookmark added in those seconds vanished. It is now recorded in the trash and undone from there, as a delete on the page is; the remote delete from the inline editor is recorded too.

  • Fix
    :pin, :tag and :note say so when nothing was written

    A bookmark not found on its page was posted back unchanged and reported done; :note showed "Note saved." from another save.

  • Fix
    an inbox item's QR code opens the saved page

    , not this dashboard's inbox link.

  • Fix
    the QR window's label keeps a $& in the address as written
  • Fix
    bulk Fetch icons leaves a chosen letter alone
  • Fix
    Refresh favicon and Fetch icons know an app that shows its set icon

    It said "No favicon found" and every such row counted as failed; the "Without an icon" filter leaves out a chosen letter and an app with its set icon.

  • Fix
    Automatic in a bookmark's icon menu fetches the favicon back

    for an app the sets do not know; it only cleared the icon.

Widgets

  • New
    sixteen more services for the Custom widget

    : Whisparr, LazyLibrarian, NZBHydra2, Komga, PhotoPrism, Jellystat and Mylar3 under Media; Nginx Proxy Manager and Tailscale under Network; Duplicati under System; and a Monitoring group with Beszel, Netdata, Gatus, Uptime Kuma, Scrutiny and Healthchecks. qBittorrent 5.2 gets a preset for its API key beside the sign-in one.

  • New
    services that sign in for a token

    . A sign-in can post JSON and read a token out of the answer: CredentialSession gains format, tokenPath, tokenHeader, tokenPrefix and extra. The token travels in the header the preset names, with or without a prefix, and is kept and renewed like the cookie (once more after a 401 or 403). An answer without a token -- a wrong password that said 200, a two-factor account -- reads "could not sign in" and is not retried in a loop. Nginx Proxy Manager, Pi-hole v6, Duplicati and Beszel use it; a password-only sign-in asks for no username.

  • New
    counting in a figure's path

    (customWidgetLookup). list# is the length of a list (or the keys of an object), list[key=value]# the number of entries that match, and [-1] the last entry. A selector key may be a short path ([results.0.success=false]). Still one value per path; a count is the last step.

  • Fix
    Proxmox's CPU read as about 0%

    data.cpu is a share from 0 to 1 and is now read as one.

  • Fix
    the *arr queue's second figure is "matched"

    , not "downloading": Sonarr, Radarr and Lidarr count queue items matched to the library there.

  • Fix
    Pi-hole v6 signs in itself

    It took a pasted session id that lapsed after half an hour; it now signs in with the password and keeps the id.

  • New
    the presets follow their services

    Overseerr/Jellyseerr is Seerr (same API, same id). Tautulli takes its key in a header instead of the address, Nextcloud reads with its monitoring token (NC-Token, with the OCS header sent for you), Bazarr counts wanted episodes and films and throttled providers (/api/badges), ntfy shows its message count (/v1/stats). Speedtest Tracker shows whether the last test was healthy and when it ran; SABnzbd its time left; Traefik its middlewares; Glances its load; Paperless its tags; Seerr its total. The Immich note says the key must be an admin's.

  • New
    retired presets

    Readarr (stopped upstream), Pi-hole v5 (API removed in v6) and TrueNAS (REST API removed in 26) are no longer offered; a widget already started from one keeps working and still shows its choice.

  • Fix
    a widget's own key survives Save

    After Health had loaded the credential names, Config → Widgets read the widget's key as "none" and the next Save deleted it; re-picking the Plex preset and saving without a key typed replaced the stored key with its Accept header alone.

  • Fix
    a key typed again keeps the preset's fixed header

    After a reload, a new Plex or Nextcloud key went out without Accept or OCS-APIRequest, and the stored entry lost it.

  • Fix
    "NaN" and "Infinity" are not numbers

    A NaN on a meter made the whole answer fail to encode, an empty reply cached for the widget's TTL.

  • Fix
    Ask now with a wrong password fails

    The draft reused the session signed in with the stored password; the password is now part of the session key.

  • Fix
    a sign-in session is renewed after an hour

    Beszel (PocketBase) answers an expired token with an empty list rather than a refusal, and the tile showed "0 systems" for good.

  • Fix
    a million reads as 1000000, not 1e+06

    , in text figures, in [key=value] matches and in lists, which now print objects as JSON.

  • Fix
    counting a list that came as null gives 0

    , not "not in the answer".

  • Fix
    a tile's error is held for 30 seconds, as on the server

    , not for the widget's whole refresh interval.

  • Fix
    a widget's own key is deleted after the page save

    Deleted first, a failed save left the widget pointing at a key that was gone; this holds for Delete, bulk delete and switching the sign-in off.

  • Fix
    places keep a temperature's unit and leave a duration or a date in words

    With decimals set, 21.5 lost its °C and a day showed as 86400.0.

  • Fix
    a relative date reads 2024-05-01 12:00:00 and Unix seconds written as text
  • Fix
    widgets refused at once sign in once between them

    Each threw the shared session away and signed in again, a seat each on Pi-hole.

  • Fix
    a widget's session no longer follows a redirect to another host or port
  • Fix
    typing a new key turns Save on

    The key alone did not count as a change, so a rotated key could not be saved without touching something else.

Alerts

  • New
    Apprise as an alert service

    Downtime alerts, certificate warnings and container notices can go to apprise-api, and from there to everything Apprise reaches: mail, Matrix, Signal, Teams and a hundred more. Pick Apprise under Status → Downtime alerts and give the notify URL of a configuration key (http://apprise:8000/notify/<key>); the passwords and tokens of those services stay in Apprise. An optional tag (Settings.MonitorNotifyAppriseTag) sends only to the destinations that carry it. The body is Apprise's own (title, body, type, format: text), with an outage as failure, a recovery as success and the rest as warning. Send test alert says what Apprise's refusals mean: 424, it could not deliver to a destination or none matched the tag; 404, there is no configuration under that key.

  • Fix
    "back online" after a Re-check

    When a Re-check, Retest all or the hourly re-check saw a recovery first, its up sample made the next monitor round compare up with up, and the recovery was never sent. Those paths now announce it before storing the sample (announceRecoveries).

  • Fix
    ntfy alerts keep ?auth=

    The button form posted to the server root without the query, and a protected topic refused it.

  • Fix
    a backup without tokens and passwords leaves out the alert secrets too

    settings.json went into the ZIP whole, with the alert address (bot token), Pushover's keys, the archive keys and the iCal address; it is written redacted, and restoring such a backup keeps the secrets in use.

  • Fix
    muting any copy of a monitored URL mutes it

    Alerts go per URL, and a mute on the second page's copy did nothing.

  • Fix
    Retest all writes one sample per URL

    A URL monitored on two pages got two per retest, counted twice and with each copy's rules mixed in.

  • Fix
    an unreachable alert service is logged by host

    The log quoted the whole address, Telegram bot token included.

  • Fix
    the health picker leaves out sign-ins a check never sends

    A widget's session login was offered, and the monitor then checked anonymously and reported down.

  • Fix
    the large view's heatmap and Today bars follow the clock across a DST switch

    ; the 23:00 hour landed in the next day's column.

  • Fix
    Collection health lets go of its charts when it closes

    , and Statistics no longer keeps every chart it drew.

  • Fix
    the outage card's count and downtime per monitor cover every outage

    , not only the 25 newest listed (incidentTotals).

Charts

  • New
    the container drawer's charts can be read

    (Containers → a container → Resources). CPU, memory, network and disk I/O over the last hour are drawn with uPlot: one cursor across the four, a tooltip in the chart under the pointer, a time axis, and a drag to zoom (double-click or 0 to go back). The arrow keys walk the points with the value read out under the chart, + and − zoom around it, and a screen reader gets the hour as a table. A theme change draws them again in its colours.

  • New
    the collection's course over time reads the same way

    (Bookmarks → Collection health → Monitors & trend). The 90-day chart, in any of its series, is drawn with uPlot: a date axis and a value axis, both drawn as lines, a tooltip per day, a drag to zoom into a week, the arrow keys with the day read out, and a table for a screen reader. The plain chart stays when uPlot cannot be loaded.

  • New
    one bookmark's health in large, with uPlot

    (a bookmark → Health → Open charts, the row menu, or Shift+H). Response time over the period is a line with the p95 as a dashed line beside it, and uptime per day (per hour for today) is bars in the colour of their share. Both have a time axis and a value axis, a tooltip, a drag to zoom, and the arrow keys with the point read out under the chart: while a chart has focus ← and → walk its points, elsewhere in the modal they still go to the previous and next bookmark. A bar says its share and how many checks it holds; a day without checks says so. The period list redraws them, and the plain charts stay when uPlot cannot be loaded. Date axes name the day without the weekday, so the labels no longer run into each other.

  • New
    outages read per monitor

    (Collection health → Monitors & trend). The card was a list of every outage, each a name and a run of date, duration and reason that broke across lines. It now says first which monitors went down, how often and for how long in all (worst first), then draws the 30 days as a lane per monitor with each outage a bar as long as it lasted, so outages that fall together line up. The list stays, by day with time, monitor, reason and duration in columns, behind "Show list" (renderBmHealthModalOutagesCard).

  • New
    every monitor, per day

    (Collection health → Monitors & trend, under the four cards). The course behind the 24 hours / 7 days / 30 days figures: a bar a day for the uptime of all monitors together, in the colour of its share, and the day's mean response as a line on its own axis on the right. The value axis runs from 90% unless a day fell below it, so a day at 99.4% does not look the same as one at 100%. Hover or the arrow keys read a day out ("22 sep: 87.5% · 300 ms · 400 checks"), and the card's name says the month's average and its worst day. The report carries the days for it (FleetStats.Days: checks, answered and mean response per UTC day, every monitor pooled by check, maintenance left out). The trend chart above it is a little lower, so the tab still fits on one screen.

  • New
    a monitor's response chart with uPlot

    (a bookmark → Health → Monitor & history). Response time per bucket with its average as a dashed line beside it, a time axis and a value axis, a tooltip, a drag to zoom, and the arrow keys with the bucket read out under the chart: its time, response, number of checks and state. That line takes the place of the readout the plain chart had, and the plain chart stays, with its readout, when uPlot cannot be loaded.

  • New
    the score over time with uPlot

    (Collection health → Overview). The collection's healthy share on a 0–100 axis with dates under it, the lowest day marked in red, and every day read out by the pointer or the keys ("lowest" on the low one). Kept compact, and the overview is fitted again once it is drawn, so it still fits on one screen.

  • New
    the healthy share in Statistics with uPlot

    (Statistics → Overview and Health). The same fixed 0–100 axis and the same gaps for days without a report, plus a date axis, a tooltip and the arrow keys; the chart's own table replaces the old one. The sentence above it is unchanged.

  • New
    the bar charts in Statistics with uPlot

    (bookmarks used and opens over time, the collection's growth, the inbox flow per day, and the small one on the Overview). A bar per period with the period's name on the axis, spaced by the widest label so weekly ranges do not run together; the inbox's added and triaged side by side; a running total (the collection's size, the inbox backlog) as a line on an axis of its own on the right. A tooltip with every series at once, a drag to zoom, the arrow keys with the period read out, and the chart's own table for a screen reader. The axis names beside and under each chart stay, and the plain charts stay when uPlot cannot be loaded.

  • New
    NdChart

    : one wrapper around uPlot for charts over time, so every chart gets the same hover, zoom, keys, table and theme handling. uPlot 1.6.32 (MIT) ships in static/vendor/uplot/1.6.32/ with its licence, fetched only where a chart is drawn (lazyLoadedAssets); its stylesheet and nd-chart.css are in the views bundle. No CDN, no CSP change. When it cannot be loaded, the drawer draws the plain charts it always did. About → Colophon credits uPlot. The screen-reader table sits in a hidden wrapper, because a table ignores the 1px height and would otherwise stretch Collection health into a long empty scroll.

  • Fix
    a URL monitored on two pages counts once

    in Collection health and Statistics: monitors, outages, uptime and the per-day chart counted it twice.

  • Fix
    the 30-day collection figures and "Every monitor, per day" read the day summaries

    , not only the checks kept one by one (about a week at a 5-minute interval).

  • Fix
    a bookmark's large view counts its whole 30 days

    "Uptime, last 30 days" covered only the checks kept one by one; the incident count stopped at 5, downtime summed those 5, and the list showed the oldest first.

Unraid

  • New
    an Unraid server to read, set once

    Settings.UnraidServers holds one server (address, self-signed switch, read and alert switches); its API key lives apart in data/unraid-secrets.json at 0600 and travels in a backup only with "Tokens and passwords". Test answers recorded by hand under internal/app/testdata/unraid/.

  • New
    the Unraid API, asked without a library

    unraid_client.go posts one GraphQL query with the key in x-api-key, through the same guarded transport as other outgoing requests, 8 seconds and 1 MB at most, no redirects (one to another address, such as https or myunraid.net, is named so it can be typed instead); a refused field (FORBIDDEN) keeps the rest of the answer, a query the schema refuses is told apart, and the key never appears in an error. NEXTDASH_UNRAID_FIXTURE answers from files, for the tests.

  • New
    queries built from what the server knows

    unraid_schema.go asks the API once a day which fields its types have, and builds each query from those, so a field a newer or older Unraid lacks is left out instead of failing the whole answer; an area that cannot be drawn without it says so.

  • New
    the answer, turned into what a tile draws

    unraid_model.go converts Unraid's kilobytes to bytes, treats a sleeping disk's missing temperature as asleep rather than an error, and decides once what is a problem — disabled or any other state but OK, missing, read errors, hot (45 °C for a spinning disk, 60 °C for an SSD or NVMe), full (the disk's own usage warning, else 90 %) — so the tiles and the alerts agree.

  • New
    one answer per area, shared

    /api/unraid/area/{area} (array, parity, shares, VMs, UPS, notifications, info and an overview built from them, side by side) asks the server at most every 30 seconds per area for every viewer together, keeps the last good answer with its age when the server does not answer, and waits longer after a 429. /api/unraid/settings and /api/unraid/test set and try the connection behind the write token; the key is never in an answer.

  • New
    Unraid alerts reach you

    With "Send Unraid alerts through the alert channels" on, Unraid's own ALERT notifications, the array stopping, a parity check that finished with errors and a disk whose error count went up go through the same channels as downtime and container alerts — ntfy, Apprise, push and the rest — bundled the same way; the first look after a start only remembers, and so does the first after the address changes or a switch goes off and on, so one server's history is never sent as another's news; a finished parity check is read from the history entry of that run, since Unraid clears the check's own error count when it completes. Checked against a real Unraid 7.3.2 server, whose answers are recorded, anonymised, under internal/app/testdata/unraid/recorded-*.json.

  • New
    seven Unraid widgets in the catalogue

    , in a group of their own (How is the Unraid server doing?): Unraid (an overview), Unraid array, Parity, Shares, VMs, UPS and Unraid notifications. Each has only how it draws — refresh (30 seconds at least), rows where it lists, and whether a click opens the page in Unraid; the server they read is set once, under Config → Unraid.

  • New
    the Unraid overview and array tiles

    The overview reads a line per subject — array, used, parity, disks, alerts, VMs, UPS — with the worst problem in colour, and leaves out what the key may not read; when the server is out of reach it shows the last reading with its age, and it says so when the key is refused. Wide, it adds the newest alert. The array tile, wide, lists every disk grouped as parity, array and cache with its fill and temperature or its problem, a sleeping disk grey; narrow, only the problems, or "N disks fine".

  • New
    Parity, Shares, VMs, UPS and Unraid notifications tiles

    Parity shows the last check, or the running one with its progress, speed and time left, and its history when wide; Shares groups the shares by where they live — the array, a cache pool, or both — with each place's fill and the shares on it, since Unraid reports a share's used and free as those of its place (twenty-six identical percentages on a real server); VMs says how many run and which are paused or stopped; UPS shows charge, runtime and load and turns amber on battery, or says the server has no UPS; notifications list the unread ones newest first, the alerts red, and a notification's link opens on the server only when it is a path there (//host is not). Each says so when the key may not read it or this Unraid version lacks it.

  • New
    Config → Unraid

    , a section of its own in the config menu, since only the Unraid widgets read this server and the Containers view does not. It explains itself: How it works draws nextDash and the server with data running between them and ticks off the three steps (a Viewer key, the connection tested and saved, a widget on a page) from what the server says; What you get shows the seven widgets in miniature, each with an Add… that opens Widgets → Types on that kind with its Add focused. One place for the Unraid server every Unraid widget reads: its address (the Docker bridge gateway is suggested when nextDash runs in a container), an API key with the role Viewer, a switch for a self-signed certificate, one for reading the server and one for sending its alerts. Test connection names the server, its Unraid and API versions and what the key may read; a new address asks for the key again.

  • New
    a script to record the API

    scripts/unraid-record.py asks a real Unraid server for each area with a Viewer key and writes anonymised answers to internal/app/testdata/unraid/recorded-<area>.json: hostname, share and VM names, notification texts and the UPS model replaced; disk names (disk1, parity, cache), sizes, states and counts kept. It stops at a redirect rather than send the key on.

  • New
    the Unraid server is set in one place only

    A settings import, and the dashboard's own settings save, leave it as it is; only Config → Unraid changes it, so no file can point the saved key at another address. An overview the key may read nothing of now says so, instead of "not in this version"; a server name is cut by characters, not bytes; a server without virtual machines says so on the VMs tile.

  • Fix
    a one-column Shares tile cut its percentage off

    The figure after the bar was pushed past the tile's edge, and "array + cache" was shortened to "array +…". On a narrow tile the figure now takes only the room it needs and the bar gives way first.

  • Docs
    a short Unraid section in the README and the manual

    : what nextDash reads, the seven widgets, the alerts and the one read-only connection, and that deeper Unraid integration is planned. The README shows it with two screenshots from demo data: the seven widgets on a homelab page (Tarnished Brass) and Config → Unraid (Nordic Frost).

  • Docs
    themes up front

    README opens with what the look studio offers — 320 themes in 160 families, twelve characters, 26 backdrops, twelve looks, Compare, 🎲 and Apply, favourites and the theme editor — and the manual's table at the top points to it.

  • Docs
    sixteen new README screenshots

    , each in a theme of its own and none of them used before, from the same demo data: containers with their app icons, the dashboard and a homelab page, the Bookmarks view and its Broken filter, Collection health, search, tags and the command palette, the inbox and triage, the look studio, and Config → Appearance and Statistics. The captions follow what each view does now; the old screenshots are replaced.

  • Docs
    Config → Help catches up

    , in all six languages: 41 Custom-widget services with the new Monitoring group, twenty-nine widget kinds with a paragraph on the seven for Unraid, and Config → Containers' four tabs with a pointer to Config → Unraid.

  • Fix
    a paused parity check is not a finished one

    The API leaves running null and says PAUSED in the status; read as done, the pause sent "Parity check finished with N errors" and the tile showed the previous run.

  • Fix
    a failed resolver no longer reads as a stopped array

    The API answers it with HTTP 200 and the field null; read as an empty answer, it alerted "The Unraid array stopped" and blanked the tiles. It now counts as unreachable, and the last good answer stays.

  • Fix
    a second Unraid push no longer replaces the first

    without a sound: each alert has its own tag.

  • Fix
    a disk's warning is its usage threshold, not a temperature

    A per-disk warning of 70 % made the disk "hot" at 70 °C; it now marks the disk full at 70 %.

  • Fix
    an address without http:// is refused

    Save stored it as blank, dropped the key and said Saved.

  • Fix
    emptying the address no longer saves the Docker gateway

    The suggestion filled the field on every save, so clearing a saved address pointed nextDash at another server and dropped the key without the warning.

  • Fix
    an Unraid notice without a subject is named by its title or description

    , not "Unraid is offline".

  • Fix
    a restore forgets the previous Unraid server's answers and schema

    , and drops a key the backup did not carry when the restored address is another one.

  • Fix
    Test connection says what is wrong when the server answered

    : a key that may not read the server's info, or an Unraid version whose API lacks what nextDash reads, no longer reads as "The server did not answer".

  • Fix
    the schema is kept per address

    A lookup still running against the old address after a save was joined, and cached for a day, for the new one.

  • Fix
    the address and its key change together

    A poll between the two writes of a save could send the old key to the new address.

Web search

  • New
    search the web from the search panel

    Shift+Enter, or a click on the last row (Search the web: …), sends the query to /api/web-search, which asks SearXNG's JSON API or the Brave Search API. The engine sees the server, never the browser. Nothing goes out while typing, and a command, a finder or a query with a filter in it never goes out at all. Five seconds per answer, at most 20 results, and an answer cached for a minute per address, category and query.

  • New
    results under *From the web

    , below the bookmarks: Web, News and Video, plus IT with SearXNG, on Shift+←/→; → opens a column with a result's title, address, date and text, ← closes it; a result from a host you keep says In your bookmarks: ‹name›* and Alt+Enter opens the bookmark; an infobox becomes a card. A result loads nothing until opened — no favicons, no thumbnails. On an error or an empty answer the panel names the reason and offers Open in ‹engine›.

  • New
    Recent on the web

    The last eight web queries, in this browser only (nextdash.webSearchRecent), as a folded group in the empty panel with a row to clear them. A web search is not written to the activity log, and the server keeps no record of it.

  • New
    Config → Behavior → Keyboard & search → Web search

    Engine (Off by default, SearXNG, Brave Search API), the SearXNG address, the Brave key and Test connection, which searches for test and reports the count or the reason. Settings.WebSearchEngine and WebSearchSearxngURL; the key lives apart in data/web-search-secrets.json, is never sent back to the browser, and travels in a backup only with Tokens and passwords.

  • New
    the address bar can search the web

    While an engine is on, the page links /opensearch-web.xml, a second engine named ‹title› Web that opens /#search?web={searchTerms} with the web results already asked for; with the engine off the description answers 404.

  • Fix
    Web search answers follow the SearXNG address

    The cache ignored it, so Test said Working for a broken new address and the panel showed the old instance's results.

  • Fix
    a row picked while web results load keeps the selection

    The answer moved it to the first web result, and Enter opened a web page.

  • Fix
    one failed status check no longer removes the web search tabs

    until a reload.

  • Fix
    SearXNG engines that could not answer are a failure

    , not "Nothing found" cached for a minute.

  • Fix
    Shift+←/→ also leaves a web category that failed
  • Fix
    no "Open in SearXNG" row without a SearXNG address

    ; it opened Brave.

  • Fix
    the two OpenSearch engines keep different names under a long title
  • Fix
    the cheat sheet lists the web search keys

    (Shift+Enter, Shift+←/→, Alt+Enter) when an engine is on.

  • Fix
    the search keys try again after the search bundle failed to load

    , instead of staying dead until a reload.

Theme editor

  • New
    every backdrop in the theme editor, as tiles

    The backdrop row of Shape & character offered nine of the patterns in a list; it now shows Automatic and all 26 as tiles drawn in the colours of the theme being edited. The list comes from the server (/api/themes/meta gains backdrops), so a new recipe appears without touching the editor.

  • New
    your own themes stand out

    In the theme browser they come first under Your themes, with a yours badge, a Yours segment and the search word yours; a packaged theme whose colours you changed wears recoloured. The Theme picker in Appearance lists Your themes and Built in as two groups, and says · yours when one of yours is in use. themeMeta gains own, recoloured and look.

  • New
    a theme of your own can carry a look

    ThemeColors.Look holds what a built-in look sets: backdrop and its sliders, card glass, depth, headers, type and spacing. The server keeps only parts the page can draw and drops a look on a packaged theme; a theme file carries it.

  • New
    picking a theme brings its look

    A card in the theme browser (saved on Apply), the Theme picker and :theme apply it; switching halves with Quick mode or the system's dark mode does not, and neither does Random theme. Use this theme's look above the grid picks a theme without it, remembered per browser. Theme looks and built-in looks go through one function, applyLookAnswers.

  • New
    the theme editor in the theme browser

    ✎ Edit on a card of your own, ✎ Recolour on a packaged one, or e on a focused card opens the editor in the panel, with ← Themes back to the grid and a link to it on the other tabs. Colour changes show on the page as you type and are saved on Apply; Cancel, Compare and Reset tab include them. A theme of your own gets This theme's look: Take the look on screen and Clear, written to both halves of a pair.

  • New
    Save as theme…

    at the bottom of the theme browser turns what is on screen into a theme of your own: the colours of the theme in use (a recolour included), the look if you like, and its other half from the real packaged half when it has one. It is saved at once and opens in the editor; picking it still waits for Apply.

  • New
    the theme browser widens from its left edge

    Drag the edge to make the panel wider, or focus it and use ← / → (Shift for bigger steps); a double-click gives the default width back. It never goes narrower than the default, where the six tabs fit, and always leaves 240 px of the page beside it. The width is kept per browser; on a phone the panel stays a bottom sheet.

  • New
    the theme browser's keys on the cheat sheet

    A section of its own in the ! modal and on the printed sheet: ← / → for the tabs, the arrows over the cards, Enter to choose, e to edit or recolour, \ held to compare, ⌘/Ctrl + Enter to apply and Esc to cancel. In all six languages.

  • Fix
    the printed cheat sheet named its font by this computer's path

    generate-cheatsheet.cjs wrote an absolute file:// URL into nextDash-cheatsheet.html; it is now relative to the sheet, so the HTML is the same wherever it is generated.

  • Docs
    the theme editor in the manual and in Help

    , in all six languages: §16.1 and the theme browser section describe the badges, the editor in the panel, the look switch and Save as theme…; §16.5 the 26 backdrop tiles, a theme's look and the picker groups.

  • Tests
    the theme editor

    Go for the meta's backdrops, own and recoloured, and sanitizeThemeLook (ranges, unknown words, an empty look, looks on packaged themes); Playwright in config-custom-theme-character.spec.js (27 tiles, a look through export and import), config-theme-browser-yours.spec.js, theme-look-on-pick.spec.js, look-studio-theme-editor.spec.js and look-studio-save-as-theme.spec.js.

  • Fix
    saving the colours keeps the Neutrals collection

    One save emptied the chip for good; installs already stripped are repaired on load.

  • Fix
    deleting the theme in use falls back to a real theme

    It set default, which is no theme id, and the page lost every colour; the half shown under Follow system counts as in use too.

  • Fix
    Save as theme and Duplicate keep the backdrop on screen

    A built-in's recipe is chosen by its id, and the copy drew another.

  • Fix
    a new or edited theme shows its depth, glow and effects at once

    , not after a reload: the cache of /api/themes/meta is refreshed after a colours save.

  • Fix
    :theme, the random theme and an OS light/dark switch bring the theme's surfaces

    , not the previous theme's depth, glow, backdrop and card glass.

  • Fix
    surface changes for "this theme" show under Follow system and a random theme

    They were stored under the chosen theme and drawn from the one on screen.

  • Fix
    Save as theme gives a typed name a number when it is taken

    , and caps it, as a rename does.

  • Fix
    :theme lists themes made or deleted since the page loaded
  • Fix
    a light/dark pair keeps the theme's own surfaces

    , and deleting a theme clears its rows in the settings.

  • Fix
    a look picked outside the studio draws its backdrop variant at once

    , not after a reload.

  • Fix
    the other half made by Save as theme brings the look too
  • Fix
    an imported look with part of its backdrop tuning takes the defaults for the rest

    , not zero.

Config

  • New
    Config → Overview as panels

    The section was eight figure tiles, four explained blocks, a news band and a colophon line, all framed and titled alike. It is now one attention line and two zones. Your install has a panel each for bookmarks, the inbox (unread, arrivals per day over two weeks, the oldest waiting link), containers (running, stopped, unhealthy, updates; from the list search keeps, left out without a Docker socket), health (the ring and the four states) and statistics (opens this week from the open log with two weeks of bars, the most-opened link, the busiest page and the cleanup score with its heaviest deduction). From nextDash holds the three newest posts from nextdash.cc, the three newest announced features with the running release and Show what's new under them, and a tip of the day from Help → Tips that steps back and forward in place. Every panel has the same shape — title with a state dot, a way in, its own warning in the foot — and Needs attention is a row of chips (now with container updates) instead of a block of sentences..

  • Fix
    the sub-tab strip no longer jumps between sections

    The band's line under the section name is cut to one line (the whole sentence on hover) and keeps its height when a section has none, so a long line such as Bookmarks' no longer pushed the rail and the tabs down. Statistics' tabs sat 2px lower and its rule 3px lower, beside a scope picker taller than the tabs; both line up with the other sections now.

  • Tests
    the overview spec follows the panels

    : counts, the attention chips and where they lead, the clean line, the cleanup reason, the four health states, the containers panel from stubbed Docker routes and its absence without a socket, the newest dated features and where the first one leads, the tip stepping in place and All tips landing on Help → Tips, and All news landing on About → News.

  • Fix
    Keep settings on this device only leaves web search and container icons to the server

    An old device copy turned web search off for every browser or put old icons back; the Docker keys not yet on the list are added too.

  • Fix
    Config → Unraid can be reached from the command palette

    (:config unraid).

  • Fix
    clearing the cheat sheet filter opens the section of the view it came from again
  • Fix
    Only changed and the settings filter stay in sections with a bar for them

    ; carried into Containers they hid settings with no way back.

  • Fix
    the Overview tip buttons keep keyboard focus
  • Fix
    no What's new explanation starts mid-sentence

    An item whose bold part carries on ("X, and Y." or "X — Y.") was split at the bold, and the line under the title opened with a comma, a dash or a lower-case word, in 143 items across 33 releases. splitItemText now drops a dash or colon and capitalises what follows, and joins a comma or a lower-case continuation to the title up to its full stop.

  • Fix
    the arrow keys keep walking Appearance's tabs

    Appearance repaints more than once after its tab changes, and every repaint after the first left the focus on the page: the second arrow press did nothing. A strip drawn again just after a keyboard switch now gives the focus back to the tab.

Tours and tips

  • New
    the dashboard tour opens on what is new in this release, and every reader sees it once more

    Four steps come first, each with a moving drawing: web search (a search, your bookmark, the web results with their tabs, and Shift+Enter, Shift+←/→ and Alt+Enter), app icons (letters giving way to the apps' icons, and the ✎ menu), the theme editor (the panel widening from its left edge, a recolour, Save as theme…) and the Unraid widgets (the array with fill and temperature, a running parity check, the shares). The theme browser step loses its "New:". Twenty steps in all, in six languages; the scenes rest on their finished picture with less motion, as before. The tip id moves to dashboardTutorialV3 everywhere it is named (the tour, DashboardPromos, the Onboarding list in config and search, the test fixtures and helpers), so a reader who finished V2 is offered it again, after What's new. dashboard-tutorial.spec.js checks the twenty titles, that a reader who saw V2 gets it opening on web search, and that the new scenes carry no English. MANUAL's tour line follows.

  • New
    the Containers tour covers v1.17, and runs once more for everyone

    Two new steps, each with a moving drawing: every container with its app's icon (letters giving way to icons, and the ✎ menu in the side panel) and the Resources charts (a cursor walking an hour of CPU and memory with its values, a stretch dragged out to zoom, and the keys). The Config step is redrawn for the four tabs — a row each for Connection, View, Updates and Alerts, with the selection walking down them — and its text follows. Fifteen steps instead of thirteen, in six languages; a label longer than its room is drawn narrower (fitLabel) rather than over its neighbour. The tip id moves to containersTutorialV3 everywhere it is named, and PREVIOUS_TIP_IDS replaces PREVIOUS_TIP_ID: a step's since (2 or 3) against the newest earlier tour the reader took decides which steps carry New, and the update note lists what came since — a V1 reader gets both lists. containers-tutorial.spec.js checks the fifteen titles and the marks for a V2 and a V1 reader; the contrast spec walks fifteen steps.

  • New
    a tip for the QR code

    Want a link on your phone? under Editing and organising in Config → Help → Tips (tipEditQrCode, six languages): Shift+J or QR code in the right-click menu, drawn in the browser so the address goes nowhere. MANUAL gets the same as a tip under the right-click menu, where QR code was already listed.

  • Fix
    the cheat sheet catches up

    Four rows it lacked, in the ! modal and on the printed sheet, in six languages: the theme browser's left edge (←/→, Shift, Home, End), a chart's keys in the Bookmarks view and in Containers → Resources (←/→, +/−, 0), and the app icon picker (↓ into the grid, the arrows, Alt+←/→ for the variant). The web search rows get short print labels, and nextDash-cheatsheet.html/.pdf are regenerated — the printed sheet had not had the web search keys at all.

Translations

  • Docs
    web search in all six languages, in Help, Tips and the manual

    The 38 strings of web search and the three cheat-sheet rows for its keys, English since the feature landed, are in Dutch, German, French, Chinese and Spanish; the not configured message names the real tab, Behavior → Keyboard & search. Config → Help: Searching the web and the second address-bar engine under Searching your bookmarks, web search in Behavior's Keyboard & search line, A wider panel in Themes, and alert secrets left out of a backup without tokens in Data — all six languages. Tips: web search under Finding things and a wider theme browser under Making it yours. MANUAL: Searching the web in §8.3, the web engine in §8.4 and the address table, the Keyboard & search row, the theme browser's width, the alert secrets and the Unraid and Brave keys under what a backup carries, :remove into the trash, an Unraid disk full at its own usage warning (hot at 45 °C or 60 °C), an Unraid address that needs its scheme and what Test connection reports, and the icon sets' private names, weekly re-ask, 3000-file cap and favicon fallback.

  • Docs
    the overview panels and the icon menus in all six languages

    The 35 strings of Config → Overview's panels, attention line and tip, and the three new headings of the side panel's ⋯ menu, are in Dutch, German, French, Chinese and Spanish; they had been English fallbacks in the code, with no locale key behind them.

  • Docs
    Help, README and the manual describe them

    Config → Help: the Overview line under Configuring, the side panel's head (the ✎ on the icon with its three choices, the ⋯ under its headings) in the Bookmarks view tab, and choose an app icon in the bookmark form's ✎ — in all six languages. MANUAL §11.3 and §17.1/§17.8 rewritten for the panels and the two menus, §19.4 names the side panel's pencil; README gains a Config → Overview line and the app-icons line says where the pencil is.

  • Docs
    every new string in all six languages

    The 138 strings this release added in English only — the QR code, the Unraid widgets and Config → Unraid, and Containers' tabs — are in Dutch, German, French, Chinese and Spanish, and two that changed (the right-click menu's cheat-sheet line, the container notices' note) are brought up to date; validate:locale-parity, the placeholder and cheat-sheet checks pass.

  • Fix
    thirty strings that never reached a locale file

    The app icon picker and the container drawer's icon menu, the Apprise fields, the charts and outage timeline in Collection health, and the chart and icon credits under About called for keys that did not exist, so they stood in English in every language. They are in en.json and translated.

  • Docs
    README and the manual describe this release

    Twenty-nine widget kinds with the seven for Unraid, 41 Custom-widget services (table rebuilt from the presets, the retired ones named), Apprise among the alert services, app icons and DISABLE_ICON_SETS, the Custom widget's counting paths and token sign-ins, the charts and per-monitor outages in Collection health, and the two test-only fixture variables.

Docs

  • Docs
    static/data/whats-new/v1.17.0.json and its index entry

    , leading the What's new window; whats-new-stub.js's DASHBOARD_RELEASE moved to 2026.10-dashboard-release-v1.17.0 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v315; whats-new-hidden-release.spec.js follows. An Overview spotlight for the Unraid widgets, with since v1.17.0, in six languages. go generate refreshed asset_hashes_gen.go.

  • Docs
    the Unraid template

    : templates/nextdash.xml and the live copy in unraid_templates carry v1.17.0 and v1.16.0 in <Changes> (keeping the last five releases), the date, Unraid, web search and the look studio in the overview, 28 built-in widget kinds, and all 18 README screenshots.

Tests

  • Tests
    Go

    the index (rounds, aliases, variants, search), the 62 containers and the bookmark hosts, refresh with ETag, stale copy and back-off, the cache route (unknown names, traversal, one fetch, sanitising, wrapped PNG, the hour of misses), adopt, the API handlers, the container override and the background fill.

  • Tests
    every monitor, per day

    bookmarks-health-modal.spec.js reads the days through the keys (share, response and checks, a day without checks) and keeps the plain bars when uPlot is blocked; Go pins the pooling per UTC day, maintenance left out, a failed check without a time, and the days carried in the report.

  • Tests
    charts, phase 3

    bookmarks-health-tab.spec.js reads a monitor's buckets through the keys (response, checks, state), checks the average line and the plain chart with its readout without uPlot; bookmarks-health-modal.spec.js the score's low point, marked and read out, and its plain chart; config-stats-trend-scope.spec.js the healthy share read by the keys, a missing day as a gap and not a zero, and the plain line without uPlot.

  • Tests
    charts, phase 4

    the Statistics specs that measured the plain bars (config-stats, -axis-labels, -inbox-trend, -panels) now read the uPlot chart: a row a period in its table, the value axis from 0, the tick labels' places on the canvas (no collisions, none past an edge), the tooltip under the pointer at the top of a column, the keys and their readout, both series' colours, the backlog line on its own axis, and the plain bars when uPlot is blocked. config-stats-panels also reads the healthy-share gap from the new chart; it still looked for the old polylines after the phase 3 change.

  • Tests
    charts

    docker-drawer-charts.spec.js and bookmarks-health-modal.spec.js check the charts through the pointer and the keys: the tooltip only in the pointed chart while the others follow, the arrow keys and their readout, + and 0, the table, a redraw on a theme change, and the plain charts when uPlot is blocked. bookmarks-health-large.spec.js checks the large modal: the p95 in the readout, ← and → kept in a focused chart, a bar's share and checks, the bars per period, and the plain charts without uPlot. config-about.spec.js checks the credit, and bookmarks-health-modal.spec.js the outages card: the per-monitor order, a lane per monitor with a bar per outage, and the list opened from Show list.

  • Tests
    Apprise

    notify-apprise.spec.js picks Apprise in the panel, fills in the URL and a tag and presses Send test alert against a stub apprise-api, checking the body that arrives and the sentence shown for a 424; Go tables cover the type per event, the tag and the refusals.

  • Tests
    presets against recorded answers

    widget-presets-recorded.spec.js points every preset still offered at a local stub that answers with its service's documented response (tests/fixtures/widget-presets/, source in each), through the route Ask now uses, and fails on a figure that finds nothing or finds a whole object. The fixture holds the service's side of the sign-in, so a wrong header or prefix in a preset fails too. Through the panel itself: retired presets are not offered, and Pi-hole v6 asks for a password only and signs in on Ask now. Go: counting and the last entry, and the token sign-in (prefix, no prefix, password only, renewal, no token).

  • Tests
    Playwright

    icon-set-picker.spec.js (a suggestion, the picker by keyboard, Escape, offline, Fetch again, dashboard rows), docker-icons.spec.js (row icons, Use letter across a reload, Automatic, the picker, the theme switch) and a credits test in config-about.spec.js.

  • Tests
    the P1s of bug hunt round 3

    : a paused parity check, a failed resolver, a recovery seen by a Re-check, an alias match, :remove through the trash, and a widget key kept across Save after Health and after a re-picked Plex preset.

  • Tests
    the P2s of bug hunt round 3

    , each one failing without its fix; config-docker-usage-alerts opens the Alerts tab since Containers has tabs.

  • Tests
    a selection of the P3s of bug hunt round 3

    , each one failing without its fix.

  • Tests
    the remaining P3s of bug hunt round 3

    : config-carried-state.spec.js, and Go tests for the Unraid, icon, widget, web search and look fixes.

  • Tests
    CI follows the release

    : Containers tabs in docker-auto-update and docker-drawer-charts, twenty tour steps in dashboard-tutorial-contrast, Unraid in dashboard-command-palette-config, the backdrop switched off through the setting in theme-backdrop-variety, the favicon outcome stubbed in health-bulk-fetching, and config-subtab-keyboard waits for the focus before the next key.

Only docs and tests changed in this release.

v1.16.0 The theme browser becomes a look studio: a panel beside the dashboard whose tabs change the theme, its backdrop, the card glass, the category headers and the type live, with twelve ready-made looks and nothing stored until Apply. +15 4 fix

The theme browser becomes a look studio: a panel beside the dashboard whose tabs change the theme, its backdrop, the card glass, the category headers and the type live, with twelve ready-made looks and nothing stored until Apply. Backdrops grow from 9 to 26, and every built-in theme pair now has one chosen for it rather than hashed, so most themes show a different backdrop after the update. Appearance gains a Background and a Surface tab, card glass and category header styles, and a Neutrals collection adds ten glass themes.

Backdrops

  • New
    26 backdrop recipes instead of 9

    themeBackdropImage adds mesh, aurora, bokeh, nebula, stars, sunset, dunes, mountains, waves, topo, perspective, blueprint, pinstripe, hexagons, halftone, prism and chevron, all built from the theme's own --accent-primary, --accent-error and --background-primary. Recipes that need it carry a per-layer background-size and -position, emitted as --theme-backdrop-size and --theme-backdrop-position beside --theme-backdrop; theme_backdrop_recipes_test.go checks every recipe for an image, no bare colour layer, and lists as long as its layers.

  • New
    every built-in theme pair has a backdrop chosen for it

    theme_backdrop_choice.go maps all 160 pairs (light and dark share one) to a recipe picked from name, palette and archetype; each recipe is used 3 to 10 times. Lookup order in themeBackdropRecipeFor: the theme's Backdrop field, the choice map, the archetype, then the hash, which now only reaches custom themes. The 28 Backdrop fields on built-ins moved into the map. Visible change: most themes draw a different backdrop than in v1.15.8. theme_backdrop_choice_test.go pins coverage, pairing, the 3–10 spread and that no entry names a theme that does not exist.

  • New
    choose and tune the backdrop

    themeBackdrop (and ThemeSurfacePref.Backdrop) is now follow, off or a recipe name; a stored on reads as follow. A chosen recipe is drawn through one rule per recipe in /api/theme.css (themeBackdropOverrideCSS, body[data-backdrop-recipe]). Settings.BackdropTuning holds intensity, scale, variant, blur, brightness, saturation and theme tint; all but the variant are live --bd-* variables, the variant reloads /api/theme.css?seed=N (no-store). GET /api/themes/backdrops serves the thumbnails.

  • New
    the backdrop is drawn on a layer of its own

    , .theme-backdrop-layer as the first child of <body>, so blur, brightness and saturation filter the backdrop and never the bookmarks. A background image of your own (body::after) gets the same values separately. The stacking is unchanged: theme colour, backdrop, pattern, your own background, content.

  • Fix
    a theme's dot pattern no longer covers its backdrop

    With the pattern left to the theme, there is none while a backdrop is shown.

Appearance

  • New
    Background and Surface tabs

    between Look and Grid. Background holds the source (Auto, None, Gradient, Image), its opacity, the backdrop picker and settings, and the pattern; Surface holds depth, glow, effects, "Use these for every theme" and card glass. Look keeps theme, favicons, type, text contrast and animations. "Only changed" and Find settings know the new tabs.

  • New
    card glass

    ThemeSurfacePref.Alpha, Blur and Border per theme, or Settings.CardGlass with "Use these for every theme"; written as --theme-surface-alpha and --theme-surface-blur on <html> and data-card-border on <body>. It works at depth Glass, and the panel says so with a button to switch. In layouts without cards (Default, Compact, Masonry) Own gives each category a pane (data-card-glass="own"); the layout preset is repeated in the panel. A badge shows the contrast of text on a pane (ThemeBrowser.contrastRatio).

  • New
    category header styles

    on the Rows tab: CategoryHeaderStyle (theme, clean, underlined, boxed, label, group), CategoryHeaderSize, ShowCategoryIcon (on by default, with a missing-key entry), ShowCategoryCount and CategoryHeaderAccentLine, as data-cat-* on <body>, drawn by category-header.css. category_header_test.go covers defaults and sanitising.

Theme browser

  • New
    the theme browser is a look studio

    theme-browser.js drops AppModal for a panel over the right of the dashboard (a sheet below 768 px), with tabs Themes, Backdrop, Surface, Headers, Layout and Looks; the other tabs reuse the Appearance controls through dashboard-config-studio.js. A dot marks a tab that differs from the look at opening. Shift+A, Browse…, the corner notice and the changes tour all open it.

  • New
    preview without saving

    While the studio is open, saveSettings sends the look fields as they were at opening and everything else as usual; Apply sends one save; Cancel, Esc, the × in the corner and a click on the dashboard beside the panel restore the snapshot (only a click that starts and ends outside, so a drag from the panel does not count). Compare is a switch (and \ held) that shows the look from before. Applies to (this theme or all themes), Reset tab and 🎲 per tab. The rest of <body> is inert, without aria-modal, so the dashboard still scrolls; ⌘/Ctrl + Enter applies, the arrow keys walk the cards and Enter picks one. No "Saved" toast during a preview.

  • New
    twelve looks

    : Glass, Glass boxed, Frosted, Aurora, Night sky, Soft, Desert, Paper, Blueprint, Terminal, Neon and Plain, each setting backdrop, tuning, card glass, depth, all five header fields, font, density and spacing, with a line saying what it sets.

  • New
    the layout preset is part of the preview

    , and the Layout tab holds type, text contrast and favicons. Every setting in the studio has an ℹ, whose dialog opens over the panel.

  • New
    a collection chip

    beside the archetype chips, from collections in /api/themes/meta.

  • New
    the dashboard tour opens on what is new, and every reader sees it once more

    Three steps come first, each with a moving drawing: the theme browser beside the dashboard, the 26 backdrops, and the looks, card glass, category headers and Neutrals; the Config step names the backdrop, card glass and headers. Sixteen steps in all, in six languages. The tip id moves to dashboardTutorialV2 everywhere it is named (the tour, DashboardPromos, the Onboarding list in config and search, the test fixtures), so a reader who finished V1 is offered it again, after What's new. dashboard-tutorial.spec.js checks the sixteen titles, that a reader who saw V1 gets it opening on the theme browser, and that the new scenes carry no English.

  • New
    the theme in use is named above the grid

    : "In use: …", or once another card is picked "Chosen: … · … stays until Apply", with Show, which clears the search and filters if they hide the card and scrolls it into view. The × in the corner stays in the corner on the phone sheet, where the key line is hidden.

Themes

  • New
    the Neutrals collection

    : Slate, Zinc, Gray, Stone and Neutral, each light and dark, under glass (SurfaceAlpha 0.55, SurfaceBlur 12), with backdrops aurora, mesh, mountains, dunes and bokeh. ThemeColors.Collection names a theme's collection.

Dashboard

  • Fix
    with the Launcher layout preset, widgets looked empty

    Widgets are .category blocks too, so .layout-launcher.category's align-items: flex-start shrank their body to the width of its widest word. .layout-launcher.category.dashboard-widget stretches them to the full row again.

  • Fix
    a widget inside a category that is already a pane drew a second card

    It now sits flat in the pane.

  • Fix
    Dark Reader recoloured the page on top of the theme

    The page now asks it to leave nextDash alone.

Docs

  • Docs
    static/data/whats-new/v1.16.0.json and its index entry

    , leading the What's new window; whats-new-stub.js moves DASHBOARD_RELEASE to v1.16.0 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v314. Config → Overview names the look studio.

  • Docs
    MANUAL §16

    has eight Appearance tabs, a new The theme browser part with its tabs and the twelve looks, card glass under Surfaces, the backdrop layers and all 26 backdrops under §16.4, and the category header in the Rows table. README names the look studio and the backdrops, and counts 160 families.

  • Docs
    Config → Help → Appearance and Tips follow the look studio

    , in all six languages: eight tabs, the browser as a panel with Apply and Cancel, its tabs and looks, backdrops, card glass and the Neutrals collection; four new tips (looks, backdrop, card glass, category header). The theme browser's corner notice says nothing is saved until Apply.

Tests

  • Tests
    look-studio.spec.js

    (serial: overlay without moving the columns, scrolling, Cancel, saves of other settings during a preview, hover, Enter, Compare, Apply, card glass and layout, back to Appearance), appearance-background-surface.spec.js, and Go tests for recipes, choices, tuning, category headers and TestThemeCSSTakesSeedFromQuery. Specs that drove the old theme modal or the moved controls are updated: the eight Appearance tabs, Apply before a reload, and the theme pattern measured with the backdrop off.

  • Tests
    the row-width check failed on a slow runner

    By the time it measured, the docked action bar had slid away after its default two seconds and lay past the right edge; it is inert while away, and the check now skips inert elements.

Only docs and tests changed in this release.

v1.15.8 The documentation puts the self-hosting half up front: how the Containers view, the bookmarks of your services, their health checks and the alerts work together. +2 59 fix

The documentation puts the self-hosting half up front: how the Containers view, the bookmarks of your services, their health checks and the alerts work together. A second bug hunt across the app fixes 108 more bugs: moves and undos that put bookmarks on the wrong page, copies of one address acting for each other, settings and backups that did not keep, and automatic container updates that failed in silence.

Dashboard

  • Fix
    undo of a tag-filter delete after a page switch saved the rows onto the wrong page

    It now restores them from the trash onto their own page, as the multi-select undo does, and drops the trash entries after a same-page undo.

  • Fix
    a page save undid newer opens and health results

    A tab sends back the open counts and check it loaded; a newer last open or check stored since (another device, the monitor) now wins, with its error and "down since".

  • Fix
    a tab still showing a deleted page brought it back as "Page N"

    Saving rows to a page that does not exist answers 404, a page list naming a page that sits in the trash leaves it out, and deleting a page that is already gone no longer adds an empty trash entry that blocked restoring the real one. Undo of a page delete in Config now restores the page from the trash, widgets included.

  • Fix
    undo of a multi-select tag change, or of a category move, did nothing once the page had reloaded

    A focus that found a new revision was enough. The tag undo now writes through PATCH /api/bookmarks by URL, and the category undo takes the server path when its rows are no longer the ones on screen.

  • Fix
    GET /api/trash without the token returned a deleted page's custom-widget address and credential id

    The listing now withholds them, as the blocks route does.

  • Fix
    a bookmark moved to another page kept the source page's category id

    and sat under "Unknown category" there (Shift+M, the selection bar and the tag filter). It now takes the target's category with the same name, or none.

  • Fix
    on a touch screen every touch on a bookmark started a drag

    , so a swipe that began on a row could not scroll. There the grip over the icon drags and the rest of the row scrolls; a cancelled touch now ends a drag instead of leaving the scroll lock on.

  • Fix
    with a write token, health results still pending when the tab closed were refused

    A beacon cannot carry the token; a keepalive fetch with it is used instead.

  • Fix
    smaller things

    An undone delete no longer leaves a trash entry that refused Restore; pinned rows keep the order they are given; a drag no longer overwrites the hand-made order of sorted categories; Shift+Alt+←/→ files the row in the category beside it in packed columns and keeps the cursor on it; Alt+←/→ on a category steps past widgets and over hidden empty categories; undo of a bulk move no longer jumps to the source page; a failed reorder save no longer reports "saved" afterwards.

Bookmarks and Health

  • Fix
    editing the second copy of a duplicated address changed the first

    The side panel, the Checking select and the icon and preview sweeps now send which copy they mean.

  • Fix
    with the same address on two pages, the side panel's Health tab, its keys and Work through acted on the other page's copy

    The report is joined by page and address.

  • Fix
    in the Unsorted view, Delete, Export CSV and the icon and preview fetches on a selection did nothing

    They read the same rows the selection bar counts.

  • Fix
    saving Expectations in the Bookmarks view removed the bookmark's sign-in

    The credential names were never loaded there (and with a write token were refused), so the select showed "Nothing"; they load with the report, and a credential missing from the list stays selected.

  • Fix
    a manual re-check used the first copy's rules but recorded the result on the copy that was clicked

    /api/ping takes the row's page and index.

  • Fix
    checks from Retest all, the daily re-check and manual re-checks inside a maintenance window counted as outages

    Their samples are now marked like the monitor's own.

  • Fix
    a certificate threshold crossed during Retest all or a check was marked notified with no alert

    , so the monitor never warned for it. Those checks now send the warning.

  • Fix
    health.down and health.up webhooks never fired unless an alert service or push was also set up

    An enabled Config → Webhooks endpoint now counts as a listener.

  • Fix
    moving a category to another page, or merging it, removed the category even when some bookmarks stayed behind

    It now stays until every bookmark has left.

  • Fix
    Work through in the Bookmarks view went to the wrong card after a delete

    Its queue is remapped with Health's when the report reloads.

  • Fix
    a collection rule "Category includes …" picked from the suggestions never matched

    A page::id value matches that page's category; a bare id still matches on every page.

  • Fix
    smaller things

    Copies of an address are counted as the server counts them; saving Expectations on an unmonitored bookmark keeps its monitor settings; Enter in a tags field with nothing chosen saves instead of adding a tag; "Recently opened" shows the most recent; a check-mode change from Health touches only that page's copy.

Inbox

  • Fix
    holding d or Shift+K in triage acted on card after card

    , with no undo for deletes; and a second key while a write was in flight acted on the same card again. Repeats are ignored and one action runs per card at a time.

  • Fix
    Ctrl/Cmd chords ran triage actions

    : Ctrl/Cmd+D deleted the link, Cmd+R marked it read and blocked the reload. Chords are left to the browser, as in the list.

  • Fix
    a source run moved its cursor before the import was written

    , so a refused or failed round was skipped for good; one invalid row also refused the whole round. The cursor moves after the write, and invalid rows are left out.

  • Fix
    a source whose page was deleted imported into a page nothing shows

    The run is refused with a message.

  • Fix
    with a write token, the extension's link previews and icon uploads were refused

    The shared code now gets the token in the extension too.

  • Fix
    smaller things

    A pasted bare domain saves to the Inbox; a source no longer brings back a link it imported before and the reader deleted; Mastodon names are cut on a character; the extension shows "D" for an address filed on another page and keeps typed tags on "Save to Inbox"; undoing a snooze restores the old wake time; bulk Keep and Promote undo leave read links read; bulk Promote files a link whose copy waits in Unsorted; auto-file on Keep no longer claims "Filed on X" for a link that was not; an undo that pushes a link out at the cap says so; the Inbox widget no longer counts snoozed links.

Containers

  • New
    the Disk tab shows the progress overlay while it measures

    A measurement is one /system/df read and can take a long time on a large host. The first load and Refresh now use the shared ProgressOverlay.begin (dockerDiskMeasuringTitle, new in all six locales), which appears after 300 ms and closes when the answer arrives.

  • Fix
    nextDash could miss its own container and stop itself mid-update

    With a set hostname or host networking on cgroup v2, it took the first 64-hex string in /proc/self/mountinfo, which on overlay2, btrfs (Unraid's docker.img) and zfs is a storage layer; now only Docker's /containers/<id>/ paths count.

  • Fix
    Remove stopped took containers that stopped after the Disk tab measured

    The request now names the containers the question showed, and only those go.

  • Fix
    an automatic update that failed and put the old container back was logged as a success with no notice

    It now sends "could not be updated automatically" with the step it failed at.

  • Fix
    the automatic update's notices ignored the Notifications switch and the mute list

    Its "was updated automatically", "could not be updated automatically" and rollback notices went out with notices switched off or the container muted. dispatchContainerNotices now checks both for every notice, wherever it was made.

  • Fix
    an update could unpublish a port

    A published port the old image also EXPOSEd was dropped with the image defaults; every port in PortBindings stays exposed.

  • Fix
    smaller things

    A paused container is left out of automatic updates and a restarting one is watched; failure notices of an update that ran out of time arrive; a night's window past midnight tries a failed update once, and a run respects opt-outs and the window's end; the Logs tab keeps the newest lines; the widget leaves out nextDash's disk-measuring container; Backspace on the Disk tab no longer offers to remove containers ticked elsewhere; a window with the same start and end hour becomes two hours.

Config

  • Fix
    forgetting or changing the archive keys was undone by the next settings save

    in the same tab, which posted the keys loaded with the page. Settings saves no longer carry the keys, and the panel updates the in-memory switch.

  • Fix
    "Keep settings on this device only" let an old device copy overwrite the server's data

    : tag rules, saved searches, maintenance windows, alert, backup, log and container settings added in another browser were lost on the next save. The device copy now holds only how this device looks.

  • Fix
    Hypr mode and the date, time and weather toggles only applied after a reload
  • Fix
    "Reset panel" skipped each setting's own apply step

    , so a reset language, weather location or shortcut hints stayed as they were until a reload.

  • Fix
    smaller things

    Text contrast "Normal" is 0.47, the server's default; a restore applies its log settings at once; "Send test" waits for the address just typed; Statistics → Collection keeps its backups and sources rows with a write token; a bare #config restores the Data & backups, Logs, Bookmarks, Widgets, Inbox and About sub-tabs.

Search

  • Fix
    an instant shortcut opened its bookmark and then reopened the search on its empty state

    50 ms later.

  • Fix
    :pin, :tag, :move, :edit, :copy and :archive never saw the selected row

    The search reset the row ':' was pressed on with every keystroke; it now lasts until the search closes.

  • Fix
    a dialog over the palette (the :note editor, the cheat sheet) lost Enter, the arrows, Tab and Escape to the palette behind it

    A newline wiped the note, and Escape closed both.

  • Fix
    :remove deleted on the page showing, not the bookmark's own page

    : a silent 404, or the copy of the same address that was here. Failures now say so, and the toast is no longer in Dutch.

  • Fix
    :save saved while typing

    , so :save my stored three searches and :saved saved one too. It saves on Enter, names the search it will save, and never saves the command text.

  • Fix
    swiping sideways changed the dashboard page from every view

    , a slider in Config included. It works on the bookmarks view only, and not from a form control or during a drag.

  • Fix
    a network error counted against a push subscription

    , so a burst of alerts during an outage removed every device. Only an answer from the push service counts now.

  • Fix
    smaller things

    The mobile search box takes pastes, swipe-typed words and corrections whole; Ctrl/Cmd+Enter on a result opens a new tab; ? on AZERTY opens finders instead of Move; a failed What's New load no longer leaves it dead; a slow What's New no longer writes into another dialog.

Widgets, feeds and previews

  • New
    custom widget percentages say their scale

    "Show as" offers Percentage (0–100) and Percentage from a share (0–1). The old guess read every value from 0 to 1 as a share, so 0.8% showed as 80%; fields saved before keep that guess as Percentage (guessed) until changed.

  • Fix
    every re-read of a preview dropped its pictures

    The carry-over looked in a cache no caller filled; it reads the stored preview now, so a refresh, an expiry or a keyword round keeps a picture whose address did not change.

  • Fix
    the picture downloader wrote back a stale copy of the whole preview

    , undoing "Clear suggested words" and a refresh's new title, and batch rounds dropped pictures stored while they ran. Only the picture fields are written, and a stored picture stands.

  • Fix
    RSS 1.0 (RDF) feeds had no items

    , in the RSS tile, Fresh (which retired them) and the sources; dc:date is read too.

  • Fix
    a calendar event with an e-mail reminder showed as "Alarm notification"

    Properties of nested components are ignored.

  • Fix
    smaller things

    Polled tiles and the weather tile fetch afresh on each beat; disk names follow the request; all-day events last their whole day west of UTC and DURATION events stay while they run; floating and Windows-named calendar times are read in the server's zone and the right zone; the trash and duplicates tiles follow deletes on the dashboard; "Image" turned back on in the card fetches pictures again; long widget titles are cut on a character; mount points with spaces are offered unescaped; feed dates in common variants and US zones are read, and feed previews show Atom text and no raw HTML entities.

Data and backups

  • Fix
    backups left out the Containers view's held and skipped images and its GitHub token

    docker-updates.json is now carried, and an older archive without it leaves the current one in place. docker-secrets.json is carried as a credential: it is left out with leave out credentials and restored at 0600. The timeline, update history, disk sizes and logs stay out on purpose, because they belong to the host. The four hand-kept lists in backup.go are now one register, dataFiles, with a policy per file. TestEveryDataFileHasABackupPolicy fails for any file written to the data directory that the register does not know.

  • Fix
    a move or merge could lose rows on a full disk

    Pages were written in map order and the write stopped at the first failure, so the source could be emptied before the target failed. Pages that gain rows are now written first: a failure leaves a duplicate, not a loss.

  • Fix
    a restore or import on a full disk left half the archive and half the old data

    Every file is now written beside its destination first, and only renamed into place once all of them are on disk.

  • Fix
    restoring the oldest automatic backup deleted it

    The safety copy taken before a restore or import no longer prunes the rotation; the next scheduled backup does.

  • Fix
    a CSV import or a trash restore could give two pages the same shortcut, after which both refused every save

    A shortcut already taken elsewhere is let go; an import to a page that does not exist is refused.

  • Fix
    the container chowned only /app/data

    A data folder set with NEXTDASH_DATA_DIR (which failed the start-up write check and restarted in a loop) and the NEXTDASH_AUTO_BACKUP_DIR folder (every backup failed) are now given to the app's user too.

  • Fix
    smaller things

    "Detect redirect" and the Sources widget work with a write token; a settings save keeps the preview-image migration marker, so restarts no longer rewrite every page; a config change from another tab during a refresh is no longer lost; the save on tab close fits the keepalive limit; a webhook retry keeps its message id; icons are written atomically.

Security (write token)

  • Fix
    without the token, GET /api/settings still returned the private calendar address, and the blocks route an RSS widget's feed addresses

    Both are withheld now; a save that comes back without the feeds keeps the stored ones.

Docs

  • Docs
    static/data/whats-new/v1.15.8.json and its index entry

    , leading the What's new window; whats-new-stub.js moves DASHBOARD_RELEASE to v1.15.8 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v312. Config → Overview names the self-hosted guide, opening Help → Containers. go generate refreshed asset_hashes_gen.go.

  • Docs
    the changelog is split in two

    CHANGELOG.md holds the releases since v1.0.0; the calendar-numbered releases up to v2026.09.09.3 moved to CHANGELOG-ARCHIVE.md, with links between the two. "How releases are numbered" now describes semantic versions.

  • Docs
    README opens with "Run your self-hosted setup from one screen"

    , between the intro and the screenshots: containers, bookmarks, health and alerts and push in four steps, nightly updates with a rollback, the Disk tab and the homelab widgets. Two new screenshots sit under it, screenshots/nextdash-containers-health.jpg (grouped by project, the bookmark marks, a failing healthcheck and its timeline) and screenshots/nextdash-containers-updates.jpg (an automatic update rolled back and skipped), made from demo data with a mocked Docker host. The Features section's Containers and your homelab gains three lines on the bookmark link, the shared alerts and updates at night.

  • Docs
    MANUAL gains a Self-hosted guide

    (#self-hosted-guide), unnumbered, between the table of contents and §1, and linked from the resource table and the top of the contents: what it gives you, the set-up in four steps with a compose example, linking web UIs to bookmarks, monitoring them, alerts, push and container notices, updates, Disk and logs, a homelab page, a morning routine and the keys. The chapter numbers and anchors are unchanged.

  • Docs
    MANUAL §7.1 no longer says the Containers view has no key of its own

    : Shift + Y opens it.

  • Docs
    Config → Help → Containers gains "Containers, bookmarks and health together"

    (helpContainersTogetherTitle/Body), after the set-up panel, with Continues in links to Alerts & notifications and Availability & health, and an entry in HELP_JUMP_PANELS.

  • Docs
    Tips gain a group, "Your self-hosted setup"

    : the seven container tips move there from Data in and out and Making it yours, and six are new — monitoring a web UI's bookmark, Runs in, container notices on your phone, holding databases, :docker <name> logs and a homelab page. The nine new strings are in all six languages. go generate refreshed asset_hashes_gen.go.

  • Docs
    MANUAL §19 says what a backup carries for the Containers view

    : the held and skipped images go in, its GitHub token goes with the tokens and passwords, and its timeline, update history, disk sizes and logs stay out.

  • Docs
    Config → Help follows this round's changes

    , in all six languages. Custom widget names Percentage (0–100) and Percentage from a share (0–1), and says an older field keeps Percentage (guessed) until changed; Backups says the Containers view's held and skipped images go in and its timeline, update history and disk sizes stay out; Containers says a failed automatic update sends a notice naming the step.

Tests

  • Tests
    the grid filter test failed in daytime

    It counted every visible row, and the Today collection, which ranks by the hour, showed the new bookmark a second time before 18:00. It now counts the rows outside the smart collections.

  • Tests
    specs that relied on old behaviour

    The trash spec brings a deleted page back from the trash rather than by posting its id again (now refused); the page-delete spec picks new page ids past the trash, as the app does; the grid-shortcut spec runs in "Enter opens" mode, since in instant mode it passed only because of the reopening search. The Go decimals test reads its ratio as a share now that Percentage means 0–100.

  • Tests
    new specs and Go tests for most of the fixes above

    , each checked to fail without its fix; the smaller fixes are covered by the existing specs.

Only docs and tests changed in this release.

September 2026

v1.15.7 The Containers tour catches up with v1.15.6 and is shown once more, the Bookmarks view's selection gets the bar Inbox and Containers have, and a bug hunt across the app fixes more than a hundred bugs — several of which lost bookmarks, widgets or settings. +1 32 fix

The Containers tour catches up with v1.15.6 and is shown once more, the Bookmarks view's selection gets the bar Inbox and Containers have, and a bug hunt across the app fixes more than a hundred bugs — several of which lost bookmarks, widgets or settings.

Bookmarks

  • Fix
    ticking rows opened the side panel, and there was no selection bar

    A tick counted as a click on the row, which opens the panel, and two or more ticked rows always opened the bulk form there. Ticking now only selects: a selection bar above the list — the shared multi-select toolbar Inbox and Containers use — counts what is ticked and offers Edit…, Re-check, Mute alerts, Export CSV, Delete and Clear selection. Edit… opens the form in the side panel (one ticked row opens its own panel). The side panel still opens for a bookmark you click. syncLibraryDrawer opens the bulk form only when _bmBulkPanelWanted is set.

Everywhere

  • Fix
    the Inbox selection bar's Delete deleted nothing, and a confirm dismissed with Escape never answered

    AppModal ran a caller's onHide before the button's own handler, so a confirm settled on "no" before it heard Delete, and Escape or the backdrop left confirm()/alert() pending — a Health row waiting on one stayed busy until a reload. A button's handler now runs first and onHide is told the reason (confirm, cancel, dismiss, replaced); the tours no longer report "dismissed" at step 1.

Dashboard

  • Fix
    a bulk move could lose rows

    A selection with rows from the target page and from other pages dropped the other pages' rows from both; copies of one URL now move in a stable order.

  • Fix
    moving a bookmark with a shortcut to another page always failed

    , and a move could put the same URL on one page twice (AddBookmark).

  • Fix
    an add to a page that does not exist was stored

    POST /api/bookmarks/add took any page id, so a move there removed the bookmark from its own page and left it where nothing shows it. It now answers 404, as the bulk move already did; Unsorted still takes adds.

  • Fix
    undo after a page switch put bookmarks on the wrong page

    The single and multi-select delete undo, the category-move undo and the category-delete undo restore where the rows came from; a failed multi-select undo no longer empties their trash entries.

  • Fix
    a failed blocks fetch on a page switch let an edit write one page's widgets over another's

    The widgets on screen still stay, but a widget edit or a block move on the new page is refused until its own blocks have loaded.

  • Fix
    saves that were dropped

    A category rename after a same-page reload, a block move within a second of leaving the page or closing the tab, and a second drag while the first was saving are kept; a reorder save no longer waits on itself. A deleted page comes back from the trash with its widgets.

  • Fix
    Other went to the top of the page

    Bookmarks without a category (or with one that no longer exists) jumped above every category once a block order was stored; they are at the end again, as the manual says.

  • Fix
    smaller things

    A page with only widgets draws them; Shift+F matches URLs and tags; the page-tab colour goes back on Escape; an older page load no longer lands after a newer one; opens are counted on the bookmark by URL.

Containers

  • New
    the Containers tour covers v1.15.6, and runs once more for everyone

    Three new steps — your columns and order, a web UI and its bookmark, updates at night with a rollback and notices when a container runs hot — and the side panel, Disk and Config steps brought up to date: thirteen steps instead of ten. The tip id moves to containersTutorialV2 (in the tour, the view, the replay lists in Config and search, and the e2e helpers), so the tour opens again on the next visit. Whoever took the earlier tour is told on the first step that it is an update with new features, and the new or changed steps carry a New mark; a first-time reader gets the plain tour.

  • Fix
    automatic updates

    A stopped container is updated and left stopped instead of being rolled back every night; a rollback starts the old version; a stop or restart from the view during the watch is left alone; each container gets its own time, is marked as tried only once it was, and waits for a running prune.

  • Fix
    updates and checks

    A VPN client (network_mode: container:) can be updated; an image with two digests for one repo reads current; a check that runs out of time keeps what was known; size measuring backs off after a failure; very long log lines arrive whole; the widget counts incidents of listed containers only.

  • Fix
    the view

    The arrows and Shift ranges follow grouped rows, Resources keeps one stats call in flight, and the "+N" ports list survives a refresh.

Config

  • Fix
    a move made the category on the target page under its raw id

    , CSV export wrote category ids that the import read back as names, and an import made a second category beside one with the same name.

  • Fix
    Enter in the right-click menu ran the item the arrows had reached

    , not the one under the pointer — a Delete, one wrap up.

  • Fix
    a new page took the id of a page in the trash

    , so that page could no longer be restored.

  • Fix
    a refused import still wrote a safety backup and pruned the rotation

    ; an archive with bookmarks-0.json is refused instead of removing every page; the HTML bookmark import takes files over 4 MB.

  • Fix
    smaller things

    Save a copy now no longer reports a failure; a failed reset no longer leaves the overlay up; Density applies without a reload; settings saves are sent one after another; the auto-backup and log panels read back after the save; a stale category-editor or news answer is ignored; cross-tab sync keeps an event that arrives mid-refresh; the Stats tabs bind once; Appearance's intro shows once; deleting the active custom theme applies the default; the Brave finder seed no longer turns default-on settings off; a fresh install has a stale limit of 50.

Inbox

  • Fix
    an import into a nearly full inbox pushed out older links

    It now stops at the cap.

  • Fix
    triage

    Keys in the snooze menu no longer act on the card behind it, and a card is removed by id after an action that awaited the network.

  • Fix
    undo

    Undo of Keep restores the entry itself (its id, date and read state); bulk-keep undo brings back every link and leaves a copy that was already kept; undo of a delete drops an icon file that went with it and reports a link it pushed out.

  • Fix
    smaller things

    A list read no longer undoes a delete made while it loaded; snoozed links wake with an empty list; Oldest first orders the date groups; the groups survive the clock change; bulk Open marks only the tabs that opened as read; d and Shift+K act once per row; the promote menu closes on Escape; shared links get a preview and count as added; a batch delete writes the stats once.

Health

  • Fix
    cancelling Retest all marked every remaining bookmark broken

    , and a run over 60 s reported failure.

  • Fix
    alerts

    Samples inside a maintenance window no longer alert; "alert after 1 failure" alerts once; a certificate rollout no longer re-alerts.

  • Fix
    the same URL on two pages with different rules was checked once, with the first bookmark's rules

    A copy with other rules is checked by its own in the same round; history, alerts and certificates stay per URL.

  • Fix
    smaller things

    Errors are classified by their cause, not by the URL; a re-check the dashboard could not run records nothing; the per-day bars are labelled in UTC.

Search

  • Fix
    a deep link with % in the URL failed the dashboard load

    Also: one Enter on mobile ran a match twice; ? with no finders opened nothing; :__proto__ threw; $ in a query was read as a pattern; * and / pressed before the search bundle loaded opened the wrong thing; blocked site data stopped the start-up.

Widgets and feeds

  • Fix
    a feed retired after five failures was never polled again

    It is tried again a day later. Atom entries with several links and feeds in ISO-8859-1 or windows-1252 are read; summaries are cut on a character.

  • Fix
    Mastodon and Hacker News imports skipped links saved since the last round

    , and a new handle kept the old cursor.

  • Fix
    smaller things

    Favicon fetches use the page's declared icon; oEmbed thumbnails are downloaded; cached previews are answered without the rate limit; an edited custom widget answers with its new config; all-day calendar events keep their day; CPU no longer counts guest time twice; a failed update check is retried after 15 minutes.

Security

  • Fix
    with a write token set, GET /api/settings returned stored keys and tokens, and GET /api/logs answered without the token

    Both are fixed, and the app reads them with the token. Logs → Download works with a token, and editing a widget no longer wipes a custom widget's address and credential.

  • Fix
    webhooks and push

    New webhook keys are whsec_ keys the Standard Webhooks libraries verify (older hex keys keep working); webhooks have their own outbound budget; an alert too long for a push message is shortened instead of removing every device.

Docs

  • Docs
    MANUAL §11.4 describes the selection bar

    The tour's new texts are in all six languages.

  • Docs
    MANUAL brought up to date with the fixes

    : §12.2 (the same address on two pages), §12.5 (maintenance and alerts), §13 (import stops at a full inbox), §14.5 (automatic updates of stopped containers, and after a rollback), §23.2 (what the write token keeps back).

  • Docs
    MANUAL §19.3 describes whsec_ webhook keys

    The five new messages from the fixes are in all six languages.

  • Docs
    static/data/whats-new/v1.15.7.json and its index entry

    , leading the What's new window; whats-new-stub.js moves DASHBOARD_RELEASE to v1.15.7 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v311. Config → Overview names the Bookmarks selection bar. go generate refreshed asset_hashes_gen.go.

Tests

  • Fix
    the Go preview tests failed about one run in three

    The refresh tests walk the default bookmarks, which are real sites, and each queued a background picture download; the preview media worker finished seconds later and stored the file in whichever test's data directory was current by then, so the orphan sweep and file-count tests found one file too many. queuePreviewMediaFetch now honours NEXTDASH_DISABLE_PREFETCH, the brake enrichInboxPreviewAsync already has, which the Go suite and the e2e server both set. Covered by TestQueuePreviewMediaFetchHonoursTheBrake.

  • Tests
    most of the fixes above come with a test that fails without them

    ; the rest were small enough to verify by reading the change.

  • Tests
    four specs caught up with the fixes above

    The server-log spec reads /api/logs with the token and no longer expects line 1 after a clear (the count goes on); the webhook spec expects a whsec_ key; Density left the list of settings that need a reload; and docker_logstream.go is gofmt-clean, which the CI's fmt-check wanted.

  • Tests
    the reduced-motion move test measured a whole move

    It sent the bookmark to page 0, which failed only because of the shortcut bug fixed above; now that the move goes through, the time included the refresh after it and ran over on a slow runner. The test refuses the write in the page and times the pause before it.

  • Tests
    the preview sweep's Stop test failed on CI and proved nothing

    The previews were answered at once, so on a slow runner the three rows were done and the bar closed before the click, which then waited on a hidden Stop; and a Stop that did nothing passed too. The answers now take 800 ms, the side panel's own requests are left out of the count, and the test checks that no row is asked for after Stop.

Only docs and tests changed in this release.

v1.15.6 The Containers view grows up: choose your columns, see a web UI's bookmark and its health, get told when a container runs hot, let updates run at night with a rollback, and measure what Unraid's appdata takes. +10 5 fix

The Containers view grows up: choose your columns, see a web UI's bookmark and its health, get told when a container runs hot, let updates run at night with a rollback, and measure what Unraid's appdata takes. It leads the What's new window.

Containers

  • New
    automatic updates

    A switch in a container's Updates section, or Update automatically in the selection bar, lets nextDash update it in a nightly window (Config → Containers → Updates, 03:00–05:00 at first). One container at a time, only what the last check found, never a skipped or held version or nextDash's own. Each update is watched for five minutes; a container that stops, restarts on its own or turns unhealthy is rolled back and the version skipped. Updates, rollbacks and failures send a notice. New docker_auto_update.go.

  • New
    a web UI's bookmark

    A bookmark mark follows a container's web UI link in the colour of the bookmark's checks; a click opens the bookmark in the Bookmarks view, its row in view and in focus, on Details. It is found by hand (the side panel's new Bookmark section), else by the same port on this server, a subdomain named after the container, or its title — and not guessed between two. The bookmark's Details say Runs in back. Chosen links are kept in dockerBookmarkLinks.

  • New
    notices when a container runs hot

    Above 90 % CPU of every core or 90 % memory of its limit for 10 minutes (each adjustable in Config → Containers → Notifications), and when it is back under. Reads the stats history. New docker_usage_alerts.go.

  • New
    Columns

    Show or hide Image, Status, CPU, RAM, Size, Restarts, Web UI and Ports; remembered with the view. Restarts (off at first) counts starts again in the last 24 hours, from the timeline.

  • New
    sort by size and restarts

    , from the headings and the sort menu.

  • New
    group by network or by image

    , beside project and status.

  • New
    network and disk I/O

    in Resources: in/out and read/written now, and two more charts of the last hour.

  • New
    Disk: remove stopped containers

    in one go, after naming them; volumes and images stay, hidden ones and nextDash's own are left.

  • New
    Disk: measure a bind mount's folder

    A short-lived alpine container mounts it read-only with no network and runs du; only folders a container mounts can be measured. New POST /api/docker/binds/measure.

  • New
    an ℹ in the header

    explains the view, as Bookmarks and Inbox have.

  • Fix
    a followed container log stayed silent in the browser

    The gzip middleware asserted http.Flusher on the request log's recorder, which only has Unwrap, so nothing was flushed until 4 KB had piled up. It now flushes through http.ResponseController.

  • Fix
    the side panel's Volumes and Health were hard to read

    A mount shows where it appears in the container, with where it comes from under it and tags for its kind and read-only; the health check sits in its own block, and each last check is a mark and a time in one column.

Bookmarks

  • Fix
    a bookmark further down than the first page lost its cursor

    when opened from elsewhere; the list is drawn down to it and scrolled to it.

  • Fix
    after closing the side panel with the mouse, the page would not scroll

    until Escape: the row stayed the cursor and kept Space and the arrow keys. Closed with the mouse it lets go; closed with Escape or i it stays.

What's new

  • Fix
    Support and Esc sit in the header's right corner

Tests

  • Fix
    the update-status fixture let a test end mid-fetch without failing it

Docs

  • Docs
    MANUAL §11.3 and §14, Config → Help and four new tips describe all of the above, in six languages; README's Containers caption too

    static/data/whats-new/v1.15.6.json, its index entry and two Overview entries (the bookmark link and automatic updates); whats-new-stub.js moves DASHBOARD_RELEASE to v1.15.6 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v310.

Only docs and tests changed in this release.

v1.15.5 A tidier Containers table, and the host folders containers keep their data in. +3 2 fix

A tidier Containers table, and the host folders containers keep their data in. It leads the What's new window.

Containers

  • New
    Disk lists bind mounts

    Under Volumes, Bind mounts names each host folder containers mount and who mounts it where (sonarr → /config). On Unraid that is where container data lives, so the Volumes list there is mostly anonymous leftovers. Docker neither measures nor removes a folder, so the list has no size and no Remove…; the Docker socket and host files such as /etc/localtime are left out. /api/docker/disk carries them as binds.

  • New
    three ports in a row, the rest behind +N

    A container that publishes many ports kept its row wide; the rest now open in a popover with the port inside the container and tcp or udp. A port published for both counts once in the row.

  • Fix
    an update is an arrow before the name

    The orange update pill after the name broke the names' left edge and wrapped long ones; an orange ↑ in front of the name says the same, with Update available on hover.

  • Fix
    names and images on one line

    Both are cut short with the whole text on hover, and the image drops its registry host and a :latest tag: lscr.io/linuxserver/sonarr:latest reads linuxserver/sonarr.

  • New
    a group band counts its containers

    (Updates · 9).

Tests

  • Fix
    no "is available" toast in a run older than the latest release

    A rerun of a commit made before v1.15.4 shipped got the update toast in #app-notification, where specs wait for their own message. tests/fixtures.js now answers /api/update-status with no update unless a spec routes it itself.

Docs

  • Docs
    MANUAL §14.2 and §14.7, and Config → Help → Containers, describe the arrow, the short image, the band count, +N and bind mounts, in all six languages

    static/data/whats-new/v1.15.5.json, its index entry and an Overview entry for bind mounts; whats-new-stub.js moves DASHBOARD_RELEASE to v1.15.5 and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v309.

Only docs and tests changed in this release.

v1.15.4 One fix for the Containers table, held back from the What's new window (hideFromModal) like v1.15.1, so v1.15.3 keeps leading it. 1 fix

One fix for the Containers table, held back from the What's new window (hideFromModal) like v1.15.1, so v1.15.3 keeps leading it.

Containers

  • Fix
    a group band in the Containers table stopped short of the Ports column

    Grouped by project or status, the band's cell spanned a fixed 7 (or 5) columns; the Size column made it 8, so the top-right corner over Ports was left empty. It now spans as many columns as the heading row has. A new test in docker-table-headers.spec.js fails on the old span.

Docs

  • Docs
    static/data/whats-new/v1.15.4.json and its index entry, held back from the modal

    whats-new-stub.js moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v308; DASHBOARD_RELEASE stays on v1.15.3. tests/whats-new-hidden-release.spec.js lists v1.15.4 with v1.15.1 as held back. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.15.3 A Containers follow-up: a Size column, removing several containers at once (running ones stopped first, from the bar, ⌫ or a right-click on the ticked rows), ⌫ in place of a Delete key many keyboards lack, and port links that go to the right server — a note while no Docker host address is set, and an example and a live check on that setting. +4 1 fix

A Containers follow-up: a Size column, removing several containers at once (running ones stopped first, from the bar, ⌫ or a right-click on the ticked rows), ⌫ in place of a Delete key many keyboards lack, and port links that go to the right server — a note while no Docker host address is set, and an example and a live check on that setting. Announced in the What's new window.

Containers

  • New
    Config → Containers → Links says how to write the host address

    The note gives the format (the server's LAN address or name, no http://, no port) with an example — 192.168.1.10 or tower.local, so port 8080 opens http://192.168.1.10:8080 — and the field's placeholder is that example instead of the current host. A line under the field checks it as it is typed: ✓ with the address port 8080 would open, the host that will be saved when a full http://…:8080 is pasted (it is cut to its host on save — the server keeps a bare host only and used to drop anything else without a word), or Not an address. New: config-docker-host-check.spec.js.

  • New
    a note while no Docker host address is set

    Without one, a port or [IP] link uses the host the page was opened on; through a reverse proxy that is the proxy's domain, and dash.example.com:8080 goes nowhere. The page cannot tell which case it is in, so while the address is empty and the table has such a link, the view says where port links point, with Set host address (Config → Containers, the field focused) and Dismiss (remembered in this browser). New: docker-host-hint.spec.js.

  • New
    a Size column and the size in the side panel

    Each row shows what the container wrote (its writable layer), with the size including its image on hover — the two figures docker ps -s gives — and the side panel names both under Details and the written size under Resources. The daemon takes seconds to work them out on a big host, so the list never asks: docker_sizes.go keeps the last measurement by container id and starts a new one in the background when it is over half an hour old, and the Disk tab's /system/df read refreshes it too. A container not measured yet reads —. The column goes with CPU and RAM below 900 pixels. New: docker-sizes.spec.js, TestDockerSizeOfMeasuresInTheBackground.

  • New
    remove ticked containers in one go, running ones included

    The selection bar gains Remove: it asks once with the names, says which still run, stops those first (the daemon refuses to remove a running container) and ends with N removed. With containers ticked, ⌫ or Delete does the same, and a right-click on one of the ticked rows opens a menu with the bar's actions for all of them. A single running container's Remove (menu or ⌫) takes the same stop-first route. New specs in docker-bulk-select.spec.js.

  • Fix
    ⌫ removes, and the legend says so

    A Mac's delete key sends Backspace, which already removed the selected container, but the legend, the row menu and the cheat sheet named Del, a key many keyboards lack; they now show ⌫. Pressing it on a running container used to do nothing at all; it now offers to stop and remove it. Help, the tour and MANUAL §14.2 and §14.4 follow, in all six languages.

Docs

  • Docs
    Config → Help → Containers follows

    The Containers view says Remove stops running ones first and that a right-click on a ticked row and ⌫ do the same; Setting it up gains a Links paragraph: the host address format with an example, the live check and the note in the view. All six languages.

  • Docs
    static/data/whats-new/v1.15.3.json and its index entry, and one Overview feature

    whats-new-stub.js moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v307 and DASHBOARD_RELEASE to v1.15.3. Config → Overview and About → News & features gain What each container takes on disk (since: v1.15.3, in all six languages); README's Containers line names the size. tests/whats-new-hidden-release.spec.js follows the new lead. go generate refreshed asset_hashes_gen.go.

  • Docs
    the manual, Help and translations follow the Containers changes

    MANUAL §14.2 (Size, ticking and removing, the host address note) and §14.4 (⌫ / Delete, removing the ticked ones); Config → Help → Containers (Size, removing several, ⌫); the cheat sheet row and the tour step name ⌫ instead of Delete. The new keys (dockerColSize, dockerFieldSize, dockerSizeTitle, dockerConfirmBulkRemove*, dockerBulkRemoved, dockerHostHint*) are in all six languages.

Only docs and tests changed in this release.

v1.15.2 The Containers view's big round: a live logs window, a Disk tab, notices when a container goes down, a timeline and health checks per container, skip, hold and rollback for updates, CPU and RAM columns, compose stacks and ticked containers acted on as one, and the analytics that go with them. +26 61 fix

The Containers view's big round: a live logs window, a Disk tab, notices when a container goes down, a timeline and health checks per container, skip, hold and rollback for updates, CPU and RAM columns, compose stacks and ticked containers acted on as one, and the analytics that go with them. The Bookmarks and Inbox views get sortable column headings, a string of settings, backup and listener fixes lands everywhere, and the docs and translations catch up. Announced in the What's new window.

Everywhere

  • New
    the category sort menu says what each sort does

    The ⋯ in a category header listed Rec and Top; it now reads Manual, A–Z, Last opened, Newest and Most opened, and only the chip in front of it keeps the short name. A new spec, dashboard-category-sort-usage.spec.js, checks the order Last opened and Most opened give, never-opened bookmarks last.

  • Fix
    the Inbox key legend named keys that did nothing

    It always listed Shift + K, which only keeps a link while Unsorted is on, and called a double click open even with the double-click setting on note. The legend now follows both.

  • Fix
    suggested tags were read out as a bare name and "×"

    The chips under the tags field (bookmark form, inbox, Config → Bookmarks) now carry the same labels as their tooltips: Tag this bookmark #… and Stop proposing #… here.

  • Fix
    the tag cloud's close button had no name until the modal first opened

    It now has a static aria-label, translated on open.

  • Fix
    the analytics notice could pass markup through

    Its escape helper fell back to returning the text as it was; it and the stat tile now use the shared escape-html.js. A new spec, shared-escape-callers.spec.js, checks that markup arrives as text.

  • Fix
    Config's status tiles, danger panel and setting swatches ignored the theme

    Hard-coded colours in config-view.css and setting-art.css are now the theme's success, warning and error tokens and a mix of its background; the six theme plates keep their own colours on purpose.

  • Fix
    preview card images load lazily and decode off the main thread

    The favicon, the video poster and the link-preview image in the bookmark form gained loading="lazy" and decoding="async", as the card's main image already had.

  • Fix
    one formatBytes instead of three

    Widgets, Config and the mount picker each had their own; they now share shared/format-bytes.js, each keeping its wording through an option.

  • Fix
    a Bookmarks view link kept the reader's last sort and group

    Absent keys in #bookmarks?… cleared the filters but not the sort or group, so following a link, or going Back to one, kept the order you had and then wrote it into the address. Absent now means the default, as the address is written; an unknown sort is ignored.

  • Fix
    with the inbox rail folded, every visit left a document listener behind

    Its outside-click handler was added on each mount and never removed, each holding the old view. It is now removed when the view closes and before a new one is added.

  • Fix
    every Appearance repaint left a document listener behind

    The theme picker's outside-click handler was added on each bind and never removed, so old ones held their detached lists, and one bound while the list was open could revert the theme preview on every later click. The previous handler is now removed first.

  • Fix
    the inbox's bulk Promote menu could list one page's categories under another

    Choosing page A, going back and choosing B let A's categories, arriving late, be added under B's heading, so a click promoted to A. A late answer for a step no longer showing is now dropped.

  • Fix
    duplicating a page could make an empty copy and call it a success

    A failed read of the source's bookmarks or categories counted as none, and a failed category save let the copied bookmarks point at categories the new page did not have. Either now stops the copy with an error.

  • Fix
    an inbox tag filter stayed in the address after going back to a page

    Leaving the inbox removed its keys from the address by name, and ib_tag was not on the list, so a reload brought the tag back and it outranked the stored filter and sort. Every ib_ and hv_ key now goes, by prefix.

  • Fix
    the server log could show lines that did not match the filter, or the same lines twice

    A poll that landed after the search changed was appended to the filtered list, and on a slow server two polls asked from the same position. Only the newest read's answer is used now, and a poll waits while one is on its way.

  • Fix
    clicking a category in Statistics → Collection opened an empty Bookmarks list

    The row passed the category's name as the filter, but bookmarks carry the category's id; it now passes the page-and-id key, and no longer also types the name into the search.

  • Fix
    three things in the Containers side panel

    After a refused or failed action the list was re-read but the side panel kept the old state; it now refreshes too. The CPU and memory figures polled the daemon every two seconds even with the tab hidden; they now wait until it is visible. And their labels, CPU and Memory, now go through the translations.

  • Fix
    the Container list widget opened http://[IP]:…, and a non-web address from a label reached the browser

    The widget used the raw web UI address; it now fills [IP] as the table does. And webuiHref(), which every web UI link goes through (table, side panel, row menu, search, widget), now returns nothing for an address that is not http(s)://, so a javascript: label set by an image is never opened.

  • Fix
    the update badge could come back right after an update

    An update check reads the image states, asks the registries, then writes them all back; an update or rollback that finished in between was overwritten by the older reading, and the badge stayed until the next check. An entry newer than the check's start is now kept.

  • Fix
    a stop, restart or remove could slip into a running container update

    Actions were locked by container id, but they resolve the container by name, and an update moves the name to a new id halfway; a second tab could then act on the half-made new container. The lock now holds the name as well.

  • Fix
    a failed container update could leave the old container stopped and renamed

    The rollback ran on the update's ten-minute budget, so an update that spent it on the pull failed its rollback too; and a new container already removed (from another tab) made the rollback stop before it restored the old one. The rollback now has two minutes of its own and treats a 404 on removing the new container as done.

  • Fix
    two settings saves at once could drop one of them

    A settings POST, a favicon or font upload and the archive-key save each read the settings, changed their field and wrote the whole struct back; two at once started from the same snapshot and the second erased the first's change. Each read-change-write now runs under one lock.

  • Fix
    restoring a backup could leave torn or mixed data

    Each file was written straight over the live one, so a crash or a full disk mid-restore left half a JSON file, and a bookmark click during the restore could write its page back over the restored one. Files now go through the atomic writer (which also puts back 0600 on an existing secret file), all under the store lock.

  • Fix
    a maintenance window whose days were all invalid silenced alerts every day

    Out-of-range days were dropped, and a window left with no days reads as every day; such a window is now dropped instead.

  • Fix
    posting a settings file from another instance reset depth, glow and effects to follow

    SaveSettings kept every one-time migration marker a save left out except surfaceFollowMigrated, so the next read ran that pass again over the forced look.

  • Fix
    the activity log kept one backup fewer than set

    Rotation moved .1 onto .2 before .2 had moved on, so .3 never existed and a rotation's worth of history was lost each time; the shift now runs oldest first.

  • Fix
    Remember scroll position and soft 404 detection were off on installs from before 17 August

    Both default on, but a settings file written before they existed read as off; an absent key now means on, as it does for the other default-on switches.

  • Docs
    Help and the manual describe the sortable column headings

    Config → Help (Bookmarks view → the list, Inbox → working the list, in all six languages) and MANUAL §11.2, §11.13 and §13: which headings sort and in what order, the arrow, that Sort follows, and the rev= and ib_dir address keys.

  • Fix
    seven more places no longer report a failed settings save as done

    saveSettings() resolves false on a failed save rather than rejecting, and resetting onboarding, bringing a tour back, a choice in the changes tour, the Shift+Q search mode, the ask-again for browser notifications, the date-and-weather card and the feeds switch in the fresh tutorial each ignored that answer: they said the change was made, or kept it on screen, beside the save error. Each now checks the answer.

  • Fix
    restoring a bookmark from the trash keeps its page free of duplicates

    A page holds each address once, as a save insists, but a restore put the bookmark back even when the address had been added again since: it is now refused and the item stays in the trash. A shortcut taken since is let go, and the bookmark comes back without it. TestRestoreTrashItemKeepsThePageFreeOfDuplicates fails on the old code.

  • Fix
    the Go tests are race-clean again

    go test -race./... failed four tests on races in shared state: the activity log's config and its test override were read without a lock while a save or a test replaced them, and every set of handlers rewired the Containers view's settings source. Both now sit behind atomic pointers.

  • New
    every column heading in the Bookmarks view sorts

    Tags (A to Z by the first tag, untagged last), Shortcut (the keyed ones first), Usage (the most opens in the sparkline's window first) and Score (the worst first, now without a Health filter too) join Name, Pinned, Opens, Last opened and Added; the toolbar's Sort offers the same four. The labels reuse the column names, so no new strings.

  • New
    analytics, when switched on, also reports how widgets, the Containers view, Health, Inbox and the Bookmarks view are used

    Three more once-per-load events beside the settings and content snapshots: widgets-snapshot (how many widgets of each type), containers-snapshot (which Containers options are on, whether a socket and control are configured, and counts of hidden containers, custom addresses and waiting updates) and views-snapshot (Health's checked, down and certificate counts and the age of the last check; Inbox's unread, snoozed and noted counts and which of the known sources were ever used; the layout options chosen for Inbox and the Bookmarks view). The server counts them, only when analytics is on and cached for ten minutes like the content counts, dropped on a settings save; the browser buckets every count before it leaves. Nothing names anything: no container, image or widget names, no addresses, and Docker itself is never asked. The privacy text and the manual's table say so; the new sentence is English in the other five languages until the next docs round.

  • New
    the column headings in the Bookmarks and Inbox views sort the list

    A click sorts by that column in the order it reads naturally (names A to Z, counts and dates the highest first, the worst score first), a second click turns it round, and the toolbar's Sort follows; picking from the toolbar starts afresh in the natural order. An arrow on the heading says which way the list runs. Bookmarks sorts on Name, Pinned, Opens, Last opened, Added, and Score while a Health filter is on; a turned-round sort rides in the address as rev=1. Inbox sorts on Title and Site, a second click reversing them (ib_dir=desc, kept like the sort), and Added switches between newest and oldest first; under Snoozed, which keeps its wake order, the headings stay text.

  • Fix
    the header hid its Bookmarks, Inbox, Containers and Config buttons at some window widths with room to spare

    fitHeaderZones() measured the clock by the box it is drawn in, and that box is the row's 1fr track, stretched over whatever the other zones leave, so the sum always came to exactly the row's width and a fraction of a pixel decided: 1440px hid the buttons, 1452px kept them. Each zone is now measured at its content width (max-content, for the measurement only), with a pixel of slack for fractional widths. A new spec walks the window from 1100px to 1700px and fails on the old code at a dozen widths. The same comment block, pasted three times in that function, is down to one.

  • New
    the Bookmarks and Inbox views name their columns, as the Containers view does

    One shared style, .lvs-colhead in list-view-shell.css: the group heads' uppercase caption in the theme's own text, surface and rule colours, pinned under the view's header while the list scrolls, and gone at phone width. Bookmarks lays its headings on the rows' own grid from the same column choices (View → Columns shown) and the same cell classes, so a heading stands over its column at every width; it sits outside #config-bm-list, so the virtual window and the row queries never see it. Inbox shows Title, Site (Address when the whole address is shown, none when hidden) and Added. No new strings: every label already existed.

Containers

  • New
    tick containers and act on the lot

    A box in front of each name, x or Space ticks a row, Shift-click, Shift + X or Shift + ↑/↓ a run, and Ctrl/Cmd + A everything the filter shows. The bar above the list starts, stops, restarts, updates or mutes the ticked containers one at a time, with a count, and ends with one notice such as 3 restarted, 1 failed; nextDash's own container is left out, and without actions switched on only muting is offered. Esc clears the ticks first. New spec: docker-bulk-select.spec.js.

  • New
    container actions in analytics

    With analytics on, each action sends one docker-action event: which action, whether it worked, and where it came from (row, side panel, menu, key, command, selection bar), with a bucketed count for a selection. No names, images or addresses. An update the server had to roll back now counts as failed.

  • New
    a custom web UI address shows where you look

    The side panel's head shows the web UI address under the name, tagged Custom when it is one you set (the tag opens the Custom section), and the table's Web UI column puts a dot in front of it.

  • Fix
    the Containers column headings use the shared .lvs-colhead-sort

    as Bookmarks and Inbox do; sort keys and the stored sort are unchanged.

  • Fix
    an update keeps the container's anonymous volumes

    A volume the image declares (VOLUME) and nothing mounts by name is created per container, so the swap gave the new container a fresh, empty one and left the data in a volume nothing used -- which the Disk tab then offered to remove. dockerKeepAnonymousVolumes() mounts the old container's into the new one; binds and named volumes stay as HostConfig has them. A rollback does the same. TestDockerRecreateKeepsAnonymousVolumes fails on the old code.

  • Fix
    an update or rollback refuses what it cannot swap safely, before anything is pulled or stopped

    A container others run inside (network_mode: container:X, a VPN container and its clients) would have left them pointing at a container that no longer exists: refused as network-shared, naming them. One started with --rm would have been removed by its own stop, with nothing to go back to: auto-remove. One made from an image id has no reference to update: pinned-by-id, and the update check no longer asks Docker Hub for library/sha256. Each has its own message. TestDockerRecreateRefusesWhatItCannotSwapSafely fails on the old code.

  • Fix
    nextDash speaks the daemon's minimum API version when its own is too old

    Docker Engine 29.0 to 29.2 refused anything older than 1.44, and nextDash asked for 1.41: every Docker call failed, and the list said the socket was missing. The version is now read once per socket from /version and raised to the daemon's minimum when needed; a daemon that refuses is reported as such, not as a missing socket. TestDockerSpeaksTheDaemonsMinimumVersionWhenOursIsTooOld fails on the old code.

  • Fix
    the Disk tab counts shared layers once

    What an unused image frees is its size less the layers other images keep, the images together take LayersSize, and a shared or in-use build-cache record does not go with a prune -- as docker system df counts. Measured on a real host, the old figure said 396 MB reclaimable where Docker said 168 MB. The Containers tile's reclaimable figure follows. TestDockerDiskCountsSharedLayersOnce fails on the old code.

  • Fix
    a container left behind by its tag offers no skip

    Its newer image is already on the host, so there is no version on offer to skip; the drawer said Skip this version and the server answered nothing-to-skip. The row now carries recreate, the Updates part says the image is here and an update recreates, and Skip is left out. A new spec in docker-updates.spec.js fails on the old code.

  • Fix
    the Containers tile counts updates per container and restarts by uptime

    Updates is counted as the view's badge counts, so a container left behind by its tag counts too; just restarted reads when a container last started (its uptime) rather than when it was created, which a restart does not move and a recreate does. TestDockerMetricsExtras and TestCountContainersReadsRestartsFromUptimeNotCreation fail on the old code.

  • Fix
    Resume in the logs window brings every line since the last one

    The resume asked for the ordinary tail as well, so more lines than that written meanwhile left a silent gap; with since, the tail is what the window keeps, 5,000 lines. TestDockerLogStreamRoute fails on the old code.

  • Fix
    an update refused because a prune is running says so

    , as prune-running (A clean-up on the Disk tab is still running), rather than Another action is still running on this container.

  • Fix
    an env value or log the drawer cannot read says so

    A refused or failed read showed an empty value, dropping its button, and an empty log; the value's button stays with a message, and the log reads The log could not be reached. A new spec in docker-view.spec.js fails on the old code.

  • Fix
    a web UI address the server refuses to save is not kept

    The drawer waited for saveSettings() to throw, but a failed save resolves false; it said Web UI address saved beside the save error. A new spec in docker-custom-webui.spec.js fails on the old code.

  • New
    the Containers and Container list widgets report more

    The Containers tile's figures can add updates waiting, reclaimable disk space and incidents (24 h), and a new Name the three busiest by CPU lists the top three under them. Updates count as the Containers view counts them: DockerMetrics.Updates read the raw check results, so a skipped or held version was still counted, and now reads them with the reader's choices applied. Reclaimable is the last Disk measurement, whoever asked for it; once it is six hours old the tile's next read starts a new one in the background (dockerReclaimable(), one at a time) and shows the old figure meanwhile, or a dash before the first. Incidents are the timeline's crashes and turns unhealthy of the last day; the busiest come from the stats sampler. Nothing ticked still means every figure, so the three new ones appear for anyone who never chose, and nine figures lay out three abreast. The Container list sorts by CPU or memory, busiest first, and can show CPU and memory beside the name — with three rows, a top three. widgetFields accepts the new choices; MANUAL §15 and Help say so; locale keys in English outside en until the next docs round.

  • New
    a compose project updates as one stack

    Grouped by project, the project's row gains Update (n) beside Start, Stop and Restart: n is how many containers in the stack have an update waiting, and only those are updated — a skipped or held version, an image no check has looked at and nextDash's own container stay as they are. The selection bar's runBulk() asks once, naming them, and updates them one at a time; a filter or search narrows the stack as it does for the other stack buttons. Disabled when nothing waits, absent read-only. MANUAL §14.2 and Help say so; one new locale key, in English outside en until the next docs round.

  • Fix
    an update no longer carries the old image's defaults into the new container

    Docker folds an image's Env, Cmd, Entrypoint, working directory, user, healthcheck, labels, exposed ports and volumes into a container's Config when it is made, and inspect hands them back merged; recreate sent them back as they were, so a new version with a new PATH, entrypoint or healthcheck started with the old one's. dropImageDefaults() in docker_recreate.go now leaves out what equals the old image's value, so the new image fills it in; what was set for the container stays, and an entrypoint of its own keeps its command. A rollback benefits the same way. TestDockerRecreateLeavesImageDefaultsToTheNewImage fails on the old code.

  • Fix
    a container left behind by its tag shows its update

    After one of two containers on the same image was updated, or after docker compose pull without up, or after a failed update that had already pulled, the daemon lists the container by image id: the table showed sha256:…, the check answered unknown, and the badge was gone although the container ran an older image. The list now takes the reference from the container's own Config for those rows, and a container that runs an older image than its tag points at shows an update (held stays held), which a click installs with a recreate alone. One /images/json per list read. TestDockerContainerLeftBehindByItsTagShowsAnUpdate fails on the old code.

  • Fix
    a failed list read keeps the containers table

    A poll or the refresh after an action that could not read the list (a timeout, a restart, the daemon answering not available) emptied the table, set the header badge to 0 and closed the side panel of a container that was still there; the last list now stays. Only the newest read is applied, and a poll waits for the one still on its way. A new spec in docker-view.spec.js fails on the old code.

  • Fix
    a port bound to 127.0.0.1 or ::1 is no web UI

    The Web UI column's fallback and the row menu's Web UI linked the first published TCP port even when it answers on the Docker host only; they now skip loopback bindings, through one helper, DockerSearchIndex.firstWebPort(). A new spec in docker-table-webui.spec.js fails on the old code.

  • Fix
    the release notes follow the container and the last check

    The changelog cache was one list per repository, filtered by the first container that asked: a container on a prerelease and one on a stable version of the same project saw each other's list for a day. The key now carries the prerelease choice, and a list fetched before the last update check is fetched again, so a release the check just found is not missing. TestChangelogCacheKeepsPrereleasesApartAndFollowsTheCheck fails on the old code.

  • Fix
    a GitHub token that is turned down says so

    A 403 was always rate-limited; with requests left it is now auth-failed, and the drawer says to check the token under Config → Containers (dockerChangesAuthFailed, English fallback until the next docs round). TestChangelogRouteNamesARefusedToken fails on the old code.

  • Fix
    docker error responses are JSON again

    writeDockerError, dockerTarget and the update-failure answer set the status before the content type, so every 404, 502 and 503 went out as text/plain. TestDockerErrorsAreJSON fails on the old code.

  • New
    a timeline per container

    The side panel's Overview gains Timeline: what happened to the container, newest first — started, stopped (by you, by someone, or by nextDash), exited on its own, crashed with its exit code or out of memory, turned unhealthy and healthy again, paused and resumed, updated and rolled back — with a run of crash-and-restart cycles folded into one Kept restarting line. The notifier, which reads Docker's event stream anyway, writes these to data/docker-events.json whatever the notices are set to (Docker keeps only a few hundred events itself, and healthcheck execs use them up): a hundred per container, for thirty days, kept by name so a container an update recreated keeps its history, saved in batches on the notifier's tick. GET /api/docker/containers/{id}/timeline merges them with the update history; the part asks for it only when opened. The first healthy of a container that was never unhealthy is its healthcheck starting, and is not written down. docker_timeline.go.

  • New
    keys for the logs window, mute and Disk, and Shift+Y into the view

    In the Containers view, l opens the selected container's logs window, m mutes or unmutes its notices and d switches between the list and Disk — none of them taken elsewhere; from the dashboard or Config, Shift+Y opens Containers (C, D, K, N and O were taken). The legend now names every key of the view — move, details, search as well — and shows without actions switched on too, leaving out the keys that act on Docker; the cheat sheet and its PDF list the new keys.

  • New
    the Containers key legend goes above the list, below it, or away

    Config → Containers → View → The key legend, with the choices Bookmarks and Inbox offer; above, where it always stood, is the default (dockerViewKeyLegend).

  • New
    the Containers tour covers what was added

    Two steps more, ten in all: Logs, live and What the disk holds; the others now name the sortable headings, CPU and RAM, the stack buttons, Health, Updates and Timeline, skip, hold and rollback, notices and mute, and Shift+Y. The tip id stays containersTutorialV1, so nobody gets the tour again unasked.

  • Fix
    a failed webhook post for a container names the container in the log

    The warning used the notice's URL, which a container notice does not have, so it read " could not be reached"; it now falls back to the name.

  • Fix
    a rollback that had to be undone says it was a rollback

    When the new container failed and the old one was put back, the message spoke of a failed update; it now reads The rollback of {name} failed at "{step}"; the container runs as before. (dockerRollbackRolledBack, English fallback only until the next docs round). A new spec in docker-updates.spec.js fails on the old code.

  • Fix
    muting a container whose save fails is no longer kept or reported as done

    toggleMute() waited for saveSettings() to throw, but a failed save resolves false: the muted list stayed changed in the browser, the menu said Unmute, and "No more notices about …" showed beside the save error. It now puts the list back and says nothing of success. A new spec in docker-notify.spec.js fails on the old code.

  • Fix
    a burst of container notices reaches the webhook as one message

    One crash taking its dependants along sent a message per container, the pattern Slack and Telegram rate-limit. Four or more notices of one event at once now go as one — 6 containers need attention (or recovered), naming the first three and a count — as Health's own downtime alerts already did; fewer, or a mix of downs and ups, go one by one. Browser notifications stay one per container. TestDockerNotifierDigestsABurst fails on the old code.

  • Fix
    a corrupt update history is no longer overwritten

    A docker-update-history.json that does not parse is left alone, with a warning, instead of being replaced by the next update's single entry, which lost every rollback in it. TestDockerUpdateHistoryKeepsAnUnreadableFile fails on the old code.

  • Fix
    the logs stream's heartbeat stops before its handler returns

    A beat due just as the stream ended could write to a response the server had already taken back. TestDockerLogStreamHeartbeatEndsWithTheHandler fails under -race on the old code.

  • Fix
    container notices no longer call a slow stop a crash, or a finished job one

    A stop whose grace period ran past ten seconds was told as "stopped unexpectedly": a stop's SIGTERM or SIGKILL now covers five minutes, a reload signal such as HUP covers nothing, and a start ends it. nextDash's own action counts as expected for its whole length rather than ten seconds from its start, so a long pull before the stop no longer matters. A container that exits 0 and stays down finished its work and raises no notice; a loop of them still does. TestContainerNotifierLongStopsAndFinishedJobs fails on the old code.

  • Fix
    an image prune no longer takes the image an update is about to use

    Between an update's pull (or a rollback's tag) and its create, the new image is unused, and a prune of unused images removed it. An image prune now answers busy while any container action runs, and an update or rollback answers busy while a prune runs; the build cache is not held back. TestDockerPruneAndUpdateExcludeEachOther fails on the old code.

  • Fix
    sort by uptime follows when a container last started, not when it was created

    An old container that restarted five minutes ago used to sort as the longest running. compareFn() in dashboard-docker.js now orders on startedAt, longest up first; a stopped container has no uptime and goes to the end, by name.

  • Fix
    the logs window and the volume confirmation dim the page behind them

    Their ::backdrop read var(--modal-scrim), but a backdrop inherits no custom properties in every browser (Safari among them), so the page stayed as bright as before; the scrim is now written out, a shade darker than the app modal's, with its 3 px blur.

  • Fix
    an empty Disk tile reads 0 B, not 0 KiB

    formatBytes() in dashboard-docker-disk.js counts in bytes below one KiB.

  • New
    a Disk tab in the Containers view: what images, volumes and build cache take up, and clearing what nothing uses

    Containers | Disk sit in the toolbar row; Disk has its own address, #docker/~disk (no container name can start with ~, so a container called disk keeps #docker/disk). Four tiles — unused images, dangling images, build cache, unused volumes — each with its size and its clean-up, then the images and volumes themselves, biggest first, with what uses them; an untagged image that is still a container's way back (the update history of the Updates part) says "rollback for sonarr", and the dangling and unused tiles warn which rollbacks a prune ends, as does the question before it runs. Every prune asks first with the size it frees; volumes, which hold data, are never pruned in bulk but removed one at a time from their row, only after typing delete (a fixed word: an anonymous volume's name is 64 random characters), and never while a container — a stopped one included — holds them. The rail gains Disk used and Reclaimable once the tab has measured; measuring (/system/df) is slow on a big host, so it happens when the tab is opened and on Refresh. Read-only shows the sizes and no buttons. New routes: GET /api/docker/disk, POST /api/docker/prune/{images-dangling|images-unused|build-cache} and DELETE /api/docker/volumes/{name}?confirm={name}, the last two behind control and the write token like the actions, one prune at a time, each in the activity log. dashboard-docker-disk.js, loaded with the view. Any open native <dialog> now counts as a modal for the view's keys. New strings have English fallbacks only, until the next docs round.

  • New
    the Web UI column falls back to the first published TCP port

    A container with no web UI address (no Unraid template label, none set in the drawer's Custom) showed an empty cell, which on a plain Docker or compose host was every row. It now links the first public TCP port, as :port, as the row menu's Web UI already did; UDP alone still leaves it empty, and a template or custom address still wins. DashboardDocker.portLink(); the link carries data-docker-webui-port.

  • New
    the containers side panel closes on a press beside it

    As in Bookmarks and Inbox, through the shared side panel's closeOnOutside: a click or touch anywhere else closes it, one on another container row moves it there instead, and Config → Containers → Close on a click beside it (dockerViewCloseOutside, on by default, and on for a settings file that predates it) keeps it open. fix — the shared side panel now also ignores presses inside a native <dialog>, which carries its role without the attribute: a click in the logs window no longer closed the drawer behind it.

  • Fix
    the containers table fits between the phone layout and a wide screen

    With CPU and RAM beside it, the table ran out of room around 800 pixels: the image broke mid-word and the status wrapped over three lines. Below 1100 pixels the Image column now goes (the drawer names it), and below 900 pixels CPU and RAM go as well; from 768 pixels down the phone layout takes over as before.

  • New
    notices when a container stops unexpectedly, keeps restarting or turns unhealthy

    And a second notice when it recovers: running again, stable again after ten quiet minutes, or healthy again. nextDash follows the daemon's event stream (GET /events, one connection, reconnected with a growing pause) rather than polling, so a crash the restart policy fixes within seconds is still seen, and a crash is told apart from a deliberate stop: Docker's own stop sends kill before die, and nextDash's own stop, restart, update and rollback are marked as expected. A die is only told when no start follows within 30 seconds; three crash-and-restart cycles in ten minutes are a loop, told once. Out-of-memory kills say so. One notice per incident. The notices go where Health's downtime alerts go — the alert webhook with its presets (the raw JSON carries source: "container", and ntfy's button opens the container) — and to browser notifications under a new category, Notify when a container stops, keeps restarting or turns unhealthy. Config → Containers gains Notifications (dockerNotify, on by default, and on for a settings file that predates it) and Muted containers, which says where notices go or that nothing receives them yet; a container is muted from its row menu or its drawer's ⋯ menu, and the drawer's Details says Notifications: on, muted or off. Muted, hidden and nextDash's own container raise nothing. Every notice is also in the activity log. The decisions are a state machine fed events and a clock; the webhook sending that monitors used is now postMonitorTarget, shared by both. New strings have English fallbacks only, until the next docs round.

  • Fix
    the drawer's image chip names the tag once

    nginx:alpine read nginx:alpine:alpine: _layout() in dashboard-docker-drawer.js added the tag to a reference that already carries it. The chip now shows the reference as the container was made from it.

  • New
    skip a version, hold updates, see what updates did, and roll the last one back

    The drawer's Overview gains an Updates part: where the image stands, Skip this version (the digest on offer stops counting as an update — no badge, no count, left out of an update of a selection — until a newer one appears), Hold updates (the image never counts as having one until resumed; the row shows a quiet held label), Undo for either, and a history of what updates did, newest first, with versions from org.opencontainers.image.version or short image ids. While the image the last update replaced is still on the host, Roll back to that version asks first, then tags that image as the reference again and recreates the container on it — the update's own swap without a pull, so the container keeps its ordinary reference and later checks still work — writes it down, and skips the version it left so it is not offered straight back. Updating by hand still works on a skipped or held image. New: data/docker-update-history.json (twenty entries per container), held and skipped beside the check's results in docker-updates.json, which every route now serves with those choices applied (status skipped or held), POST /api/docker/updates/choice behind the write token, and a rollback action behind the same control and token as update, which refuses with a reason (no-rollback, old-image-gone, pinned-by-digest) and touches nothing when it cannot. A check keeps the choices, and lets go of a skip once the registry has moved past that digest. dockerRecreate is split so the swap (dockerRecreateOn) serves both. New strings have English fallbacks only, until the next docs round.

  • New
    a logs window that follows a container's log live

    Opened from the row menu's Show logs, from :docker <name> logs, or from Open logs window in the drawer's Logs tab, which stays the quick look. It takes most of the page (the whole screen on a phone) and follows the log as it is written; scrolling up pauses the follow and counts what arrives meanwhile, with Jump to latest to catch up, and a stream that ends (the container stopped) offers Resume, which picks up after the last line without showing it twice. One toolbar: search that marks every match with Enter and Shift+Enter to step through them, Filter to show only matching lines, All/stdout/stderr, how many lines to start with, timestamps, wrapping, Copy for the lines shown and Download for the loaded lines as <name>-YYYYMMDD-HHMM.log; stderr lines are red. Keys: / search, f follow, Enter next match, Escape close. The choices are kept per browser. It reads a new route, GET /api/docker/containers/{id}/logs/stream, which follows the daemon's log with timestamps and answers NDJSON, one {t, s, m} object per line with its stream (a TTY container's lines all count as stdout); it sits behind the write token like /logs, lifts the server's read and write timeouts for itself, sends a blank heartbeat line every 25 seconds so a reverse proxy keeps a quiet stream open, and ends when the container stops or the window closes. At most 5,000 lines stay on screen and 16 KiB per line. A native <dialog>, so the page behind is inert while it is open. New strings have English fallbacks only, until the next docs round.

  • New
    CPU and RAM columns in the containers table

    Each running container shows the stats sampler's latest reading (every 30 seconds) beside its status, right-aligned; a stopped one, or one not read twice yet, shows —. The list route carries the reading as usage from the sampler's in-memory store and says usageEnabled, so the columns cost no stats call per row; with Config → Containers' history switched off there are no columns and no CPU or memory sort. Both headings sort, highest first on the first click, and a container without a reading stays last either way; the toolbar's sort select offers CPU and memory too. Hidden at phone width, like Image. New strings have English fallbacks only, until the next docs round.

  • New
    the container drawer shows the healthcheck's last checks

    Overview gains a Health part, there only for a container that reports a health state: the status, how many checks have failed in a row, the healthcheck command as typed (CMD arguments joined, a CMD-SHELL line as is), and the last five checks newest first, each with its time, a ✓ or ✗ with the exit code, and its output capped at 2,000 characters. The checks come from a new route, GET /api/docker/containers/{id}/health, read from inspect's State.Health and Config.Healthcheck; it sits behind the write token like logs and env values, since a check's output is a command's output, and it is only asked for when the part is opened. New strings have English fallbacks only, until the next docs round.

  • New
    a compose project starts, stops and restarts as one stack

    Grouped by project, each project's group row carries Start, Stop and Restart; they run the selection bar's runBulk() over the project's rows as shown, so Stop asks once with the names and the containers go one at a time, and a filter or search narrows the stack as it narrows a selection. A button is disabled when no container in the stack allows it, No project gets none, and a read-only daemon (NEXTDASH_DOCKER_CONTROL off) shows none. Enter on a focused stack button runs it instead of opening the selected row's drawer. Update stays with the selection bar. No new strings.

  • New
    the Name and Status headings sort the containers table

    A click sorts by that column; a second click turns the order round, and the direction is kept with the rest of the view state (sortDir in nextdash.docker.view). The toolbar's sort select follows the headings, and picking a sort there starts in its natural direction; uptime stays in the select only, as it has no column. The active heading carries aria-sort and a drawn arrow; Enter on a focused heading sorts instead of opening the selected row's drawer, and focus stays on the heading. No new strings.

  • New
    the containers table names its columns

    Name, Image, Status, Web UI and Ports sit above the rows and stay pinned under the view's header while the list scrolls; at phone width, where rows fold into two lines, the headings are hidden. The Name, Status and Ports labels are new locale keys, still English outside en until the next docs round.

  • New
    web UI and port links reach the container, not just the page's host

    A container on a macvlan or ipvlan network (Unraid's br0) has its own LAN address, and [IP] in its web UI now means that address; the list and detail routes hand it over as lanIP, read from the daemon's network list, and a daemon that will not list its networks leaves the links as they were. Config → Containers → Links adds Docker host address for when the dashboard is opened through a reverse proxy or tunnel: ports and [IP] then point there instead of at the browser's host. One helper in docker-search-index.js now fills [IP] for the table, the drawer, the row menu and :docker <name> open, which each did it themselves before.

Docs

  • Fix
    the check-mode menu spec closes an open menu before the next right-click

    On CI the bookmark menu still open from the previous step covered the first row and took the click, every retry; dashboard-check-mode-menu.spec.js now presses Escape until it is gone.

  • Fix
    the settings-jump spec looks for the uptime webhook by field

    Searching "webhook" now also finds Containers' notices first, so the test landed in Config → Containers; it picks monitorNotifyUrl itself.

  • Fix
    a statistics CSV export could carry a bookmark's old name or count

    The export read the figures memoised at the last paint, so a rename or an open since then went out stale; exportStatsCSV() now drops the memo first. config-stats-export-truncation.spec.js memoises before renaming, and was the flaky failure on CI's third e2e shard.

  • Fix
    the wide Containers tile spec counts nine figures

    Updates, reclaimable space and incidents joined the tile's figures, and an unset list shows them all; widget-wide-columns.spec.js still expected six and failed CI's last e2e shard.

  • Fix
    CI's gofmt check passes again

    Two Containers test files, docker_fake_test.go and docker_recreate_test.go, were committed unformatted, so the go-test job stopped at make fmt-check before go vet and the tests ran.

  • Docs
    static/data/whats-new/v1.15.2.json and its index entry, and four Overview features

    whats-new-stub.js moves NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v306 and DASHBOARD_RELEASE to v1.15.2, so the window opens once for this release. Config → Overview and About → News & features gain Several containers at once, A container's log, live, What the Docker disk holds and Told when a container goes down (since: v1.15.2, in all six languages); their buttons open the Containers view or Config → Containers, which openViewFromTile() now reaches. go generate refreshed asset_hashes_gen.go.

  • Docs
    README, manual, Help and translations caught up for v1.15.2

    README's Containers list now names the logs window, Disk, notices, stack and ticked actions, skip, hold and rollback. MANUAL §9.3 describes the category ⋯ sort menu (it still spoke of A–Z and Recent chips), §14.2–§14.4 ticking containers, the custom address dot and head tag and their keys, §23.8 the docker-action event, and §14.9 the full Behavior → Status & alerts → Downtime alerts path. Config → Help (Containers, Bookmarks, Self-hosting) says the same. In Dutch, German, French, Spanish and Chinese: the 15 new keys, and 13 texts whose English had grown since they were translated (the Containers tour, the analytics notice, three Help pages).

  • Fix
    the Docker host address spec no longer fails one run in twenty or so

    A load of /#config/containers draws config twice, from loadData() and again from init()'s renderDashboard() once the language is in; a fill() that landed between the two was drawn over, so Tab committed nothing and the poll of /api/settings never saw tower.lan. docker-table-webui.spec.js now waits for _configRefreshReady before typing; 100 runs in a row pass.

  • Docs
    Help, the manual and the cheat sheet describe the Containers additions

    Config → Help → Containers (The Containers view and Setting it up) and MANUAL §14 (with new §14.7 Disk, §14.8 The logs window, §14.9 Notices), §7.1 and §17.7 cover Shift+Y, the keys, sorting, CPU and RAM, stacks, Health, Updates, Timeline, the logs window, Disk, notices and the new settings; npm run generate:cheatsheet rebuilt the cheat sheet's HTML and PDF. The 176 locale keys the Containers work had left as code fallbacks are now in all six locale files, in English outside en until the next docs round translates them; the English Help and tour texts that changed keep their earlier translations until then.

Only docs and tests changed in this release.

v1.15.1 Updating or stopping a container from the Containers view failed on a real host, and said the socket was missing when it was not; an existing install still started new bookmarks on Off; and :config missed two sections. 5 fix

Updating or stopping a container from the Containers view failed on a real host, and said the socket was missing when it was not; an existing install still started new bookmarks on Off; and :config missed two sections. Recorded but not announced: the What's new window still leads with v1.15.0.

Containers

  • Fix
    update and stop were cut off after five seconds

    Every call to the Docker socket went through one client with a five-second Timeout, and Go's http.Client counts reading the body in that. An update's pull streams progress for as long as the layers take, and a stop waits out the container's own stop timeout (ten seconds by default), so both were cut off mid-way. Start, stop, pause, restart, update and remove now use a client without that deadline; dockerActionTimeout (ten minutes) on the action's context ends one that hangs. Reads keep the five seconds. TestDockerUpdateOutlastsTheReadTimeout holds the fake daemon's pull and stop open longer than the read deadline and fails without the change.

  • Fix
    a failure no longer claims the socket is missing

    writeDockerError answered every error that was not the daemon's own reply with 503 {"reason":"no-docker-socket"}, and the browser, not knowing that reason, fell back to Docker did not do that. Only a failure to reach the socket is reported that way now; anything after the connection is 502 {"reason":"docker-error","message":…}, and a failed update adds failedStep (pull, stop, rename, create, connect or start) to the message. Every failed action is logged with its error. TestDockerUpdateSaysWhatBroke cuts the pull stream off halfway.

Bookmarks

  • Fix
    an existing install still started a new bookmark on Off

    v1.15.0 moved defaultNewBookmarkCheckMode to Periodic, but Off had been the default before and every install that ever saved its settings had written it into settings.json, so the change reached fresh installs only. A stored Off now moves to Periodic once, marked by newBookmarkPeriodicMigrated; Monitor was never a default and stays, and Off chosen afterwards sticks. The fallback form in search-commands-new.js, used when the dashboard's own form is not loaded, preselected Off whatever the setting said and now follows it too. TestStoredOffCheckModeMovesToPeriodicOnce seeds a stored Off.

Everywhere

  • Fix
    :config did not offer the Inbox and Containers sections

    Both were added to the Config rail in v1.15.0 but not to _CONFIG_SECTIONS in search-commands.js, so the palette's list of sections stopped short of the rail. They are there now, in rail order, with commands.configInbox and commands.configContainers in all six locales. dashboard-command-palette-config.spec.js compares the palette with the rail.

  • Fix
    the page could stay locked after a modal closed

    The watcher that holds the scroll lock while any modal is open re-checked on a mutation or a transitionend; a close whose transition was cancelled, or never ran, fired neither once the overlay was finally hidden, and the page stayed unscrollable with nothing on screen. Seen in CI only. It now also listens for transitioncancel and looks again every 300 ms while it holds the lock. scroll-lock-refcount.spec.js polls for the release and, when it fails, names who still holds the lock.

Only docs and tests changed in this release.

v1.15.0 Three views take over from the old ones: a Bookmarks view at #bookmarks that holds the whole collection and everything Health used to do, a Containers view for the Docker host nextDash runs on, and an Inbox rebuilt on the same side panel. +48 5 fix Read the post

Three views take over from the old ones: a Bookmarks view at #bookmarks that holds the whole collection and everything Health used to do, a Containers view for the Docker host nextDash runs on, and an Inbox rebuilt on the same side panel. Work through and triage both start from a pile and say why each item is there. 34 new theme families, a Container list widget, Statistics rebuilt in two columns, and new screenshots.

Bookmarks view

  • New
    a view of its own at #bookmarks

    with its icon in the header (Bookmarks, then Inbox, then Containers). A rail of views, health filters, pages, categories and tags on the left; one-line rows with tags, shortcut, a score, 30 days of opens as bars, when it was added and last opened; a side panel on the right.

  • New
    the side panel in three tabs: Details, Health and Usage

    (1 2 3, [ ]). Details edits the bookmark and saves as you type, and fills in the preview the server already has. Health is a summary with an accordion of why, score breakdown, checking, monitor history and expectations. Usage draws opens over time. Every way of opening a bookmark counts, and an open shows in the bars at once.

  • New
    group by page, category, site, status or tag

    Every row is coloured by its health and scored; checking can be turned on for everything still Off in one go.

  • New
    pages and categories in a modal over the list

    (Shift + P / Shift + C): drag, move, merge and tidy on one screen.

  • New
    Collection health

    (h) on one screen, in two tabs: Overview (score over time, what is wrong by kind, by page, checking coverage, monitors, certificates) and Monitors & trend. +N pages unfolds the rest in its card.

  • New
    one bookmark's health in large

    (Shift + H on a row, the row menu, or ⤢ on the Health tab): Overview and Checks, a period from today to 90 days, every value under the pointer, and every check of the period with CSV export. The server serves one bookmark's checks and 90 days of daily summaries as JSON.

  • New
    a Collection ▾ menu

    in the view's band for the whole-collection tools: Collection health, Rot report, Pages & categories, merge duplicates, checking, retest, open broken, fetch previews, export and refresh. An ⓘ explains the view.

  • New
    promote an Unsorted bookmark

    from its side panel or row menu, as the inbox does.

  • New
    Config → Bookmarks → View

    the view's own settings, with a live preview on a fixed example. The old List tab is gone; the list is the Bookmarks view's alone.

  • New
    #health and the Health icon lead to the Bookmarks view

    The standalone Health view is gone; its filters, summary, keys, bulk actions, duplicates and form live in the Bookmarks view.

  • Fix
    the panel's address stays on one line

    so the tabs do not move; preview text in Details no longer shows HTML entities.

Work through

  • New
    choose a pile first

    Broken links, Changed or wrong content, Stale, Never opened, and This list as it is filtered now, each with its count and the one that needs you most on top.

  • New
    each card says why the bookmark is here

    and offers one main step: Re-check now for what fails, Open it and decide for what is stale or never opened. Beside it: Fix the address (e) and Delete (d). Not now: Keep (y, the reason will not come up again), Ignore 30 days (z), Skip (j).

  • New
    the end of a pile counts

    what was fixed, deleted, kept and snoozed, and offers the next pile.

  • New
    Save preview (s)

    writes a preview the card fetched onto the bookmark, onto the right copy when the URL is duplicated.

Inbox

  • New
    one-line rows and the Bookmarks view's side panel

    with Open, Promote and Keep in it and a legend for its keys. Rows are plain list rows at the height of the Containers view's, and the row under the cursor has no glow.

  • New
    Triage starts from a pile

    Waiting longest, New this week, With a note, This list as filtered now. Each card says where the link came from, how long ago, whether it was opened, and its note. Promote to a page is the main step, and after the save triage carries on with the next link; Keep in Unsorted, Note and Delete beside it; Snooze, Mark read and Skip under Not now. The end of a pile counts what was promoted, kept, deleted, snoozed and read.

  • New
    the Kept tab is gone

    kept links wait in Bookmarks → Unsorted, and the Unsorted widget reads from there, a row opening its side panel.

  • New
    the tags dialog

    completes existing tags and shows suggestions.

  • New
    Config → Inbox

    as its own section, in four tabs: Collecting, List, Panel & clicks and Header icon, with previews on fixed examples.

  • Fix
    triage

    Enter on a focused button presses that button, a pile that emptied while the chooser was up recounts instead of freezing, and a promote resumes past the links already skipped.

Containers

  • New
    a Containers view at #docker

    for the Docker host nextDash runs on: filters for All, Running, Stopped and Updates, group by status, a status glow per row, ports and a web UI column. The header icon counts containers with an update waiting.

  • New
    the side panel in four tabs

    Overview (Details, Network, Custom, Volumes, Environment), Resources, Logs and What's new — the release notes between the running version and the newest.

  • New
    CPU and memory over the last hour

    as two charts under Resources. The server samples running containers every 30 seconds, in memory; Config → Containers → Keep the last hour of CPU and memory switches it off.

  • New
    a web UI address of your own

    under Overview → Custom (http/https, [IP] for this server), used by the list, the Container list widget and :docker <name> open.

  • New
    start, stop, pause, restart, update and remove

    behind NEXTDASH_DOCKER_CONTROL=1; update and remove always ask, Config can add stop and restart. The container nextDash runs in refuses to stop, pause, restart, remove or update itself. A long action outlives the server's write timeout.

  • New
    image update checks

    on request and every 6, 12 or 24 hours, asking the registry which digest a tag points at; an optional GitHub token raises the rate limit for release notes.

  • New
    search finds containers

    and :docker <name> offers what can be done to one.

  • New
    Config → Containers

    the connection as the server sees it, View, Updates, Safety, hidden containers and the GitHub token. It says why the view is empty without a socket and links the setup help.

  • New
    the container joins the socket's group

    at startup and says so when access is denied; NEXTDASH_RUN_AS_ROOT=1 for a socket owned by gid 0.

  • New
    an eight-step tour

    on the first visit.

Widgets

  • New
    Container list

    the containers themselves, one per row; one column on a narrow tile, two on a wide one. Running only or all, problems first or by name or uptime, uptime, image tag or nothing beside the name, and a click that opens the container in the view or its web UI.

  • New
    the Containers tile

    opens the view, and its update figure links to #docker?filter=updates.

Themes

  • New
    34 families, each light and dark

    six glass, four lacquer, four carbon, four matrix (terminal), four aurora, four frost, four brushed and four ink — 155 families, 310 themes.

  • New
    a new badge

    on them in the theme browser, and searching new finds them.

  • New
    Matrix Bluepill

    is the theme a fresh install starts on.

  • New
    --accent-vivid

    a colour even where a theme's accent is grey.

Statistics

  • New
    tabs renamed and rebuilt

    Overview, Usage, Collection, Inbox and Health. Each opens with six figures and lays its panels out in two columns.

  • New
    Needs attention

    on Overview lists only what is above zero, each with a button: links not answering, a certificate close to expiry, unread inbox items older than 30 days, bookmarks never opened.

  • Fix
    the charts' axes and figures are corrected

    Stale follows Count as neglected after like the rest of the app, and the health trend counts skip Unsorted. The CSV export fetches the inbox and health figures itself.

Everywhere

  • New
    search keys > : ? * open from every view
  • New
    slow actions show a wait

    and the bookmark being checked again is marked.

  • New
    modals hold the page still

    any open modal takes the scroll lock, and they share one scrim.

  • New
    What's new

    lit rows, filters and a support card.

  • New
    tours

    a thirteen-step dashboard tour once quick-start is done, ten steps for the Bookmarks view, six for the inbox, eight for Containers.

  • New
    new bookmarks start on Periodic checking

    and the + form follows the setting.

  • New
    callouts take the theme's accent

    instead of a warning yellow.

  • New
    the cheat sheet

    covers the Bookmarks and Containers views and prints black on white; its link is hashed so a new PDF is never hidden by the cache.

  • New
    startup warns when a write or capture token is weak
  • Fix
    :health page

    lists the pages again, and :health reaches every filter.

  • Fix
    stored preview text

    with HTML entities reads back as characters in the inbox and Unsorted.

Setup

  • New
    docker-compose.yml and the Unraid template

    ship with Docker actions and root off (NEXTDASH_DOCKER_CONTROL=0, NEXTDASH_RUN_AS_ROOT=0) and the socket commented out; local settings go in docker-compose.override.yml.

  • New
    README and MANUAL

    describe setting up the Containers view — socket, actions, write token, and when root is needed — and that the write token keeps other sites out but is not a login.

Only docs and tests changed in this release.

v1.13.7 The bookmark form is rebuilt around one read of the page, tag suggestions reach every place a tag is set, and the grid stops dropping to one column on any narrow window. +12 5 fix

The bookmark form is rebuilt around one read of the page, tag suggestions reach every place a tag is set, and the grid stops dropping to one column on any narrow window. Leads the What's new window, and v1.13.1, v1.13.5 and v1.13.6, recorded but held back until now, are shown there as well.

Bookmark form

  • New
    one column, in the order it is filled in

    Address, name, a preview card, tags, page › category with the shortcut, pin and checking, note. The two side-by-side groups are gone, and so are the icon-URL field, Set URL and the separate Fetch button. The form is split into bookmark-form-card.js, bookmark-form-title.js and bookmark-form-place.js under static/js/bookmark-form/; the hidden page and category selects and the icon input stay as the data model, so the save path is unchanged.

  • New
    one read of the page after the address

    Leaving the address field makes a single /api/bookmark-preview call that fills the icon, a name suggestion (the host when the page has no title), the card and the keywords for tag suggestions. A changed address starts a new read and only the latest one counts (fetchSeq); a fetched icon is replaced, an uploaded or stored one is kept. The card says Reading the page… while a slow site answers, explains itself before there is an address, and says No preview with Try again when the read gave nothing. Create + New resets it. A form opened with an address already in it — a paste, the inbox, :new <url>, the extension — reads the page at once.

  • New
    the icon's ✎ menu

    Upload…, Fetch again, Clear.

  • New
    a name suggestion

    An empty name field shows the page's title as Suggested from the page · Clear; a typed name gets Page: … · Use under it instead.

  • New
    suggested tags in the form

    Chips from TagSuggestLive.forDraft under the tags field: the collection is the evidence, the page's keywords the last source, and a bookmark being edited gets its stored keywords from /api/tags/keywords without reading the page. + adds, ✕ refuses for the site everywhere (dismissedTagSuggestions), ↻ asks again. Config → Tag suggestions follows every change through TagSuggestLive.changed and onTagEvidenceChanged.

  • New
    page › category in one field

    It opens the Move to… popover (move-popover) with a filter; arrows and Enter pick, and Enter with one match takes it. Its first rows hand off to the form's existing InlineCreateRow for a new category or page, and a new page opens its first-category row.

  • New
    ⓘ on tags, shortcut and checking

    , the check group's own button, with the text as the field's aria-describedby.

  • New
    save guards

    No page: a notice. No category: Save without / Choose a category. The same link on another page: Already saved · Save anyway. The same link on this page: a notice naming the bookmark that has it, where it used to fail with Could not create bookmark.

  • New
    keyboard-only use

    The form opens with the cursor in the address field, adding and editing (keyboardNavigation.disable() now runs before the render, which stole the focus). While it is open the form owns Tab: its own controls in order, wrapping at both ends, so focus can no longer walk out to the What's new ★ or the page tabs. The tag list no longer pre-selects its first entry when nothing is typed, so Tab moves on. Escape closes the tag list, the icon menu, the place popover and the create row before the form, and a dialog on top of the form (z-index 10300) takes the focus through its fade.

  • Fix
    the dashboard no longer scrolls behind the form

    (ScrollLock.acquire('bookmark-form-modal'), overscroll-behavior: contain), and a render while it is open no longer aborts the form's fetch timer.

Tags

  • New
    suggestions in the Config → Bookmarks side panel

    Up to three chips under the tags field of a single bookmark; + writes the tag through commitWorkbenchField, ✕ refuses. A selection of several gets none.

  • New
    a Suggested section in Shift+T

    (forDashBookmark, top three) and in the multi-select Tags popover. Each selection offer counts the rows it fits (on 1 of 2), and applyTagToSelection(tag, mode, { onlyKeys }) writes, rolls back and undoes only those rows.

  • New
    one chip component

    TagSuggestChips.render and refuse in static/js/shared/tag-suggest-chips.js, used by the form, the side panel, the inbox and Kept.

  • Fix
    Shift+T opens at the top of its list

    It focused the row's first tag on open, so a long library scrolled it 1250px down and hid the header, the row's tags and the suggestions. It now starts on the first item; the ✓ still marks the row's tags.

Previews

  • Fix
    page titles no longer carry HTML entities

    extractTitleFromHTML returned the <title> text raw, so Q&A reached every reader as written; the meta values were already decoded. Previews cached before this fix keep the old title until they expire or are refreshed.

Dashboard

  • Fix
    as many columns as fit

    Below 768px every window dropped to one column, and between 768 and 991px responsive.css forced two with !important and a flex rule that broke the packed masonry grid. getEffectiveColumnsPerRow now takes the configured count, capped by how many columns of --dashboard-column-min fit in the grid's container; shouldStackDashboardCategories is true only for a touch screen held upright below 768px. A resize that changes the count re-renders the grid. The forced rules in responsive.css and mobile-experience.css are removed, and the wide-category reset follows the stack attribute instead of the width.

  • Fix
    the What's new ★ is hidden below 768px

    on any window, not only on a touch phone.

Tests

  • Fix
    Config → Bookmarks no longer throws when a repaint comes before its renderers

    repaintBookmarksList called renderBookmarksList while the lazily loaded workbench file was still on its way, and logged renderBookmarksList is not a function (caught by config-section-smoke on a loaded CI runner). It now waits for ensureBookmarkRenderers and repaints once they land; config-bookmarks-lazy.spec.js holds the file back and asks for a repaint in that gap.

  • Fix
    opening the bookmark form before the search code has arrived

    The form lives in the lazily loaded search bundle, and inbox Promote, paste-a-URL, the toolbar's add button, the empty state, Health's Edit and Config → Bookmarks' Add and Edit each read its handler straight off searchComponent. In the seconds before the bundle landed they said Could not open bookmark form or did nothing. Dashboard.newBookmarkHandler() fetches the bundle first when the handler is not there yet, and every route goes through it; inbox-promote-pages.spec.js holds the bundle back and promotes in that gap.

  • Fix
    Statistics asked for the health report twice

    when you left the Health tab and came back while the first request was still out. Each loader's field stays undefined until its answer arrives, so the tab's return started another; the loaders now run once per load (_statsInFlight). config-stats-range-and-lazy.spec.js slows the report and goes back and forth.

Only docs and tests changed in this release.

v1.13.6 The video mark gets out of the row's way, the theme browser's Light and Dark filters do what they say, and the theme help and settings catch up with the characters introduced in v1.13.3 — in every language. 4 fix

The video mark gets out of the row's way, the theme browser's Light and Dark filters do what they say, and the theme help and settings catch up with the characters introduced in v1.13.3 — in every language. Recorded but not announced: the What's new window still leads with v1.13.4.

Bookmarks

  • Fix
    the ▶ no longer takes room on the row

    It was a bordered chip after the name, beside the response time and the shortcut, and a busy row got busier. It now sits as a small disc on the corner of the favicon, the way a video service draws play over a thumbnail, and costs the line nothing. The disc is sized in percentages of the icon rather than in em: Safari's minimum font size raised the 6px glyph and the disc grew with it until it covered the whole favicon. The triangle is a clip-path shape for the same reason. With favicons off, the mark goes back beside the name as a bare accent glyph, no box of its own.

Themes

  • Fix
    Light and Dark in the theme browser show every card in that half

    The two segments only filtered: a family with a light half stayed in the grid under Light, but its card kept showing the half of the theme in use, so on a dark theme every card stayed dark and moving through the grid previewed dark themes. variantFor now answers with the segment, and choosing a segment clears the cards switched by hand before it; a single card can still be switched afterwards.

  • Fix
    the glow offer no longer calls every shining theme a gloss theme

    It fires for any theme with a sheen, most of which are not named Gloss; it now says the theme has a shine that is drawn with the glow. Six locales.

  • Fix
    the What has changed tour pointed at things that are gone

    Its themes step described a Gloss badge the theme browser no longer draws, and its last step sent people to Config → Help → Guided tours, which does not exist. The step now shows the Lacquer character badge the browser actually uses, and the tours are replayed from Behavior → Privacy & sync → Onboarding.

Only docs and tests changed in this release.

v1.13.5 A fix for the preview card, which offered a play button on every hover card in v1.13.4. 1 fix

A fix for the preview card, which offered a play button on every hover card in v1.13.4. Recorded but not announced: the What's new window still leads with v1.13.4.

Bookmarks

  • Fix
    only a video gets a play button

    videoPlayerSource asked where a player might be and took any answer. Markup with no frame in it left an empty address to be resolved against the page's own, which on an https install is a valid https address and so passed for a player — so every hover card drew a black rectangle with a play mark on it, whatever the bookmark pointed at. A provider's oEmbed frame is no longer evidence of a video either: the bookmark's own address decides, the same way the ▶ on the row does.

Only docs and tests changed in this release.

v1.13.4 A bookmark that points at a video now says so, and plays where it is. +4 3 fix

A bookmark that points at a video now says so, and plays where it is.

Bookmarks

  • New
    a row whose link is a video carries a small ▶

    Read from the address alone, so the mark is there the moment the grid draws — no preview, no request. A channel or a search is not a video and gets nothing. The mark is a glyph in the badge's own colour, beside the pin and the note; showVideoIcon turns it off.

  • New
    the preview card plays the video

    Hovering shows the thumbnail your own server already fetched with a play button over it, and nothing reaches the provider until that button is pressed. Pressing it builds the frame, hides the still picture so the card holds one image rather than two, and pins the card so a moving hand cannot stop the video. From the keyboard: Shift + V puts the cursor on the play button, Enter starts it.

  • New
    three ways out of a running player

    Esc closes the card and ends the video, the ✕ over the player does the same, and a click anywhere else now closes a pinned card — which it had promised to do for a while and never did. A click inside the player hands the keyboard to the provider, so Esc is heard again once the pointer leaves the card, which is also when the focus comes back.

  • New
    a player without oEmbed

    The frame's address is built from the bookmark's own URL when the provider advertises none, so a preview stored before the server asked for oEmbed still plays. Every address lands on a host frame-src already admits.

Fixes

  • Fix
    the byline and the video player could not be kept

    linkPreviewParts on the server is the filter a saved checklist is measured against, and neither row was ever added to it: both were stripped out of every save, so ticking them did nothing. They are in the list now, and a one-time upgrade puts them back into a checklist stored while they were being stripped. A list that is empty on purpose stays empty.

  • Fix
    the keyboard cursor's glow was cut off square

    at the end of the row. The bookmark list clips for the collapse animation, and a horizontal visible beside a vertical hidden computes to auto, so both axes clipped at the padding box. The clip box now has the blur as padding and the box is pulled back by the same amount: nothing moved, and the halo fades.

  • Fix
    the paste dialog drew two emoji

    Add bookmark and Save to Inbox now carry the app's own marks — the plus from the header's Add bookmark button and the tray from the inbox tab — rather than pictures from the system font that changed shape per platform.

Only docs and tests changed in this release.

v1.13.3 A theme was thirteen colours. +12 13 fix Read the post

A theme was thirteen colours. It is now a palette and a character: one of

Themes

  • New
    every packaged theme names a character

    Lacquer, Glass, Frost,

  • New
    one line per family

    , saying what it is like to sit in front of.

  • New
    a theme states the surfaces it was drawn for

    Depth, Glow and

Appearance

  • New
    Depth, Glow and Effects start on Follow the theme

    A change made

  • New
    Effects (off / held back / full)

    , emitted as --theme-effects.

  • New
    Vivid

    , a rung above rich where the archetypes open all the way.

  • New
    *Back to the theme's own

    * resets Depth, Glow and Effects for the

  • Fix
    the Surfaces panel lines up

    Notes sat in the third column of the

  • Fix
    themeDepth and glowStrength carried stale defaults

    (glass,

  • Fix
    one button to the theme editor

    Open the theme editor… and *Make

  • Fix
    Surfaces had grown to seven fields against a limit of five

    , and

  • Fix
    the Every theme tick sat in a .config-field

    , the one row shape

  • Fix
    the grid rule for the favicon slider was keyed on its affordances

    ,

The theme browser

  • New
    a row of chips, one per archetype

    isGloss() tested sheen > 0,

  • New
    searching reaches the archetype and the written line

    , in the

  • New
    every theme previews at its own intended surfaces

    while the browser

The dashboard

  • New
    an invitation to try the Widgets layout

    , through

The theme editor

  • New
    a Character group

    : the archetype, the grain's angle and strength,

Under the hood

  • Fix
    --layout-radius-xs/sm/md sat on fixed pixels

    , outside the radius

Development

  • Fix
    five specs pinned rules this release changed

    A fresh install no

  • Fix
    TestGlowLiftIsOneOfTwoNumbers

    required the glow geometry to be a

  • Fix
    eight e2e specs pinned absolute corner radii

    (8px, 4px) or a

  • Fix
    config-field-grid-and-mobile-nav

    read "the first slider on the

  • Fix
    the gloss glow offer wrote glowStrength install-wide

    It goes

  • Fix
    :depth in the command palette listed four choices

    and knew

Only docs and tests changed in this release.

v1.13.2 A fix-only release out of a sweep through the whole dashboard. +6 25 fix

A fix-only release out of a sweep through the whole dashboard. The one worth

Widgets

  • Fix
    reordering a page erased what its widgets watch

    A drag sends the

  • Fix
    a page opened without its widgets

    when its tab had been hovered

  • New
    a widget tile catches the light

    the way a panel in Config does. It

  • Fix
    a Disks tile answers for the disks it was given

    , and for nothing

The dashboard

  • Fix
    the tag cloud kept eating clicks after it was closed

    An invisible

  • Fix
    a long category name fits again

    Titles are shrunk a step at a time

  • Fix
    Move to… opens one popover

    , however fast the key repeats. Two

  • Fix
    a category rule names the category it offers

    The picker listed

  • Fix
    the page name is in the tab title from the first paint

    , instead of

Inbox and Kept

  • Fix
    Shift + I opens the inbox on its first tab

    It opened on whichever

  • Fix
    a failed reload no longer empties the kept pile on screen

    A dropped

  • Fix
    a preview refused with a rate limit is asked for again

    Hovering

  • Fix
    the capture page answers in your language

    The page a bookmarklet

Health and alerts

  • New
    a certificate about to expire reaches a webhook

    health.cert-expiring

Data and backups

  • New
    the Backups panel says where the backups are

    , and warns when that is

  • Fix
    an uploaded icon no longer overwrites another one

    Icons are named

Under the hood

  • Fix
    two background jobs could undo a bookmark you had just added

    The

  • Fix
    a rate limit is counted per connection

    rather than per

  • Fix
    an upload and each file inside it have a ceiling

    A multipart body

  • Fix
    a byte range is never gzipped

    A Range request for a text file

  • Fix
    /api/system/metrics cannot be made to grow forever

    The readings

  • Fix
    the preview cache forgets

    Entries past their seven days are

  • Fix
    several listeners and clients were given back

    : the rename popover's

  • Fix
    tokens are compared in constant time

    , and the health report's

  • Fix
    the last two importers go out through the shared client

    , so GitHub

  • Fix
    the What's new window opens for this release

    It reopens when the

  • Docs
    Help and the manual

    now carry the certificate webhook event and

Development

  • New
    the Unraid template carries the host widgets

    Processor, Memory,

  • New
    CI runs the eleven checks the repo already had

    and nothing ran:

  • New
    the two widget settings tables are held to each other by a test

    A

  • Fix
    eleven tests that had been failing for at least two releases

    Most

  • Fix
    two tests that could not pass whatever the app did

    The scroll

Only docs and tests changed in this release.

v1.13.1 One fix, for the widget v1.13.0 broke. 1 fix

One fix, for the widget v1.13.0 broke.

Widgets

  • Docs
    the weather widget's line in Help and the manual

    now says what a wide tile adds: what it feels like, the wind, the humidity and the chance of rain.

  • Fix
    the weather widget said "Weather unavailable"

    The readings a wide tile added in v1.13.0 — apparent temperature, wind, humidity, chance of rain — are a continuation of Open-Meteo's current= parameter, and adding them dropped the parameter itself. The answer then carried no current block at all, which this client reads as no forecast, so the whole tile went dark. The header's own weather line asks through a different call and was never affected. A test now reads the request rather than the reply: the stubs behind the other weather tests answer any URL, so nothing looked at what was asked for.

Only docs and tests changed in this release.

v1.13.0 A widget set to two columns used to show the same reading, wider. +6 1 fix

A widget set to two columns used to show the same reading, wider. Now it shows more of it: the load average behind the processor's percentage, the container that is failing by name, the date a certificate expires, what the weather feels like. Narrow the dashboard, or open it on a phone, and each tile falls back to the half worth having. The Kept widget also gained an order — newest, at random, or by tag — and prints each link's address under its title.

Widgets

  • New
    two columns say more, not the same thing larger

    Every widget now has a wide reading and a narrow one. Processor adds the 1, 5 and 15 minute load and the core count; Memory adds the file cache and swap; Disks adds used against total and how full the file table is; Containers shows all six figures and names what is failing or just restarted; Health shows four figures rather than two; Health trend opens into two files of rows; Inbox adds what arrived today and this week and how long the queue has really stood; Uptime adds how many are watched, how many are down and the seven-day average; Sources prints when each import last ran; Certificates adds the expiry date and how much is inside the window; Feeds adds how many are followed and how many stopped; Neglected splits its count into dropped and never opened; Calendar adds the date and how long an event runs; Weather adds what it feels like, the wind, the humidity and the chance of rain; Archive, Duplicates, Trash, Blind spots and Backups hold their later figures back until there is room.

  • New
    lists of rows run in two files

    on a wide tile — RSS, Inbox, Uptime, Sources, Certificates, Feeds, Neglected, Calendar, Kept and the Custom widget's items. RSS's "show less" row keeps the full width.

  • New
    the extra readings follow the width the tile actually got

    , not the number of columns it asked for: a two-column widget on a one-column dashboard, or on a phone, narrows itself and drops back to the important half at once, with nothing refetched.

  • New
    the weather forecast now carries the apparent temperature, wind speed, humidity and chance of rain

    , asked for in the same Open-Meteo request the forecast already made. Wind follows the temperature unit: mph beside Fahrenheit.

  • Fix
    a row's name no longer shrinks to nothing

    when a second figure sits beside it, and a date beside a row no longer wraps the row onto three lines.

Kept

  • New
    the Kept widget has an order

    : most recent, random, or by tag. With a tag it shows only that tag; without one it groups every tag under its own heading, untagged last. Random carries a shuffle button that reorders without refetching.

  • New
    each row prints its address under the title

    , without the scheme and www., cut in the middle so the host and the end of the path both survive.

Only docs and tests changed in this release.

v1.12.0 A third answer for the inbox. +22 9 fix

A third answer for the inbox. Until now a link left the queue as a bookmark or not at all; Keep holds on to it without asking where it belongs, on a Kept tab beside the queue — and the tab brings what a pile of postponed decisions needs: where each link probably belongs, tags it would be given, grouping, filing a whole group at once, and a run that puts one link in front of you at a time. Around it, every write in the inbox, the kept list, health and Config → Bookmarks now touches only the rows it changes, and each one can be undone from its toast.

Inbox

  • New
    Keep, the inbox's third answer

    Every queue row has a Keep button, Shift + K keeps the row under the cursor in the list and on the triage card, and the right-click menu offers it too. The link leaves the queue for good, with its note and tags, to a hidden Unsorted page (Page.Hidden, reserved id 999999, GET /api/unsorted). A copy of the row flies to the Kept tab, its count steps up, and a toast names the place with Undo.

  • New
    the inbox has two tabs

    , To triage and Kept, a real tablist with roving tabindex and Arrow/Home/End. The queue's tab carries the header badge's own count — unread and awake — and the two repaint each other, so neither lags a reload behind. Shift + U and #unsorted open the inbox on Kept.

  • New
    r marks read in the list and in triage alike

    Triage's r used to keep; one letter meant two things a tab apart. Keep is Shift + K in both, and the legends, the cheat sheet, the triage hint and the tour say so.

  • New
    the selection bar keeps and tags

    Keep and Tags join promote, open, copy, mark read, snooze and delete; bulk promote asks for a page and a category; Select all on the bar ticks what the filter shows. Each bulk action has an undo, and they write in batches rather than one request per row.

  • New
    Promote carries the tags

    given in the queue, by hand or from a suggestion chip, into the bookmark form.

  • New
    suggested tags where a link is triaged

    The engine behind Config → Bookmarks → Suggestions answers per row in the queue and on Kept: a dashed chip adds the tag, × turns it down in the same list config writes.

  • New
    a drawn tour in nine steps

    , most of it about Kept, each step with a small scene painted from the theme's variables. A Tour button in the band opens it again; the tip id moved to inboxTutorialV2, so everyone who saw the old seven-step tour gets this one once.

  • Fix
    Escape steps back one layer at a time

    : ticks on Kept, then the queue, then the queue's ticks, then the dashboard. The general key handler cleared a selection and let the same press run on.

  • Fix
    Keep undo, and a Keep of a link already filed

    says where it is filed rather than adding a second copy.

Kept

  • New
    each kept row says what it is

    : its tags (two, and +n), how long it has waited (nothing under a week), and file on … when most of that site's filed links sit on one page and category — one click files it there. File a kept link where its neighbours are (Behavior → Inbox & Fresh, off by default) lets Keep do that without asking.

  • New
    group by site, tag, suggested tag or age

    , and sort by last checked among the rest. The sort and grouping are settings, so they follow you across browsers. A group's box or its name ticks the whole group, X takes the group of the row under the cursor, and a right-click on a group heading offers what the selection bar does.

  • New
    the selection bar

    : Move to… (page and category), tags, suggest tags, open, export, snooze, Back to the inbox, delete, and Fetch icons / Fetch previews for the rows that lack them. Filing, sending back and deleting can be undone; a delete's undo takes its trash entries back with it.

  • New
    Work through (f)

    puts one kept link in front of you with every answer under it — file where its site lives, move (m), snooze (z), back to the inbox (b), skip (s), delete (d) — and ends on a count of what was dealt with.

  • New
    back and snooze from the row

    b sends the row (or the ticked rows) back to the queue, with the same flight in reverse; snooze sends it back asleep on the queue's own presets.

  • New
    a line counts the kept links that stopped answering

    , with a filter to them, and another counts the ones already filed on a page, with Remove the kept copies.

  • New
    a card in the corner when kept links pile up

    : ten or more waiting over a month, once. It opens the list; it never files or deletes.

  • New
    a Kept widget

    lists the most recently kept links on a page (WidgetTypeUnsorted, with a rows field).

  • Fix
    filing is add-then-delete

    , and a delete that failed after the add left the link filed and kept; the filed copy is now taken back off the page. Filing and sending back are no longer paced at the outbound-fetch interval, the Move to… picker asks the server for categories (an empty one was missing, others showed an id), and a background refresh no longer wipes the row a popover is anchored to.

  • Fix
    kept bookmarks stay out of the dashboard's pools

    , the tag cloud, smart collections and the health report. Search reaches them while Search unsorted bookmarks (Behavior → Keyboard & search, on by default) is on; Config → Bookmarks shows them under its Unsorted view; Move to… on a dashboard row offers the Kept list as a destination.

Health

  • New
    rows are found by URL

    , deletes go to the trash, and deletes and fixes can be undone from the toast. Ticks follow their bookmark rather than their position. A row that changed since the report was read reloads the report instead of acting on stale data.

  • New
    Fetch previews on *Missing preview

    * walks the whole collection in batches behind a counting bar with Stop, waits out the rate limit instead of ending on it, and says so in its label.

  • Fix
    a tall row menu pinned itself to the top of the viewport

    when neither side of its row had room; it is clamped toward the row, as the right-click path already was.

Config

  • New
    Config → Bookmarks writes only the rows that change

    , moves refuse a URL already on the target page and say which ones stayed, the undo takes back only what that change did, and duplicating a page copies its bookmarks (a duplicated category comes without them — a page holds each link once).

  • New
    Fetch icons and Fetch previews for a selection

    in Config → Bookmarks, counting only the rows that need it, behind the blocking bar with Stop and a rate-limit wait. A sweep's results are written one page at a time.

  • New
    the link-preview refresh

    under Data & backups → Icons & previews can be stopped; what it fetched is kept.

  • New
    Keep links without filing them

    moved from Appearance → Header to Behavior → Inbox & Fresh, and now gates Keep in triage too.

  • Fix
    the config band's filter and *Only changed

    * were written after the panels were bound and never reached the config object.

Logs

  • New
    Record server log is a toggle in the log toolbar

    , beside Copy and Download, instead of a switch behind ⚙. Every line carries its own server sequence number, and recording with no refresh interval says the view will not update by itself.

Translations

  • Fix
    25 strings the code used had no locale key

    , so they showed in English in every language: the Keep, bulk-tag and undo toasts in the inbox, the health undo and restore toasts, the Config → Bookmarks move and duplicate messages, the kept list's duplicate line and no tag group, and the Kept widget's name, description, empty and loading text and open action. All six locales.

  • Fix
    the cheat sheet's r row had no label

    (ivMarkRead sat in dashboard.*, not dashboard.cheatsheet.*) and its ivKeep read "Mark as read"; both are in place.

  • Fix
    copy that still said r keeps

    — the triage hint, the inbox explainer, tour steps 4 and 9 and the tour's keycap — says r marks read and Shift+K keeps, in six locales. The server-log help and empty state name the renamed toggle.

Docs

  • Docs
    Config → Help → Inbox

    has a new The Kept tab panel, and the inbox, working, triage, settings, tour and Behavior panels describe Keep, the two tabs and the new switches; Help → Tips gains tipEditKeep and tipEditKeptPile. Six locales.

  • Docs
    static/data/whats-new/v1.12.0.json and its index entry

    , leading the What's new window: whats-new-stub.js's DASHBOARD_RELEASE moved to 2026.09-dashboard-release-v1.12.0, so every install sees it once, and NEXTDASH_WHATS_NEW_DATA_VERSION to whats-new-v295. v1.11.1–v1.11.8 lose hideFromModal and are shown under it, the way v1.7.0 released v1.6.1 and v1.6.2; v1.11.4's lead no longer mentions a test. tests/whats-new-hidden-release.spec.js asserts that nothing is held back and that each of them is reachable in the window. static/data/overview-features.json gains two spotlights with since: "v1.12.0" — keeping a link, and filing it where its site lives — with their keys in six locales. go generate refreshed asset_hashes_gen.go.

  • Docs
    MANUAL.md

    gains §14.5 The Kept tab (Settings moves to §14.6), and §8, §11, §13, §14, §15.4, §15.5, §17.4 and §18.1 follow the changes above; README.md mentions Kept and counts twenty-one widget kinds.

Only docs and tests changed in this release.

v1.11.8 Settings groups back in tiles, and the Glass depth trading its white light for the theme's own colour — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.7, so v1.11.0 keeps leading it. 2 fix

Settings groups back in tiles, and the Glass depth trading its white light for the theme's own colour — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.7, so v1.11.0 keeps leading it.

Config

  • Fix
    Appearance and Behavior drew every settings group as one flat list

    v1.11.6 put both sections on tabs and had config-tabs.css strip the box off each .config-panel: no border, no surface, no radius, a hairline underneath and the panel title reduced to a small muted heading. On a tab carrying eighteen settings nothing marked where one group ended, and a border is exactly the "separate object" cue a group of settings wants. The flattening rules are gone, so the tile comes from .config-panel in config-view.css and from theme-depth.css / theme-character.css as it does everywhere else in config — which is also why a custom theme now restyles these tiles without knowing about config-tabs.css. The column, the preview beside Appearance and the tighter spacing under a field hint stay.

Themes

  • Fix
    the Glass depth lit its surfaces instead of letting you see through them

    Three layers stacked: --glass-brightness raised the backdrop by six per cent on every pane, --edge-top and --edge-side are written as a percentage times --theme-depth and glass sets that to 1.5 (so a 16% line landed at 24%), and on a theme with sheen the gloss painted white at up to 20% across the head of each surface. Together a column of tiles read as a column of lighter boxes. Now, at data-depth="glass" only: brightness 1.06 → 1.012, the saturate() on the backdrop 1.4 → 1.8 through the new --glass-saturate (it was hard-coded in twelve places), the lit edges from 16%/10% to 7%/5% before the multiplier and their sheen term from 30% to 8%, and --surface-gloss redefined at about a third of its strength in --glass-gloss-light — color-mix(accent 45%, white) rather than white. On Gloss Obsidian [dark] (sheen 0.9) that is a top edge of 21% instead of 64%, and a gloss band of 7% instead of 20%. Every theme on Glass is affected, and every surface: the config tiles, the modals, the search window and the card layouts.

Tests

  • Fix
    config-bookmarks-panel.spec.js placed a caret with the End key

    , which on macOS scrolls rather than moving the caret inside a text field. The click before it left the caret mid-word, the tag was typed into the middle of the value, and the spec failed on macOS while passing on Linux CI. The caret is set with setSelectionRange; the typing stays real, since the draft has to be dirty and uncommitted when the next row is clicked.

Docs

  • Docs
    static/data/whats-new/v1.11.8.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v294, DASHBOARD_RELEASE untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.8 alongside v1.11.1–v1.11.7. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.7 The Log settings popover on screen and at its gear, and the Logs section versioned like the rest — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.6, so v1.11.0 keeps leading it. 2 fix

The Log settings popover on screen and at its gear, and the Logs section versioned like the rest — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.6, so v1.11.0 keeps leading it.

Logs

  • Fix
    the Log settings popover opened far from its gear, scrolled inside itself, and slid under the header

    It is position: fixed inside the log panel, and under the Glass depth .config-panel carries a backdrop-filter, which makes the panel — not the window — what "fixed" is measured from: the popover landed a panel's offset below and to the right of the gear, past the window's edge. bindLogSettingsPopover() now measures that frame's origin with a zero-size probe and takes it off. The popover is laid out in two columns with the labels beside their selects and no height cap (about 400px instead of 760px behind a 320px scroll box), so it is on screen whole; it opens under the gear, or over it, never under the sticky header band; when neither fits the page scrolls just far enough to make room under the gear, and a ResizeObserver places it again when the live note fills in. The panel is lifted above the band while the popover is open, for a window too low to keep clear of it. config-log-settings-popover.spec.js covers the placement, the absence of a scroll box, the band, and the popover drawing over the band — each confirmed failing without its part of the fix.

  • Fix
    the Logs section loaded without a version token

    dashboard-config-logs.js, split out of config, was missing from lazyLoadedAssets, so it loaded under its bare path and a browser went on running its old copy after an update. Listed now, and TestConfigSectionModulesAreLazyAssets fails for any SECTION_MODULES file left off the list.

Tests

  • Fix
    six specs still pressed Escape twice to leave config

    , once for the tiles and once to leave. With no start screen the first press leaves, and on CI the second landed while config was closing, so action-bar-position.spec.js failed to reopen config for its next placement. One press now (action-bar-position, config-dashboard-view, favicon-harmonization-default, header-action-overflow).

Docs

  • Docs
    static/data/whats-new/v1.11.7.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v293, DASHBOARD_RELEASE untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.7 alongside v1.11.1–v1.11.6. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.6 Config's Appearance and Behavior back on plain tabs, with a live preview beside Appearance — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.5, so v1.11.0 keeps leading it. +6 1 fix

Config's Appearance and Behavior back on plain tabs, with a live preview beside Appearance — held back from the What's new window (hideFromModal) like v1.11.1–v1.11.5, so v1.11.0 keeps leading it.

Config

  • New
    Appearance and Behavior open straight on their settings, in tabs

    The start screen of tiles (v1.11.0) and the split of each group into a few cards plus More settings are gone: an extra click in, a second layer inside, and settings that could only be found by guessing the tile. static/js/shared/config-hub.js and static/css/config-hub.css are removed; both sections draw renderSectionTabStrip() over one column of settings.

  • New
    the tabs were regrouped by what a reader looks for

    Appearance: Look (theme, surfaces, animations, type, background), Grid, Rows, Header (now also the clock placement, the browser tab's page name and the custom title and favicon), Action bar, Date & weather. Behavior: General, Keyboard & search (the keys moved in from General), Inbox & Fresh (the two thin tabs merged), Status & alerts, Privacy & sync (onboarding and Keep settings on this device only moved in from General). Panels move with an order field in behaviorSchema(), sorted stably in panelsFor(); the tab ids in addresses are unchanged, and fresh, branding, grid, look, rows, action-bar and the old hub names still open the tab that holds their settings now (APPEARANCE_TAB_ALIASES, BEHAVIOR_TAB_ALIASES).

  • New
    a live preview beside Appearance

    static/js/shared/config-preview.js draws header, grid, three sample rows and the dock from the current settings, in the page's own theme and font, and dims all but the part the open tab is about (data-preview-focus). Below 900px it stands above the settings.

  • New
    a short line under every setting

    fieldSummary() takes a declared hint, else the first sentence of the setting's ℹ text, so the line and the dialog cannot disagree; ten settings without ℹ text got a hint of their own.

  • New
    the filter and Only changed say where else they find something

    "Also found on: Header 2" under the list, per other tab of the section (renderFilterElsewhere(), countTabMatches()), keeps the filter when clicked.

  • New
    each section opens on the tab you used last

    , kept per browser (nextdash:config-tab-v1); the address now always names the tab, so a shared link opens what it shows.

  • Fix
    a setting promo pulled the reader back to Look

    Its "chosen on purpose" check only knew the tab strip, so Make your own theme… was undone a moment later by ensureSubTab. It now counts the page buttons and the Also found on buttons too.

Docs

  • Docs
    Help, tips and tours follow the new tabs in all six languages

    helpConfigBody, helpAppearanceBody, helpBehaviorBody, helpConfigKeyboardBody, helpHeaderBody, tipConfigHub and the What has changed tour's config step rewritten; every "Behavior → …" and "Appearance → …" pointer in Help, tips, tutorials, notices and hints renamed to the tab it lands on now (about forty strings per language), with the English fallbacks in the JS to match. The 37 hub* keys and eight tab labels nothing reads any more removed from all six locales. MANUAL.md §12 and §15 rewritten for the tabs and the preview, the rest of the manual's pointers renamed.

  • Docs
    static/data/whats-new/v1.11.6.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v292, DASHBOARD_RELEASE untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.6 alongside v1.11.1–v1.11.5. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.5 Overview news, shorter news dates and two Health row-menu fixes, held back from the What's new window (hideFromModal) like v1.11.1–v1.11.4, so v1.11.0 keeps leading it. +1 6 fix

Overview news, shorter news dates and two Health row-menu fixes, held back from the What's new window (hideFromModal) like v1.11.1–v1.11.4, so v1.11.0 keeps leading it.

Config

  • New
    the two newest nextdash.cc posts above the overview tiles

    renderOverviewSiteNews() takes the site posts from the stream About → News & features already loads (loadNewsStream), newest two, and draws them as a "Latest news" tile — the same stat-tile config-tile classes as the figures under it — one line each: title, clipped summary, date, and a link to the post. Nothing is drawn while it loads, when "Show posts from nextdash.cc" is off, or when the feed is unreachable. "Latest news" translated in all six locales.

  • Fix
    the overview's intro line showed twice once the news arrived

    _fillShellHeadFromSection() lifts a section's .config-view-intro into the header band, but repaintOverview() — the repaint the news arrives with — re-rendered the body without lifting it again, so the sentence stood in the band and above the tiles. The repaint lifts it now.

  • Fix
    news dates say which day

    Overview and About → News & features used the header's full date line, so under "weekday only" every row read "Friday". formatShortDate() gives day and month in the reader's date format — 18/09, 18-09, 09/18, 09-18; the two word formats follow the interface language — with the year only when it isn't this one.

  • Fix
    the release What's new opens on dropped out of About → News & features

    The stream shows the newest five releases (RELEASES_IN_STREAM), and five hidden patch releases (v1.11.1–v1.11.5) filled it, pushing out v1.11.0 — the release the modal still leads with. buildStream() now always adds the newest release not flagged hideFromModal. Caught by config-overview-release.spec.js on CI.

  • Fix
    the first keys typed after leaving config could be lost

    When a setting had just been changed, closeConfigView() waits for its save before bringing the grid back; until then the view still read as config and the control just changed still held focus, so > and the start of a query went nowhere — under load, whole words. It now marks the dashboard as leaving (_leavingConfig, which search's view guards read) and lets go of that focus straight away; the grid still waits for the save. Found through config-server-log-level.spec.js on CI, where a search typed as zzz-search-on arrived as on; reproduced locally under CPU throttling.

Health

  • Fix
    a row's menu pinned itself to the top of the viewport

    When a tall menu (many repair options) had no room above or below its row, toggleMenu()'s fallback set it flush against the top margin wherever the row was, drawing it over the header and everything down to the row. It now clamps toward the row, as positionMenuAtPoint() already did for right-click.

  • Fix
    the sticky header band drew over an open row menu

    .lvs-header's z-index was lifted by 1300 to clear the teaching popovers, while a row with an open menu stayed at --layer-row-raised (6). The row now sits one above the header while its menu is open.

Docs

  • Docs
    static/data/whats-new/v1.11.5.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v291, DASHBOARD_RELEASE untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.5 alongside v1.11.1–v1.11.4. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.4 One real fix and one test correction, held back from the What's new window (hideFromModal) like v1.11.1–v1.11.3, so v1.11.0 keeps leading it. 1 fix

One real fix and one test correction, held back from the What's new window (hideFromModal) like v1.11.1–v1.11.3, so v1.11.0 keeps leading it.

Search

  • Fix
    a search reached from the address bar or a bookmarked #search?q=… query could be silently dropped

    search.js loads lazily on first use; dashboard.searchComponent is only guaranteed to exist once that bundle has loaded and initializeSearchComponent() has run. Both hash-routing paths in dashboard.js (routeFromHash()'s #search branch and the window.__nextdashBootSearch boot-query consumer) called this.searchComponent?.openSearchWithQuery?.(query) directly — reaching either one before the bundle loaded made the optional chain no-op, and the boot-query path had already deleted window.__nextdashBootSearch by then, so nothing was left to retry once the bundle did arrive. Both now go through SearchLoader.ensureReady(), the same load-then-open pairing loadThenOpen() already used for a keypress that beat the bundle. Reproduced locally at roughly 1 in 4–6 runs of tests/opensearch.spec.js; 10/10 clean after the fix.

Tests

  • Fix
    two more flaky assertions, found chasing unrelated CI failures on the runs for v1.11.2 and v1.11.3

    tests/opensearch.spec.js's two arrival tests were missing the dismissBlockingOverlays() call their sibling test already had. tests/config-tag-suggestions.spec.js's "applying a suggestion leaves the rows you ticked ticked" checked cfg.bmSelected once, right after a tag-count poll that only proved the tag mutation had landed — the selection-preserving step is separate work on the same refresh and wasn't part of what that poll observed. Not reproducible locally after 15 full-file runs; converted to expect.poll(), same class of fix as the dashboard-merged-header.spec.js correction in v1.11.3.

  • Fix
    a flaky toggle click in tests/toolbar-button-toggles.spec.js, found chasing the CI failure on the run for this release

    "the setting is offered in Appearance and applies without a reload" clicked the showCollapseAllButton checkbox with toggle.click({ force: true }), which still resolves the element and clicks it over two separate round trips through the Playwright protocol — a window this self-rebuilding data-behavior-special="chrome" control landed a rebuild inside under CI load ("element was detached from the DOM, retrying"), eventually exceeding the 30s test timeout. Replaced with a page.evaluate() click, which queries and clicks the element in one synchronous in-page step and so has no gap left to race. 5/5 clean locally after the fix, where it had flaked before.

Docs

  • Docs
    static/data/whats-new/v1.11.4.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v290, DASHBOARD_RELEASE untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.4 alongside v1.11.1–v1.11.3. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.3 One addition and one internal fix, held back from the What's new window (hideFromModal) like v1.11.1 and v1.11.2, so v1.11.0 keeps leading it. +1

One addition and one internal fix, held back from the What's new window (hideFromModal) like v1.11.1 and v1.11.2, so v1.11.0 keeps leading it.

Availability checking

  • New
    a corner card offers to switch every unchecked bookmark to Periodic at once

    Once 20 or more bookmarks have no availability checking at all (CheckMode.of(bm) === CheckMode.OFF — neither checkStatus nor monitor), unchecked-bookmarks-notice.js offers to switch them all to Periodic in one action, naming the count. It builds an explicit {pageId, index, url} target list from each affected page's current bookmark order and calls the existing POST /api/health/check-mode-all — the bulk endpoint deliberately refuses to turn checking on without one, so this does not ask the server to touch "everything". Shown at most once a month (localStorage, no server setting); a first "No thanks" brings it back next month, a second offers "Don't ask again" for good. tests/unchecked-bookmarks-notice.spec.js covers the threshold, the monthly gate, the escalating actions and a real accept round-trip.

Tests

  • Fix
    a flaky header-shift assertion in dashboard-merged-header.spec.js

    waitForTimeout(900) sampled the header's measured positions once at a fixed delay, racing whatever layout/paint work follows the awaited openInboxView() rather than waiting for it — the same commit produced a different value on every CI retry. Replaced with expect.poll(), which waits until the measurement stops changing instead of guessing how long that takes.

Docs

  • Docs
    static/data/whats-new/v1.11.3.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js's NEXTDASH_WHATS_NEW_DATA_VERSION moved to whats-new-v289 so a browser holding the old index learns this one exists, DASHBOARD_RELEASE is untouched. tests/whats-new-hidden-release.spec.js now pins v1.11.3, v1.11.2 and v1.11.1 as held back. Config → Help's Availability & health panel and the "Keeping it healthy" tips group mention the card; MANUAL.md §13.1 does too. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.2 Two corrections to how a docked action bar comes and goes, held back from the What's new window (hideFromModal) like v1.11.1, so v1.11.0 keeps leading it. 2 fix

Two corrections to how a docked action bar comes and goes, held back from the What's new window (hideFromModal) like v1.11.1, so v1.11.0 keeps leading it.

Dashboard

  • Fix
    a docked action bar that slid away stays away while you switch page or view

    A hashchange listener in action-bar-autohide.js called show() on every navigation, so each page switch brought the bar back, and moving through pages faster than its delay kept it on screen for good. The listener is gone: a load, the pointer at the edge, focus moving into the bar and ' / Shift + O bring it back, and once back it keeps its delay. action-bar-autohide.spec.js switches page with a digit key and walks Health, the Inbox and config with the bar away.

  • Fix
    a docked bar brought back with ' or Shift + O stays until you are done with it

    The key called show(), which armed the same timer as the edge, so the bar slid off again after the delay while the reader was still reaching for it with the keys. action-bar-autohide.js now pins a bar the key brought back: no timer runs until the key is pressed again (which sends it away at once) or the pointer has passed over the bar and left it, which hands it back to the delay. The edge, the handle and a reload keep the delay as before. action-bar-autohide.spec.js holds a key-called bar for 3.5 s, and lets one go once the pointer has passed over it; the test that checked the delay after ' now calls the bar from the edge.

Docs

  • Docs
    static/data/whats-new/v1.11.2.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js is untouched, so the window does not reopen for it. tests/whats-new-hidden-release.spec.js pins v1.11.2 and v1.11.1 as held back and v1.11.0 as leading. MANUAL.md says that switching page or view leaves a slid-away bar where it is, and that a bar called by a key stays until the key again or the pointer has passed over it. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.1 Corrections to v1.11.0, and the specs brought up to the header, the tile hub and the new defaults it shipped with. 10 fix

Corrections to v1.11.0, and the specs brought up to the header, the tile hub and the new defaults it shipped with. Held back from the What's new window (hideFromModal), so v1.11.0 keeps leading it.

Dashboard

  • Fix
    the corner cards have buttons again

    Dropping the first-run setup window (8e011f63) took the .quickstart-btn rules with it, and NoticeCard still draws every card's actions with that class — Fresh, the tour of what moved, clock and weather, and the analytics and theme-browser notices, which build theirs by hand. Each fell back to the browser's own grey buttons. The rules are back in dashboard-quickstart.css, beside .notice-card-actions.

  • Fix
    a card's primary button and a finished quick-start step are drawn in the page's colour on the accent, not in white

    White on a light accent fell under 2:1 — 2.1 on Tarnished Brass, the new default — and under 3:1 on 111 of 242 themes. --background-primary is what every other filled accent button uses, and it clears 3:1 on all of them.

  • Fix
    the filter bar lies over the grid it filters

    With packed columns off the grid is a fixed number of fixed-width columns centred in the container, and the bar spanned the container: in a 1500px window it stood 90px left of the rows and 180px wider than them. dashboard-grid-filter.js measures the grid and hands the width and offset to the stylesheet as custom properties.

  • Fix
    * and / work whether or not their buttons are on screen

    Switching the tag-cloud button off took the tag cloud with it, so / fell back to the search panel's tag mode; the setting now only decides whether the button is drawn.

  • Fix
    Escape stays inside an open widget or category menu

    Menus from the shared _openMenu builder carry bookmark-context-menu only as a class, so the check by id missed them: the menu closed itself, and the key went on to _escapeFallback(), which opened search a tick later.

  • Fix
    the page overview opens with its cursor on the page you are on

    .focus() ran while the overlay was still visibility: hidden and did nothing, so AppModal's own deferred pass focused the first row; the modal now places the cursor once it is on screen.

Config

  • Fix
    a hub tile names a setting once

    The form's labels end in their own colon, so the summary printed Weather location:: Leiden and 3 columns per row: · Compact. config-hub.js strips a trailing colon (full-width included) before composing the line, and the time format is named in front of its value: its options are examples, and 23:59 on its own read as a clock stuck at one minute to midnight.

Search & commands

  • Fix
    :rows and :highlight are two commands again

    search-commands.js had two methods called handleRowHighlightCommand; the second replaced the first, so :rows never ran its own code and both words reached the older one. Each has a name of its own now, and both set the row highlight.

Health & Inbox

  • Fix
    the header band is opaque, at rest and once scrolled

    Rows passed visibly behind it on glass themes, which its own comment said should not happen.

Browser extension

  • Fix
    the extension's bookmark form shows a row's status colour like the app does

    The preview read an absent setting as off; it is !== false now, like its neighbours.

Docs

  • Docs
    the specs follow the one-row header, the tile hub and the v1.11.0 defaults

    Every spec gets a window wide enough to show the header's destinations, and the ones that need a narrow window open Health and the Inbox by key rather than by a link that has folded away. Waits were added for what a spec reads next — a whole command, an underline that fades in, the group a field sits in.

  • Docs
    the CI shards are sized by measured speed, not test count

    , and the shard weights went again once the slowness they answered turned out to be a timeout. The manifest spec stopped racing its neighbours for one settings file, and the widget-drift specs keep a window their page still scrolls in.

  • Docs
    regression specs for this release

    config-hub.spec.js checks the tile summaries for a doubled or dangling colon and a named time format; dashboard-fresh-notice.spec.js checks that a card's buttons are drawn by the card, with page-coloured ink on the accent. Both fail against v1.11.0.

  • Docs
    new README screenshots, taken from v1.11.0 with demo data

    The ten PNGs in screenshots/ showed a real install on a teal theme from before the one-row header; eight JPGs replace them — dashboard, search, inbox, health, monitoring, the bookmark workbench, the config tiles and the Gloss themes — shot at 1920×1200 on Tarnished Brass from a data directory of public sites only. Statistics, the cheat sheet and the separate widgets shot are gone (the widgets stand on the dashboard shot now); the workbench and the config tiles are new. Each has a few lines of description under it in README.md, and the Unraid template points at the same eight files.

  • Docs
    static/data/whats-new/v1.11.1.json and its index entry, flagged hideFromModal

    ; whats-new-stub.js is untouched, so the window does not reopen for it. tests/whats-new-hidden-release.spec.js pins v1.11.1 as held back and v1.11.0 as leading. go generate refreshed asset_hashes_gen.go.

Only docs and tests changed in this release.

v1.11.0 A hundred and twenty-six changes across 269 files, +38,395 / −17,736 lines, and one question behind most of it — where does a thing live. +41 23 fix

A hundred and twenty-six changes across 269 files, +38,395 / −17,736 lines, and one question behind most of it — where does a thing live. The buttons floated over the grid on a bar with no home; the page tabs, the clock and the view's name each owned a band of their own; config opened on a wall of every setting at once; and the bookmark list was a table with a dialog on top of it.

Header

  • New
    one header row, in three zones

    The clock and the page's name on the left, the page tabs in the centre, the destinations and the actions on the right. The name folded into that row and the 60px band it used to own is gone; the bar sits at the top of the page with the grid's air underneath it rather than a rule.

  • New
    the page switcher is a choice of four

    Numbers beside the destinations (the default), one segmented control, plain text tabs, or one button with a list of its own. :switcher tries them without opening config.

  • New
    page tabs shown before “+N”

    , 3 to 9, five to begin with. What does not fit is counted rather than dropped, and every page keeps its digit key whether its tab is drawn or folded.

  • New
    the clock and the weather stand where you put them

    : beside the view name, in a column of their own, or on their own line with the name underneath — the old top of the page, offered back as a third placement and what every install now starts on. They are drawn to be read rather than to fill a band.

  • New
    the header folds in one order as the window narrows

    , so the page switcher and the destinations are the last things to go, and the actions fold away before them.

  • New
    plain or plated header controls

    Plain underlines what is current; plated gives each control its own box. Under plated the action buttons and the page tabs stay bare — a box inside a box read as a second bar.

  • New
    a dashboard destination beside inbox, health and config

    , the pages button became one of the action buttons, and the inbox and pages buttons can each be switched off with their keys still working.

  • New
    the header sheet is one shape two panels can wear

    , and the launcher header is drawn from it.

  • Fix
    the header controls carried a ring around their key chips

    , the chips were dimmer than the labels beside them, and the action glyphs were a weight heavier than the buttons they stood in. Contrast measured on every theme.

  • Fix
    the view header is painted solid while the page moves under it

Action bar

  • New
    the fixed buttons have a place of their own

    A column on the right (the default) or the left, a dock at the bottom, in the header, or behind one menu — Config → Appearance → Action bar, or :buttons. The floating bar they used to sit on is gone, and a side column takes its room from the page margin rather than from the grid.

  • New
    a docked bar slides into its edge

    After 2 seconds by default, or 5, 10, 30, or never. It comes back when the pointer touches that edge, when focus moves into it, and on ' or Shift + O — and a bar you are using never leaves while you are using it.

  • New
    a handle marks the edge a bar slid into

    Quiet at rest, larger and clearer as the pointer nears, and a click on it brings the bar back. None in the header, behind the menu, or on a touch screen.

  • New
    every action button is on to begin with

    , and up to nine stand before the fold. What the header cannot show goes behind one control whose menu names each action with its key, down to two actions on a narrow window.

  • New
    the key on a button is a chip you can switch off

    , and with the chips off, resting on a button shows that button's key beside it. A new install starts with the chips on; a dashboard that already existed starts without them.

  • New
    the setting is named for what it moves

    : Where the fixed buttons stand, with the action cap on the same tab and Header & buttons ahead of it.

  • Fix
    the tag cloud opened under a docked bar

    , and its own wrap is shown when it opens.

  • Fix
    the popovers on the action buttons are gone

    A tooltip on a button that already carries its key is a second label.

Pages and panels

  • New
    the pages panel is drawn the way recent bookmarks is

    , with New page as a button rather than a dashed row, and a page can be deleted from it — asked twice.

  • New
    recents answer one word with every kind and are drawn as tiles
  • Fix
    the grid takes the focus back when the tag cloud closes

    , and when search closes.

  • Fix
    the pages panel and recents left the header

    ; both open from the search panel, which is where the rest of the modes already live.

  • Fix
    the pages panel opens with the cursor on the page you are on

    It was placed before the panel was visible, where it does nothing, so the first arrow key walked from page one.

Bookmarks → List

  • New
    the list is a workbench

    : filters in a rail on the left, the rows in the middle, an edit panel on the right. Specced, planned and built on a model of its own.

  • New
    the panel edits one bookmark or a selection of them

    , with tag suggestions in it and the monitor interval beside them.

  • New
    rows are slabs, picked from the keyboard

    , with whole favicons rather than cropped ones, the pin drawn where it belongs, room for the name, and the tags that do not fit counted rather than dropped. The shortcut column is gone.

  • New
    Shift + E opens the full dialog from the list
  • New
    on a narrow screen the rail folds into a drawer and the panel into a sheet

    , and the rail is drawn whole without scrollbars.

  • Fix
    the panel keeps its place after a move and after a bulk edit

    , its header is readable, and a folded panel gives the row its width back — with the pin shown only in the folded list.

  • Fix
    the old list controls are gone

    , and the code behind the list was tidied with its dialog tests restored.

Config

  • New
    Appearance and Behavior open on a hub of tiles

    A tile opens its group, Escape goes back, the two to four settings a group leads with are cards, and everything else is behind More settings — specced first, then built.

  • New
    config is drawn the way health and the inbox are drawn
  • New
    every appearance setting has an explanation, a default and one kind of control
  • New
    Date & weather moved to Appearance

    , and the weather location is a card of its own rather than a field behind More settings. It saves while it is typed, so the line answers as the town is written.

  • New
    the overview is rebuilt around the collection
  • Fix
    Toolbar & tabs is called Header and buttons

    , which is what it sets.

  • Fix
    :rows reaches the row highlight

    Two commands were written with the same name, so the second quietly replaced the first and :rows had never run; both words work now.

  • New
    config fetches a section when you open it

    dashboard-config.js was 27,627 lines pulled down whole to draw one section; Logs and Help are files of their own now, loaded on demand through one SECTION_MODULES table, with the rest fetched on idle after the first paint.

  • Fix
    Only changed shows that it is pressed

    The bar sits in the view head and the repaint that applies the filter replaces only the body, so the button kept the aria-pressed it was drawn with: the rows narrowed and the control went on reading not pressed to a screen reader and to its own styling.

  • Fix
    the changed-settings count is gone from the overview

    The overview was rebuilt around the collection and stopped drawing it; the click handler and openChangedSettings() behind it were left standing and have been removed. Only changed per tab and Reset panel per group are unchanged.

Logs

  • New
    Logs is a section of its own

    , split into the server log and the activity trail, each beside its own settings.

  • New
    the activity log has format, URL, sampling and age

    , and channels for search, keys, navigation, sessions and client errors, hooked into the handlers that already existed.

  • New
    how a bookmark was opened is recorded

    , with a detail level for open records.

Appearance

  • New
    a fresh install starts on Tarnished Brass, in glass with a soft glow

    , the theme's own backdrop and the contrast that reads as Normal. An install that already answered those questions keeps its answer.

  • New
    glass reads as glass and the glow is a dial

    , with what a theme ships on settled rather than left to drift.

  • New
    ten Gloss families, and a sheen any theme can have

    They carry a lit band and a badge in the theme browser; the Gloss slider in the theme editor gives the same sheen to a theme of your own or to a recoloured packaged one.

  • New
    a custom theme can set everything a packaged theme can

    — depth, glow, glass, corner radius and sheen — and comes as a light and a dark half, like the built-ins.

  • New
    the widgets take the page's colour

    A tile was a step up the surface ladder with a cast shadow, which on every theme read as a grey-white panel pasted on the dashboard. It is the page's own colour one step off it now, its cells one step further; under glass it is see-through and blurred, with the lit edge back.

  • Fix
    a theme lost its character when its colours were saved

Dashboard

  • New
    a tour of what moved

    A card in the corner offers it once — Show me, Later, No thanks — and eight steps say where the pages, the action buttons, config, the list, the widgets, the tags and the themes are now. Where a default changed the step carries the choice, so the old arrangement is one click away, and Show me lights up the real thing on the page behind it. Reopened from Config → Help → Guided tours or :changes; the release notes stay where they are.

  • New
    the corner asks for a town, a clock and a unit

    , once, and the weather line is on to begin with on a fresh install.

  • New
    Escape on a bare grid goes home, then opens search
  • New
    a bookmark opens by its own key while the cursor is on the grid

    , and a row says when it is being waited on.

  • New
    the health trend widget is drawn like the health view's summary tile

    , with the same figures and the same words.

  • Fix
    the first-run setup window is gone

    A window of questions before the reader has seen the dashboard they are about asks for answers nobody can give yet; the checklist in the corner stays, and every setting it used to ask for is in config.

  • Fix
    the ★ moved to the bottom-right corner

    , the cards in the other corner stand at the bottom edge, the toast stands with them, and the old corner button is gone.

  • Fix
    the health trend widget drew itself twice

    when two renders overlapped.

  • Fix
    * and / work whether or not their buttons are on screen

    Each used to open something different depending on whether its button was switched on — * the recents sheet or the panel's recents mode, / the tag cloud or the panel's tags. A keyboard shortcut does not answer to a setting about chrome. Show the tag-cloud button now only hides the button; it no longer switches the cloud off.

  • Fix
    Escape stays inside an open widget or category menu

    The menu closed itself correctly and a moment later the search panel opened anyway and took the focus, because the guard listed the popovers written one at a time and not the ones the shared menu builder makes.

  • Fix
    the filter bar lies over the grid it filters

    With packed columns off the grid is a fixed-width set of columns centred in the page, so above about 1280px the bar sat to the left of the rows it was filtering and ran wider than them.

  • Fix
    the quick-start checklist can finish

    Open Config was ticked by a click handler on a header link that stopped existing when config became a view of its own, so nothing ever set the flag and the step asked for something you had already done. It reads the open view now.

  • Fix
    the spread card, the settings-search promo and what was left of the side rail are gone

    , along with the button style they described.

Inbox and health

  • New
    Select all in the ⋯ menu of both views

    It ticks every row the current filter shows and reads Deselect all once they all are, so the whole bulk bar is reachable without knowing the Ctrl/Cmd + A chord. Ticks made under another filter are left alone, the way they already were.

  • Fix
    the health and inbox header is opaque again

    It is a sticky band, so the rows were passing through it rather than behind it while you scrolled. The stylesheet said as much in a comment beside the rule that did the opposite.

Docs

  • Docs
    the config help and the tips are rewritten for the app as it is

    , with an Appearance tab and a Logs tab, and old links to panels that moved still land on them.

  • Docs
    the manual is rewritten for the current app

    , and the readme and the compose files list the newer variables.

  • Docs
    the help, the tips and the new strings are translated into all six languages

    , the strings the other languages still showed in English are gone, and so are the keys nothing uses.

  • Docs
    the manual, the help and the tips carry the action bar's defaults

    , the tour, and the key that appears on hover.

  • Docs
    the release notes, the overview stream and About → News & features carry v1.11.0

    , with five spotlight entries (the fixed buttons' placement, the one-row header, the list workbench, config's tiles, and Gloss) in all six languages. The manual documents the guided tours, and Help and the tips name Select all in health and the inbox.

  • Docs
    the config split carries its own gates

    : a census over every member of DashboardConfig, an extractor that moves a section verbatim and proves it byte for byte, a planner that works out which members a section actually owns, and a smoke spec that walks every section. npm run test:config-split pins the three mistakes they were built from.

  • Docs
    the config specs follow the new header and the tile hub

    , which they had drifted from: the destinations fold below 1500px, Behavior and Appearance open on tiles rather than fields, and the breadcrumb was replaced by the section's own description.

  • Docs
    the test suite runs in a window wide enough to use

    Playwright opened 1280px wide, the header folds its destinations away below about 1500, and every click on the inbox or health button waited its full thirty-second timeout — 552 of them in one run, which made the health and inbox families look slow when they were only waiting. The slowest CI shard went from 49 minutes to six, and the shard weights added to work around it are gone again.

  • Docs
    a Go test no longer races its neighbours for one settings file

    It wrote a theme and read the manifest back in parallel with the backup tests, which write themes of their own into the same store; it began failing when the default theme changed.

Only docs and tests changed in this release.

v1.10.0 Changes in Appearance, Panels, Search & commands, Config, Health & Inbox and Dashboard. +18 13 fix

Changes in Appearance, Panels, Search & commands, Config, Health & Inbox and Dashboard.

Appearance

  • New
    one layout, and layoutVersion is gone

    Classic and modern were two dashboards to keep in step, and half of what modern did better never reached anyone who had not found the setting. The row treatment, the mode pills reading as one switch and the thickness under config's panels were carried onto classic first; the modern branch was then folded away, taking data-layout-version with it and leaving one set of rules per surface. A stored layoutVersion: "modern" migrates to rowHighlight: "strong" so an install that chose the stronger highlight keeps it — the setting is now its own, under Appearance, rather than a side effect of a layout nobody was otherwise choosing.

  • New
    glass is three tiers, derived per theme

    A page, a panel and an overlay each blur by how much has to be read through them (--theme-surface-alpha, --theme-surface-blur), and each theme works its own glass out of its own palette rather than sharing four hand-written character themes' values. Picking glass now does something on every theme.

  • New
    one rung of the surface ladder is worth what the palette has room for

    themeSurfaceStep scales --surface-1..3 by the distance a theme leaves between its page and its ink, anchored on retro-crt-dark's measured 0.828. Three per cent of an ink that sits close to its ground is not a step anyone can see, and the collection had 182 of 222 themes on one value before the slope replaced the threshold.

  • New
    a theme answers for its fourth colour

    --accent-info is derived as the hue furthest from success, warning and error, so a surface that needs a fourth signal no longer borrows one of the three that already mean something.

  • New
    depth, text contrast, theme backdrop, backdrop, favicon harmonisation and style apply without a reload, and are in the command palette

    The controls carry special: 'chrome' / 'chromeRender' so the change reaches the page as it is made.

  • Fix
    the edge tokens were restated, so raising depth did nothing

    theme-character.css loads after theme-depth.css and redeclared --edge-light at a flat 6%; the lit edge is --edge-top now and character composes with it rather than overwriting it.

Panels

  • New
    the overlays are one design

    Search, the cheat sheet, recent bookmarks, the tag cloud, the bookmark form and the context menus are drawn from the same vocabulary: an 8px corner, the two edges, a real drop, the panel's name with the key that opens it beside it, and a way out on the right. The wide Close button and the duplicate ESC hint under it are gone from each.

  • New
    recent bookmarks is a narrow panel of quiet rows

    760px of outlined cards became a 440px list: a favicon rather than the row's own position in the list, the category inline behind the name, the time as text rather than an accent pill, and every row in one slab instead of one box each. The foot says how many are shown and what Enter does.

  • New
    a cheat sheet row ends in its key

    The key led the row in a column 40% of its width, so the reader scanned keys to find the thing they wanted. The header carries ! and the way out; a pinned foot counts the shortcuts.

  • New
    the bookmark form is a sheet with three grounds

    The sheet lifts off the page, the two groups (what it is, where it goes) lift off the sheet, and the fields are cut back down into them — the arrangement was upside down, with eleven raised fields on a sheet painted the same colour as the page behind it. The groups are equal-height boxes at every width, the actions are pinned to the foot, and only the button that saves is filled.

  • New
    the context menus joined the depth ladder

    .move-popover is the one surface every menu wears — bookmark, category, config, check-mode, and the move, tag and delete pickers — and it drew the same flat box at rich, glass and flat alike, with a 10px corner and 0 4px 18px of --text-primary at 14%, which on a dark theme is a halo under the menu rather than a shadow. Edges, a black drop and the theme's own light now, and no backdrop-filter at any depth: blur on a menu is what gave Safari a composited layer that hit-tests in front of what it covers, which is why .health-view-menu lost its own.

  • Fix
    a panel inherited the previous one's header

    One #app-modal serves every panel and show() only ever replaced the title, so opening What's new after the cheat sheet left two Esc × buttons and a ! chip naming a panel already closed. Callers mark what they add with data-modal-header-extra; show() clears it.

  • Fix
    the What's new chrome rule hid another panel's buttons

    The analytics notice borrows the same shell (modalClass: 'whats-new-modal analytics-notice-modal'), so hiding the action row by class took its Turn on button with it — a panel whose whole purpose is that button. The rule is scoped to :has(.wn-content), the release notes' own body, which only the panel it is about renders.

  • Fix
    the first-run card covered the buttons in its own corner

    The Quick setup card is fixed bottom-left at z-index: 2147482800; the tag cloud and What's new buttons sit at 1002 and 1001. elementFromPoint in the middle of the What's new button returned .quickstart-actions. The card clears two rows of the corner stack now.

Search & commands

  • New
    one door to the command panel

    Search, commands and finders are one surface with a mode switch, so >, : and ? open the same panel in the mode asked for, and the mode keys keep working once it is open.

  • New
    the search overlay is drawn to the command-surface spec

    Container padding 0 with a --radius-5 corner and a 24/64 drop, a prompt row with a rule under it, uppercase prefix chips, tighter matches, and a plate under the mode tabs so the rule above them spans the sheet.

  • New
    a command can carry a URL
  • Fix
    ? swallowed what you typed next, and shouted it back

    The finders opened without taking the input, and the query was upper-cased on the way back out.

Config

  • New
    Appearance and Behavior are laid out in blocks, one subject each
  • New
    the overview is about the collection, and the news has a page

    The stream moved to About → News & features, which carries the unread count, the dates and the per-source filter. The foot that says why a source is missing and the marker that clears the dots moved with it.

  • New
    config's statistics and a widget readout are one component

    StatTile.build/.html in static/js/shared/stat-tile.js, with one set of rules for the figure, the caption and the delta; the two had drifted to upper case at 0.06em in one place and normal case at 0.03em in the other.

  • New
    a delta says which way it moved, and the rules are the same everywhere

    A directional delta (a state got better or worse) takes success or error; a neutral one (a count moved) stays quiet, because one fewer bookmark is smaller, not worse.

  • Fix
    the finders and commands buttons had two defaults

    Folding the three doors into one panel set both to false in defaultSettings, while the normaliser still flipped an absent key to true — so a fresh install got one answer and every upgraded one the other, and the client's own FIELD_META agreed with the second. All three say false now; both are one toggle away in Config.

  • Fix
    four settings nothing read are gone

    , along with the locale keys for what was removed: showSearchButtonText, showFindersButtonText, showCommandsButtonText, showDockLayoutSelector, configGeneralLayer and configGeneralPanels.

  • Fix
    the appearance settings are in the command palette

Health & Inbox

  • New
    the shell header takes its colour from the theme

    It was --background-primary with a hairline under it — a black band across the top of a dark theme, a white one on a light theme, and the one element on either page that took nothing from the theme. It wears the dashboard widget's shape now, mixed into --background-primary rather than into transparent because it is sticky and the rows have to pass behind it.

  • Fix
    row density was two settings with opposite defaults

    The dashboard read densityMode off the server and defaulted to compact; the list views kept their own value in localStorage and defaulted to comfortable, while list-density.js's own comment said it was "one setting for the whole app". ListDensity is a front for densityMode now, feed rows key off data-density-mode, and a value stored by the old module is carried over once and the key removed.

Dashboard

  • Fix
    a toast landed on the button bar
  • Fix
    a promo card printed <kbd>…</kbd> as text

    instead of drawing the key.

  • Fix
    the glass step frosted the cards behind an open inline form

    Every .category and widget body carries a backdrop-filter on glass; measured with a form open, five cards at blur(17px) fell across it, each its own compositing layer at opacity 1.

  • Fix
    the health link shimmer uses the theme's own colour

Docs

  • Docs
    the release round for v1.10.0

    static/data/whats-new/v1.10.0.json and the index entry ahead of it, both tokens in whats-new-stub.js (DASHBOARD_RELEASE, NEXTDASH_WHATS_NEW_DATA_VERSION → whats-new-v285) and the constants they are pinned with in tests/whats-new-hidden-release.spec.js. Three spotlights with since: "v1.10.0" in overview-features.json — the one layout, the panels naming their key, and news getting a page — each with its five locale keys in all six languages, so the overview stream and About → News & features carry the release. helpVersionBody names 1.10.0 in six languages, MANUAL.md follows the settings that moved or went, and go generate refreshed asset_hashes_gen.go.

  • Docs
    thirty keys that lived only in the code were translated

    , a vocabulary that never existed was collapsed, and the new panel strings (bookmarkGroupWhat, bookmarkGroupWhere, recentShowing, recentFootOpen, cheatsheetCount, cheatsheetFootClose, whatsNewFootClose) got their keys in en, nl, de, fr, zh and es.

  • Docs
    sixteen permanently skipped tests were removed from tests/config-bookmarks-editor.spec.js

    Each was an empty shell with a comment claiming the behaviour was covered elsewhere. Two of those claims were false: the modal's __new__ category flow exists and is covered by bookmark-form-create-page-category.spec.js, and nothing at all covered the favicon fetch — tests/bookmark-icon-fetch.spec.js now does.

  • Docs
    the specs follow the panels that went

    config-appearance-layout-order, dashboard-category-spacing, config-custom-themes, config-field-grid-and-mobile-nav and config-view-performance described a Layout version panel, a sixth appearance tile and a spotlight carousel, none of which this release leaves standing. config-overview-release and config-overview-news follow the stream to About → News & features, and scope to the dated panel because About draws the back catalogue with the same row class.

  • Fix
    a preview test counted other rows' requests as its own

    preview-card-image-arrives-live stubbed every /api/bookmark-preview call and stepped one counter, so a preview asked for any other bookmark on the page spent the "first answer is pending" the test turns on, and the row under test got the finished picture on its first ask. The stubs answer for the bookmark under test and let the rest through.

  • Docs
    the design working files are kept out of the repo

Only docs and tests changed in this release.

v1.9.0 Changes in Config, Dashboard and Appearance. +3 7 fix

Changes in Config, Dashboard and Appearance.

Config

  • Fix
    the sub-tab labels under Structure were lowercase

    categories · pages · finders · collections sat beside Bookmarks' List · Tags · Tag suggestions, which are capitalised, and the strip read as two designs on one screen. The five locale strings behind them carry a capital now; the breadcrumb lowercases what it shows, so config › structure › finders is unchanged.

  • New
    Pages & tags is Structure, and Tags is a Bookmarks tab

    The section holds what a collection is filed in — pages, categories, finders, collections — and a tag is not that: it is a word a bookmark carries, which is why the other tag panels (suggestions, your rules) were already under Bookmarks and this one sat a section away from them. Tags now sits between List and Tag suggestions, keeping its word cloud, its filter and its ↑/↓ row cursor rather than taking on the j/k of the bookmark list beside it. The section's new name is one word, like every other name in the rail: Pages & tags described two of its five tabs, and with Tags gone it described one of four. Links handed out before this keep working: #config/pages-tags lands on the renamed section, #config/pages-tags/tags on the tab in its new home, and /config?section=tags redirects to #config/bookmarks/tags. The address bar is rewritten to the current name, so the next link copied is the new one.

  • New
    Appearance sits above Bookmarks in the rail

    It moved under Bookmarks in v1.3.3, when the rail was ordered by how often a section is opened. Ordered that way it is in the wrong half: Appearance, Structure and Behavior say what the dashboard is, and Bookmarks is the collection it shows. Appearance now opens the list of the three, and the deep links are unaffected — the rail's order is not part of any address.

  • Fix
    a long section name wrapped the rail button onto two lines

    The rail is a fixed 200px column, so a name never widened it — it broke across lines, and one two-line button in a column of one-line buttons makes the whole rail look ragged. Every translation of a name is a different length, so rather than keeping each one short enough for the widest language, a button now holds itself to one line and shortens with an ellipsis, with the full name on hover.

  • Fix
    every deep link into a Bookmarks tab opened List

    subTabFromHash refused the section outright, because the segment after /bookmarks/ is usually a page filter and reading a page id as a tab name would have opened a tab that does not exist. A page id is a number and a tab is a word from a known list, so the two can be told apart — #config/bookmarks/settings, /local-copies and the rest now arrive where they say, and a reload keeps the tab it was on.

  • Fix
    the finder rows split their width three ways, so the URL was the field you could not read

    Name, search URL and shortcut each flexed to an equal share, which left the URL — the only long value of the three, and the one you check for %s — cut off after about thirty characters while the shortcut box sat two-thirds empty for a key of at most five letters. The URL now takes the slack (flex: 4), the name is capped at 150px and the shortcut at 72px; below roughly 700px the row still wraps as before.

Dashboard

  • Fix
    a bookmark whose shortcut starts with c could not be reached by typing it

    Bare c added a category, and it did so unconditionally: the handler stopped the event dead, so the shortcut search never saw the letter. That is one twenty-sixth of the alphabet spent on an action taken a few times a day, in an app whose main gesture is typing a shortcut. Adding a category is Shift + N now, beside the other Shift actions (Shift + B adds a bookmark, Shift + W sets a width), and every letter starts a search again.

Appearance

  • New
    the glow under a raised surface reaches almost every theme, and the config view at last

    It was built for the four character themes and 132 of the 222 built-in themes derived to exactly zero: the formula multiplied by how dark the page is, so all 109 light themes were flat by arithmetic rather than by choice, and 23 quiet dark ones fell out on accent chroma. themeSurfaceGlow now has two branches. On a dark page it is the halo it always was, floored at 0.15 and capped at 0.60 instead of 0.45. On a light page the ground term inverts and the glow is spent as an accent-tinted shadow under the surface, floored at 0.12 and capped at 0.35 — light around a surface on paper is a smudge, which is why light themes were written off in the first place. Which of the two geometries a theme uses arrives as --theme-glow-lift, a number rather than a word, because CSS can compute with a number and cannot match a word. Nocturne Ink, Porcelain, Paper Ink, Bone China and Salt Flat declare -1 and stay flat, and prefers-contrast: more sets the glow to zero for the same reason it already flattens the tint.

  • Fix
    in the classic layout the config view had no glow at all, whichever theme was picked

    The glow rides two tokens, and every consumer of --layout-shadow-* sits inside a body[data-layout-version="modern"] rule — 58 of them in config-view.css alone — so in classic those tokens resolved to nothing and the panels carried no shadow to hang it on. Eight surfaces that classic left without a box-shadow now paint the accent layer and nothing else: config tiles, panels and choice rows, the search container, the list-view summary and groups, the quickstart card and the health monitor stats. No grey base shadow comes with it — classic stays classic, with colour under its surfaces rather than a second modern layout. The repeating rows (feed rows, inbox items, health items, CRUD rows) are deliberately left out: fifty glowing rows in a column is noise, not depth.

  • Fix
    the glow scaled its own geometry, so the softest ones were invisible

    Strength multiplied the offset and the blur as well as the colour, which at the new floor of 0.12 shrank a 6px shadow to 0.7px — precisely the themes this was meant to reach. Strength now decides how strong the glow is and not how large, and at zero the colour is fully transparent, so a theme that asked for none still paints nothing.

Docs

  • Docs
    the release round for v1.9.0

    static/data/whats-new/v1.9.0.json and the index entry ahead of it, both tokens in whats-new-stub.js (DASHBOARD_RELEASE, NEXTDASH_WHATS_NEW_DATA_VERSION → whats-new-v284) and the constants they are pinned with in tests/whats-new-hidden-release.spec.js. Three spotlights with since: "v1.9.0" in overview-features.json — the section rename, the theme glow, and c going back to search — each with its five locale keys in all six languages, so the overview stream and About → News & features carry the release rather than yesterday's. helpVersionBody names 1.9.0 in six languages, MANUAL.md tags what changed, and go generate refreshed asset_hashes_gen.go.

  • Docs
    the cheat sheet follows the keys and the sections that moved

    The ! modal, the printable sheet and both PDFs are regenerated from the registry, so Shift + N is on paper as well as on screen; the config rows no longer say Pages & tags, and the tag filter is listed where the Tags tab now is. Help's Config navigation had that filter on a Structure tab it no longer sits on.

  • Docs
    Help and the manual describe the config that exists

    Help's rail list named a section that had been renamed and put it in the old order, its Bookmarks page counted five tabs where there are six, and the tag panel still sent you to the section Tags had left. The manual pointed at config → pages & tags in ten places. All of it in six languages, except the release notes, which say what shipped at the time and are left alone.

  • Docs
    the second gallery in Emerald Matrix [dark] is gone from the README

    Its ten files were removed from screenshots/emerald-matrix/ without the block that pointed at them, so the fold held ten broken images on the published page. The <details> section goes with the files; the ten shots above it are untouched.

  • Repo
    every screenshot ever committed is out of the git history

    screenshots/ had been in the tree since the initial commit, and 89 blobs totalling 178 MB were still reachable from main, dev, the other branches and all 314 tags — including captures of a real dashboard that were added and removed again the same day. A git filter-repo --path screenshots/ --invert-paths pass rewrites all refs; the packed repository drops from 209 MB to 29 MB and the file trees are byte-identical apart from that directory. Every commit SHA changed, and the commits that touched nothing but screenshots are gone rather than left empty.

  • Docs
    the README screenshots are from the app as it is now

    The nine shots dated from before the theme browser, the search overlay, the statistics tabs and the bookmark manager's tabs, and two of them showed widgets that no longer exist. Ten new captures replace them, taken against a real collection rather than a seeded one, and named after what they show rather than numbered — the Unraid template lists the same files.

Only docs and tests changed in this release.

v1.8.0 Changes in Fixes and Config. +15 22 fix

Changes in Fixes and Config.

Fixes

  • Fix
    the finder line was empty straight after a page load, with finders configured

    ? said No finders set up yet and offered the way to add one, and a shortcut typed after it never gained its trailing space — both symptoms of the same thing: SearchComponent's constructor handed SearchFindersComponent an empty array and left the real list to updateData(). The search stack is fetched by the key that opens it, so the component is built after the dashboard's last render and nothing calls updateData() in between; the overlay opened on a set of finders it had never been told about, and only the next render — a page switch, a setting, anything — put them there. That is why it looked like a first-visit-only fault. The constructor passes the finders it was given.

  • Fix
    following the system dark mode left the old background nailed to the page when the switch happened in a background tab

    A theme switch pins the outgoing background on <body> with !important so the repaint cannot flash, and released it two requestAnimationFrame ticks later. A hidden tab runs no animation frames, so a Mac going dark while the dashboard sat behind another tab came back with the light background stuck under the dark theme's text — white on white, or the reverse — and only a reload cleared it. The frames are the fast path now, with a 250 ms timer behind them and a visibilitychange for the tab that stays hidden longer than the timer; every path goes through the same idempotent release, and a switch on top of a switch lets the earlier pin go before making its own.

  • Docs
    Help and the manual say that following the system happens in a background tab too

    Config → Appearance's help panel described the pairing and said nothing about when the swap happens, and the manual's troubleshooting list had no entry for a page whose colours came back wrong after the Mac went dark — the two places a reader looks when it does. Both cover it now, in all six languages, with the hard-refresh note for anyone still running the JavaScript from before the fix.

  • Fix
    the catalogue's "in view" check demanded that a whole settings panel fit on screen

    Rewritten with the auto-open change, it asserted the row's top and the panel's bottom were both inside the viewport — which on CI's 720px-tall window a panel of several fields cannot satisfy, so it failed there three retries running while passing locally. It now checks what the test was written for: the new row's head is on screen and its fields start above the fold, rather than the whole panel fitting.

  • Fix
    the widget specs opened a panel that was already open, and sat out a timeout each time

    Four helpers added a widget and then clicked Settings to reach its fields. Since a new widget arrives with its settings open that click is a toggle: it closed the panel, and the wait for a field that had just been hidden ran to its full 30 seconds. Seven tests failed that way in config-widget-panel, widget-secret-reveal, widget-preset-address and widget-cpu — the specs that sit in CI shards 3 and 6, which is why those two ran for double the time of the other four rather than failing outright. Each now clicks only when aria-expanded says the panel is closed, which is also what the four call sites that open a seeded widget's panel have always been doing. The affected files run in 2.2 minutes rather than 3.6.

  • Fix
    CI failed on the Spanish locale over a test that counted languages rather than naming them

    tests/list-view-shell-i18n.spec.js asserted files.length === 5 against locales/, so the sixth language broke a check that was not about it: the test exists to prove every locale carries the list-shell strings, which the loop under it already does for whatever files are there. It now compares the directory against a named list, the way validate-locale-parity.cjs and its neighbours spell theirs out — a missing locale still fails, and a seventh language trips every list at once and on purpose. tests/dashboard-category-width.spec.js was stale in the other direction: its "nothing is cut off, in any language" loop never switched to Spanish, so the longest labels in the category menu went unchecked. It covers es now.

Config

  • New
    a widget arrives with its settings already open, and the reveal scrolls to the fields rather than to the row's head

    Adding one is almost always followed by filling it in, and the fields sat behind a second click on Settings. Only one settings panel is open at a time, so on a page that already carried a widget of the same kind that click also closed the panel being read — which is what made a second RSS block feel like it could not be given feeds of its own. addWidget now records the new block's index in _widgetSettingsOpen (via a new lastWidgetIndex, since the list is grouped by default and the new row is only last when sorting by page order), and revealNewWidget takes that index rather than picking the last row on screen. The caret still lands in the title box, so renaming first is unchanged.

  • New
    Config → Bookmarks proposes tags in bulk, from the tags you already gave a host's other bookmarks

    A new pure module groups bookmarks by host and by host plus first path segment, finds the tag a group agrees on — counted over its tagged members, so a host that is only half sorted still says something — and offers it to the ones lacking it, at most two proposals per bookmark. Every row names its source, because a suggestion you cannot account for is one you cannot judge. Rules of your own (Settings.TagRules, narrowed by sanitizeTagRules) outrank what the app noticed. Applying goes through the existing mutateSelected + bulkUndo path rather than a new endpoint, so the 8-second undo works exactly as it does for the bulk bar.

  • Fix
    the tag suggestions panel corrected: a rule it could never match, a row it drew twice, and a list it drew too much of

    sanitizeTagRules stored reddit.com/r/selfhosted, www.github.com and github.com/ as rules, none of which patternsFor() can ever produce — it stops at the first path segment, strips a leading www. and never ends in a slash — so all three sat in Settings looking configured and firing never. A pattern deeper than one segment is refused now, and the other two are narrowed to the shape they will be compared against. A rule that only restates a group the app had already noticed produced two rows differing in nothing the reader can act on, and the pair ate both of that bookmark's two suggestion slots, hiding a genuinely different second proposal; suggest now offers a tag to a bookmark once, with the rule as the reason. Rows are ordered by group size rather than by how specific the pattern is, so a 45-bookmark host no longer sits under a 3-bookmark subreddit, and the list stops at 25 rows with a line saying how many are waiting. suggest also parses each URL once instead of once per rule — 10,000 bookmarks against 100 rules went from 423 ms of blocked rendering to 37 ms. Undo after applying a suggestion redraws the panel where the undo is, rather than relying on a full config re-render that skips itself while an inline edit is open.

  • Fix
    the keyboard legend removed from the top of Config → Bookmarks

    j/k, x, Enter and Esc were spelled out in a strip under the toolbar, above the tag cloud, on every visit forever. The keys are in the cheat sheet and the rows announce what they do, so the strip was a manual sitting where the list should start.

  • New
    the tag suggestions panel says what it is, folds away, and explains itself

    It opened as an unnamed box holding one sentence, the words Your rules, and two unlabelled boxes — a reader could not tell what it was offering or what typing in it would do. It is a <details> now, the same shape as the tag cloud above it: the summary carries the name and a count, so a shut panel still says what it holds, and the open/shut choice is remembered per browser rather than derived from the content, which would have sprung it open again on every repaint. An ℹ beside the name opens the standard config dialog explaining both sources, the threshold behind a proposal, the one-segment limit on a pattern, and that nothing is tagged without Apply. The two rule boxes carry labels rather than only placeholders, with an example under them. And a pattern the server would have dropped — a whole address, or one two segments deep — now says so under the form instead of vanishing: sanitizeTagRules narrowed it in silence, so three rules typed in a row left no clue which one was wrong.

  • New
    tag suggestions moved into a tab of their own, between List and Settings

    Sitting above the bulk bar it competed with the list for the top of the page and pushed the bookmarks down on every visit, whether or not there was anything to review. The tab carries the number waiting beside its name, so the reason to open it is visible from the List tab without the panel occupying it. The proposals lie flat now — the tab is the disclosure — and only Your rules still folds, since a rule list grows without bound and sits under the proposals it would otherwise push away.

  • New
    a shipped catalogue of 463 subjects, so a fresh collection has something to propose from the first visit

    Until now the panel could only repeat what the reader had already done, which says nothing at all to someone who has tagged nothing — the honest but useless "nothing to propose yet". static/data/tag-patterns.json names 463 subjects and the 1,904 sites that belong to each, served as data the way overview-features.json is and read once per page load. There is no minimum group behind a catalogue row: the evidence is the file rather than the collection, so one bookmark on a known site is as good a match as forty, though the rows are still grouped by site so a site is one row rather than forty. Your own vocabulary wins — the catalogue supplies the subject, your tags supply the name, so a catalogue entry dev whose aliases include code is proposed as #code to someone who already tags that way, and the row names the subject it renamed. It says nothing at all about a site your collection has already settled: a reader who files every github.com link under #work is not offered #dev on top, which is the shipped vocabulary splitting a tidy collection in two. A missing or malformed file costs the catalogue rows and nothing else. scripts/validate-tag-patterns.cjs runs in CI and refuses a host claimed by two subjects, a host written with a scheme or a www. that could never match what patternsFor() emits, and a tag repeated in its own aliases.

  • New
    a scan round reads the pages of bookmarks nothing else can place, and files them by what they say

    The first three sources need no network: a rule you wrote, the tags you already gave a site's other bookmarks, and the catalogue keyed on the host. None of them reaches a page on a site the catalogue has never heard of — and the only thing that knows what such a page is about is the page. Read their pages in the Tag suggestions tab does exactly that, one request per bookmark, and states the cost first: "85 bookmarks have no keywords yet." Nothing runs on a timer and nothing rides along quietly; the round is a button, and the button is also the stop. The loop lives in the browser rather than on the server, in the shape RefreshAllBookmarkPreviews already uses, which is what makes stopping free — there is no job to end, only a slice nobody asks for. What is kept is a dozen derived words per page (meta keywords, every article:tag, og:section, the first h1), never the page's text: words are tens of bytes per bookmark, prose would be megabytes in the data directory and in every backup. A page that cannot be read is a skip rather than a failure, and is not asked again. Rows from this source are grouped by subject rather than by host, since these bookmarks are on different sites by definition — #networking · across sites · 3 bookmarks · the page text (dns). Two loose keywords are the floor, because one shared word is coincidence often enough to be worthless; a page that writes the subject's own name, or your word for it, has said what it is and needs no second word.

  • Fix
    the scan round shows the same progress overlay every other long walk in config does, and it can be stopped from there

    It reported itself as a line of text beside its own button, which is not what reading a hundred pages looks like anywhere else in the app: importing sources, refreshing previews and making a backup all put up ProgressOverlay, and this walked a collection in exactly their shape while looking like nothing was happening. The overlay gained the one thing this round needed and the others do not — a way out. A blocking panel is right for a single request nobody could usefully interrupt; it is wrong for minutes of outbound requests started by a misplaced click, so a caller that can stop halfway passes onCancel and gets a quiet Stop under the bar. The rest are unchanged and get no button. showProgressOverlay was forwarding only its first two arguments, so the button was configured and never drawn.

  • New
    your rules moved to a tab of their own, between Tag suggestions and Settings

    They were a folding block under the proposals, which put the editor at the bottom of a list that grows: a reader with a screen of suggestions had to scroll past all of them to write a rule, and a reader with forty rules had to scroll past those to write the forty-first. The tab carries its own explanation and an ℹ that says what a rule beats and how deep a pattern may go, the form sits above the list rather than under it, and the form is carded exactly like the rules it produces — a form shaped differently from its own output reads as a different kind of thing. The Read their pages offer became a row of the same kind as the proposals above it, tinted rather than plain, with what it says on the left and what it does on the right. And a stored copy under Local copies is a card too: hairlines between rows made a group of captures look like ruled paper rather than like a list of things each of which can be downloaded or deleted.

  • Fix
    reloading on a bookmarks sub-tab filtered the list to a page named after that tab

    The third segment of #config/bookmarks/… is two things at once: the page a filtered list is scoped to, and — when no page filter is set — the sub-tab. Reading a tab name back as a page id left the List tab scoped to a page called "tag-suggestions", which no collection has, so it showed nothing and offered a filter chip nobody had asked for. A page filter is always a page id and those are numbers, so a segment spelling one of the tabs can only be a tab.

  • Fix
    a row's More menu and its right-click menu now offer the same things

    They were written out separately and had drifted: right-click knew Open in new tab, Edit, Pin, Checking, the three filters and Select; More knew nine of the sixteen entries and nothing else — same row, same bookmark, two different answers to what you can do with it. actionsFor() is the single list now and More is built from it, so an entry added to either appears in both. The click goes through the context menu's own dispatcher too, which already knew the handful of actions the row menu never learned; a submenu entry (Checking…) is anchored to the item that opened it, so the second menu appears where you clicked rather than beside the badge.

  • Fix
    the arrow keys walk the bookmark list, and "down" no longer leaves the page

    The keys reached the rows only once focus was already inside the list, so on a freshly opened Bookmarks section the first press fell through to the config section shortcut: pressing down on a list of bookmarks moved to Appearance. With nothing focused and rows on screen the list now claims the key, which is the whole point of a keyboard cursor — a reader should not have to click a row before the keyboard works. ArrowDown and ArrowUp are mapped onto j and k rather than duplicated, since "up" and "down" on a list of rows is the arrow keys to almost everyone, and the legend that named j/k is gone. Fields keep their own keys: the arrows still move the caret in the search box, and typing in any input is untouched.

  • Fix
    a row menu opened with m can be walked and closed on the keyboard

    It opened and then stranded you: Escape reached the view's own handler, which wiped the row cursor and left the menu hanging over the page, and j/k were refused inside a row control and then taken by the config section shortcut — pressing down in an open menu moved to the next section with the menu still up. The open menu owns the keys now: the arrows and j/k walk its items and wrap, Home and End jump to the ends, and Escape closes it and puts focus back on the More button with the row cursor where it was, so the next press carries on down the list. Enter is untouched, since focus is already on the item.

  • Fix
    the number on the Tag suggestions tab changed the moment you opened it

    Arriving on Config → Bookmarks it read 1 and opening the tab turned that into 19: the shipped catalogue and the scanned keywords were fetched when the tab was bound, so until then the strip could only count what a rule of your own had found. A count that changes when you look at it is worse than no count. Both are loaded once when the section opens now, and the strip is corrected when they land — they were already cached per page, so the tab itself still costs nothing.

  • Fix
    the bookmark search box refused the letters j, k, g and G

    They were handed to the list from inside the field: typing one left the box and moved the row cursor instead of typing, so github, json and jira could not be searched for at all, and a space opened whatever the cursor happened to be on. Two places let them through — the view's own guard and the list handler's — and both do now what a field is owed: every key belongs to the field. Escape still reaches the handler that clears the box, and the arrows still move the caret. The tag filter under Pages & tags keeps its arrows, which was always the defensible half of this.

  • New
    a suggestion can be opened to see which bookmarks it means, and one can be left out of it

    47 bookmarks was a number to take on trust, and a group with a single wrong member left the reader nothing to do but refuse the whole row and tag the other forty-six by hand. The count is the handle: it opens a list naming each bookmark, and each carries a tick. What stays ticked is what Apply writes — untick the recipe someone linked from a gist and the other forty-six still get #code in one click.

  • New
    the scan round reads the title and the description too, which more than doubles what it finds

    It read the places a publisher files a page — meta keywords, article:tag, og:section — and the first h1. Most of the web publishes none of those: on a real collection of 107 bookmarks only 13 pages yielded a word. Reading the <title> and the description as well takes that to 32. They are read last and the twelve-word cap is what keeps them in their place: a keywords tag was written to file the page, a title to sell it, so the deliberate sources fill the slots first and the prose gets what is left. Titles are split on a dash and a colon as well as a pipe, since that is how a title separates its parts. Seventeen more words joined the list of things a page says because it is a page — breaking, home, power, mobile, inbox — each of which had matched a subject by name on that same collection and filed a meme site under #news, a file-sharing page under #home and a chat assistant under #energy.

  • New
    the keywords read from your pages can be forgotten, and read again

    Forget the scanned keywords sits in Data & backups beside the other cache actions, and in the panel itself once the round is done. It clears the words and nothing else: the same cache entries hold the title, the description and the picture, all fetched for the preview cards and none of this feature's to throw away. Read them again re-reads every page for a collection that has already been scanned — after a site redesign, or once the catalogue has grown enough to be worth weighing against — and keeps the words it has until they are replaced, so the panel goes on proposing while the round runs. Which pages are still unread is its own stamp now (keywordsAt) rather than the preview's fetchedAt: a page that could not be read is remembered as asked, so a dead link is not offered on every round forever, and forgetting the words makes a page askable again without touching its card.

  • New
    both review offers can be switched off, in the group where everything unasked is answered

    Two switches join the session tips under Behavior → General → Onboarding — enableTagSuggestionNotice and enableHealthReviewNotice, both default on — which is also the first way to silence the link-review card without giving up link checking itself. An install that predates the keys keeps both: an absent key means never answered, and for an opt-out that is on.

  • New
    a card in the corner offers a round of tag review

    The panel only ever helped the reader who thought to go and look at it. tag-suggestions-notice says, now and then, that there is something worth accepting — in the shape that does not demand an answer: Start, Not today, Remind me in 30 days. Ten proposals before it says anything, and ten new ones before it asks again, so accepting part of a pile does not bring it straight back for the remainder. It counts only the sources that need no scan round. Start opens the Tag suggestions tab rather than a second copy of the panel over the dashboard.

  • New
    a turned-down proposal can be taken back on its own

    The refusals were a count and a single Offer them again, so wanting one back meant taking every refusal back with it. They are listed by name now — youtube.com → #video — each with its own way back, with the all-at-once button kept for a clean slate.

  • Fix
    scrolling the bookmark list closed an open row menu

    The list draws a window of rows and redraws it as it scrolls, and that redraw threw away the menu hanging inside it: opened, scrolled past, gone mid-use. repaintBookmarkRowsOnly already declined to redraw under the move popover and the right-click menu for exactly this reason — the one menu that lives inside the rows rather than over them was missing from that guard.

  • Fix
    the suggestion rows had a column of counts that lined up with nothing

    Each row was its own grid, so 1fr and every minmax were resolved against that row's own content: a long hostname or a longer reason moved the count in that row and nowhere else, and a list of fifteen rows had fifteen different left edges. The list owns the columns now and each row takes them with subgrid, which is the only way they line up without fixing every column's width and truncating the hosts — browsers without subgrid get exactly what they had, untidy rather than broken. The count itself became a number in a chip, right-aligned on tabular figures so 1, 9 and 112 sit on the same digit; fifteen rows each ending in the word "bookmark" was fifteen copies of what the column already means, and the full phrase stays as the chip's accessible name because a bare "3" read aloud is not a count of anything.

  • New
    a proposal can be turned down, and the rows read as a table

    Apply was the only answer a row took, so a suggestion the reader did not want had nothing to do but sit there being offered again on every visit. No thanks sits beside Apply now, recorded in settings as pattern|tag rather than as the bookmarks under it — the bookmarks change as the collection grows, and a refusal recorded against them would come back the moment one more link on that site was added. Both buttons are undoable from the toast, and a line under the list says how many are turned down and offers them again in one click. The rows themselves were a run of words with no shared edges: they are the bordered card the bookmark list uses, in five fixed columns, so the panel is scanned down a column instead of read line by line.

  • Fix
    the thinnest evidence produced the widest suggestion, and applying one wiped the rows you had ticked

    The share a group had to agree on was counted over its tagged members, which is right — three of thirty carrying #code still says something — but nothing said how many that had to be. Two bookmarks of thirty carrying #todo agreed unanimously, and the panel offered #todo to the other twenty-eight, reading "your own tags (2 of 2)". A tag now has to appear on at least three bookmarks before it counts as agreed, which is the same three the empty panel asks the reader for. Applying went through mutateSelected, which clears the selection — correct for the bulk bar, since that is what it was acting on, but this panel acts on a group of its own, so ticks made in the list are restored afterwards. The source field on a proposal is gone: only the tests read it, and reason.kind already carried the same fact.

  • New
    ten catalogue subjects that could never fire from a page's text now can

    A page-text proposal needs two loose keywords, so a subject carrying one — or none — was unreachable from that source no matter what a page said. big-data, cloud-storage, containers, insurance, journals, meal-kits, newsletter, paleontology, research and school each gained three words that a page on the subject writes and a page on another does not. The validator's collision rule is what keeps them honest: a word claimed by two subjects is refused, so peer-reviewed belongs to journals alone and research is described in its own terms.

  • Fix
    a row menu in Config → Bookmarks closed itself a few seconds after opening

    Health and the bookmarks editor share the row menu markup, class names and all, and both draw into #dashboard-layout — but health's closeAllMenus swept the whole document. Opening Config → Bookmarks calls health.clearKeyboardSelection(), health is loaded lazily, and the lazy proxy replays that call once the module arrives: a menu opened with m in the seconds before that vanished on its own, with nothing on screen to explain it. Health now closes only the menus inside its own shell, and claims Escape only for those.

  • Fix
    the count that opens a suggestion could only be opened with a mouse

    The chip carries role="button" and aria-expanded but is a <span>, and only a click listener was bound — so Enter and Space, which fire a click on a real button and on nothing else, did nothing at all on the one control in the panel that is not a button. It answers both now, with Space swallowed rather than scrolling the panel underneath.

  • Fix
    Apply on a group with every member unticked did nothing, and said nothing

    Untick the lot (an easy accident, since the ticks are how a single wrong member is left out) and the button wrote no tag, raised no toast and gave no reason. It now says so.

  • Fix
    a subject named in two words could only be read off a page that hyphenated it

    Keywords are matched as single tokens, so the catalogue writes peer-reviewed and meal-kit — but the extractor split a page's text on whitespace, which left 354 of the 1,924 shipped keywords (18% of them) reachable only by a page that happened to write the hyphen itself. Adjacent words are now also offered as a hyphenated pair, in a second pass after the single words have taken the slots they wanted: a pair is weaker evidence than a word a publisher chose, and it rests on two words that each survived the furniture list on their own.

  • Fix
    the 177 KB tag catalogue was fetched twice per visit, and revalidated every time

    Both readers of it — the review panel and the corner card — fetched it for themselves, so seeing the card and then opening the panel paid for the largest file the app ships twice over. Worse, both asked with cache: 'no-cache', which forced a conditional request on every visit even though /static/data is served immutable for a year. It is one loader now holding a single promise, asking for the file the way overview-features.json is asked for: versioned by the app fingerprint, and then cached until the next release. The suggestion engine itself no longer blocks the parser either — nothing needs it before the document is there.

Docs

  • Docs
    v1.8.0 published across every surface

    static/data/whats-new/v1.8.0.json with index.json naming it first, both tokens in whats-new-stub.js moved (2026.09-dashboard-release-v1.8.0, whats-new-v282) and tests/whats-new-hidden-release.spec.js moved with them. Three spotlights carrying since: "v1.8.0" in static/data/overview-features.json — the suggestions tab, your own rules, and the two review offers — which is what Config → Overview and About → News & features draw from. MANUAL.md gained a Tag suggestions subsection under §12 and a paragraph on the bookmark list's keyboard in §16, and the sub-tab table now names all five Bookmarks tabs. README.md gained one line: the feature list is what a new reader reads, and bulk tagging is a capability rather than a release note. Config → Help says what the section's five tabs are and what each of the four sources is, helpVersionBody names 1.8.0, and two tips joined the catalogue (tipEditTagSuggestions, tipTuneReviewOffers). Asset hashes regenerated.

  • Docs
    the six locale files translated for this release

    The keys this feature added ship translated rather than English-with-a-key: the panel, the rules editor, the scan round, the corner card and the two switches in nl, de, fr, es and zh, plus the fifteen new overview-feature keys, the two tips, the Bookmarks help and the version panel. validate:locale-parity, validate:locale-placeholders and validate:help-i18n all pass.

Only docs and tests changed in this release.

v1.7.1 Changes in Dashboard and Languages. +2

Changes in Dashboard and Languages.

Dashboard

  • New
    an RSS widget beside Weather and Calendar in "What's happening around you?": the latest articles from the feeds a tile is given, one headline per row

    Not the Feeds widget, which reports on feeds — Fresh is a checker and deliberately keeps no titles — this one reads from them. Server-side, because a feed served without CORS headers cannot be read from the page at all; the RSS and Atom parsing is the shape sources_feeds.go already carries, so only the reading half is new (no import cursor, no bookmark rows). Feeds are named per widget rather than per install — two tiles following different subjects is the ordinary arrangement — through a new urlList settings kind: a textarea, one address per line, up to ten. It is its own kind because the tags box is one comma-separated line capped at 400 characters, and a comma is legal inside a URL. Each feed is cached per address for 15 minutes and shared by every tile that names it; the merged list is newest first, undated entries last. Rows are buttons carrying data-widget-href rather than anchors, which is what keyboard navigation stops on — arrow keys walk them, Ctrl/Cmd+Enter opens a new tab, and the row menu offers the same. A headline truncates to one line via the shared .dashboard-widget-row-name, with the whole entry — title, the feed's own summary, source and age — in the existing hover/focus popover (DashboardSmartWhyPopover), gone again on mouse-leave. What is past the row count folds into a "more" row that expands in place and remembers it, the way an expanded category does.

Languages

  • New
    Spanish (Español) as a sixth full language, in parity with the other five

    locales/es.json carries all 6136 strings — the dashboard and its cheat sheet, the command palette, the onboarding and quick-start wizards, every config tab, the statistics, the health and inbox views, and all of Help's prose bodies — plus extension/locales/es.json for the browser extension. Wiring a language up touches more than the three places the old note named: availableLanguages and nameKeys in static/js/shared/config-language.js, the pickers in dashboard-config.js, search-commands.js and dashboard-quickstart.js, the noscript branch in templates/dashboard.html, EXT_SUPPORTED in extension/i18n.js, and the language lists in validate-locale-parity.cjs, validate-help-i18n.cjs and validate-cheatsheet-i18n.cjs. Verified against a running server: /locales/es.json serves, the page renders lang="es", and the grid comes up in Spanish.

Docs

  • New
    the manual, Help and the tips cover the RSS widget

    MANUAL.md gains it in the "What's happening around you?" table (twenty types now, not nineteen), a paragraph on giving one tile several feed addresses, and a troubleshooting entry for an address that answers a web page rather than a feed. Help's widget catalogue and widget intro say the same in all six locales, and helpVersionBody names this release. A new tip points at the block from Config → Help → tips.

  • New
    the Custom widget's own reference is no longer English in German and French

    The seventeen paragraphs under Config → Widgets → Types that explain what the Custom widget reads, stores and refuses had never been translated; a further eleven single strings in Dutch ("Open bookmark", "Tight columns", "Open Widgets →") were the same. npm run validate:locale-parity passes as it did before — parity was never the gap, English text sitting in a translated file was.

Only docs and tests changed in this release.

v1.7.0 Changes in Dashboard, Config and Command palette. +6 Read the post

Changes in Dashboard, Config and Command palette.

Dashboard

  • New
    icon-only action buttons (category ⋯, sort chip, config row icons, and the bottom dock's / > : ? * . ! ★ buttons) restyled for the newer themes: borderless, soft filled, circular where the content is a single glyph

    New static/css/action-btn-tokens.css defines --action-btn-bg / -bg-hover / -color / -shadow from the same color-mix()-against---text-primary formula theme-depth.css already uses for --hairline, so every theme gets the new look with no per-theme override. Full-word buttons (Quickstart, page tabs, Settings/Delete rows) are untouched.

  • New
    a Lock layout setting (Config → Behavior → General, and :lock-layout / :locklayout in the command palette) turns off drag-and-drop reordering for both bookmarks within a category and categories on the grid

    Reuses the existing sort-locked drag hint with its own wording instead of a second hint mechanism, and marks the category grid's drag handle with a plain cursor via a new body.layout-locked class. Sorting, adding, renaming, and deleting are unaffected — this only gates the drag gesture. The checkbox carries a small "New" badge (config-field-badge, a generic property any control can now set) so it stands out on the tab.

  • New
    a Weather widget: current conditions beside a forecast, in its own "What's happening around you?" group in the widget catalogue

    Reuses the location, source and unit already set for the header's own weather line (Behavior → Date & weather) rather than asking a second time — the widget's own settings hold only a Forecast range choice (3 days / 5 days / 24 hours), with a hint pointing back to where the location lives. static/js/weather.js gained fetchForecast, one Open-Meteo request carrying both current and daily/hourly rather than two round trips, cached in localStorage alongside the header's own reading. Polls on the same 30-minute cadence as the header line rather than a setting of its own.

  • New
    a Calendar widget, beside Weather in the same "What's happening around you?" group: what is coming up, from one ICS feed set for the whole install (Behavior → Date & weather → Calendar feed URL, separate from the existing outbound calendar link)

    Fetched and parsed server-side rather than in the browser, the same reasoning as the custom widget: most providers hand out a private feed address that is not meant for cross-origin JS, and it is not a thing to leave sitting in a script. A hand-rolled parser reads SUMMARY/DTSTART/DTEND, unfolds RFC 5545 line folding, and reads VALUE=DATE and TZID — recurring events (RRULE) show their own stated occurrence rather than being expanded, a deliberate v1 limit. One feed cache shared by every calendar widget (15-minute TTL, GET /api/widgets/calendar?pageId=&id=), each widget narrowing it to its own Look-ahead-days and row count. Reuses the existing .dashboard-widget-rows row styling — no new CSS. A saved widget setting or a changed feed URL redraws the tile immediately — forgetWidgetCaches now drops the calendar tile's own client cache too, and calendarIcsUrl gets its own branch in setBehavior's datetime handling, the same shape the weather fields already use.

Config

  • New
    Hypr mode moved out of the General checkbox list into its own titled section, directly under Onboarding, with a full explanation of what it does

    It was easy to mistake for the "Open links in a new tab" checkbox above it when it was just another one-line label + info icon.

Command palette

  • New
    a typed setting command now marks its current value visually, not just in the row text

    Every toggle (:animations, :lock-layout, …) and every multi-choice command (:density, :columns, :theme, …) paints its current-value row with a soft accent tint and a small "current" pill, on top of the existing "(current)"/"✓" text. Comes from two shared helpers — _buildOnOffRows/_handleSimpleToggle and the new _markCurrentRow (replacing _markCurrent, spread into the row instead of just naming it) in search-commands.js — so every command built on them picked it up in one pass rather than a per-command edit. The list already re-renders in place after a change (_paletteRefresh → refreshCommandPaletteInPlace), so the highlight moves with it live.

Docs

  • New
    the manual and the in-app Help cover the Weather and Calendar widgets, Lock layout, and the Calendar feed URL

    MANUAL.md gains a "What's happening around you?" table beside the other widget groups (nineteen types now, not seventeen), Lock layout notes under Reorder bookmarks and Reorder categories, a :lock-layout row in the command table, a "Calendar widget shows nothing" entry under troubleshooting, and a header note keeping Calendar URL (the outbound link) apart from Calendar feed URL (what the widget reads). Help's widget catalogue, Behavior tour and widget intro say the same in all five locales — de, fr and zh were still missing the system-widget group as well, so their kind counts were wrong before this and are right now.

Only docs and tests changed in this release.

v1.6.2 Changes in Health. 2 fix

Changes in Health.

Health

  • Fix
    opening a row's More menu drew it behind the row below, cut in half, under a depth theme

    .feed-row picks up a backdrop-filter under theme-character.css's glass depth, and the row's action bar already sat at opacity: 0 until hovered — both make .feed-row its own stacking context, which traps the menu's z-index: 20 inside that one row, so a later row in the DOM always painted over it regardless of the menu's own number. static/css/feed-row.css now raises the row itself while it holds an open menu and keeps its action bar painted rather than fading it out from under the pointer, both keyed on the same .health-view-menu:not([hidden]) state Health and Config → Bookmarks already share — so the fix reaches both .feed-row consumers with an in-row menu without touching either view's own CSS. Covered by a new spec that asserts on containment (menu.contains(el)) rather than z-index, under a theme that actually applies the blur.

  • Fix
    an open row menu was painted under the sticky header, and under the bulk-select bar

    Raising the row above its neighbours (above) fixed the row-on-row case but not this one: .lvs-header and .multi-select-toolbar are both position: sticky; top: 0 and both outranked it, so a menu opened near the top of a long list slid underneath them. The three numbers involved were 1, 5 and 20, written in three stylesheets with nothing tying them together, so a plain bump on the highest would have worked once and collided again. static/css/layer-tokens.css is a new unscoped token file — same reasoning as spacing-tokens.css — naming --layer-sticky-band for a view's own pinned chrome and --layer-row-raised for a row that must rise above it while transiently active. Deliberately not the overlay scale: modals and search sit in the 1000s–12000s on <body> and nothing here should compete with them.

Only docs and tests changed in this release.

v1.6.1 Hidden from the What's new modal — v1.6.0 already covers the shared-shell work this round was cut to announce, so there is nothing left here the modal needs to lead with. 3 fix

Hidden from the What's new modal — v1.6.0 already covers the shared-shell work this round was cut to announce, so there is nothing left here the modal needs to lead with. index.json[0] still names this release, and /version reports it.

Health

  • Fix
    the Monitors row in the rail could get stuck at 0

    The rail's sections config is read once, when the shell mounts — usually before the health report has finished loading — and unlike the filter rows above it, which refresh their counts on every render via setCounts(), the Monitors row had no equivalent follow-up. A setSectionCounts() call alongside that existing refresh keeps it current from then on, covered by a new spec.

Inbox

  • Fix
    clicking a row's domain chip left a stale selection anchor behind and never saved the site choice

    The chip's click handler was a hand-rolled copy of the filter reset that skipped checkAnchorId and the write to localStorage, so a later Shift+click could extend a selection through rows the narrower view never showed, and the site choice did not survive a reload the way picking it from the select does. It now goes through the same path as every other filter change.

Docker & deploy

  • Fix
    make up and docker compose up --build could stamp a container with version: "dev" even though the docs already claimed a real release

    VERSION was only ever set by the CI Docker build's --build-arg; nothing in docker-compose.yml supplied it, so a local build silently reported "dev" from /version while static/data/whats-new/index.json said otherwise. docker-compose.yml and docker-compose.prod.yml now interpolate VERSION from the environment (${VERSION:-dev}), and the Makefile's up/build/build-clean/reset-data targets export it from the new scripts/version-from-index.sh, which reads index.json[0].tag — the same field release_version.go's readLatestReleaseTag already treats as the source of truth. A plain docker build with no --build-arg is untouched and still falls back to dev.

Only docs and tests changed in this release.

v1.6.0 Changes in Dashboard, Health, Inbox and Themes. +11 23 fix

Changes in Dashboard, Health, Inbox and Themes.

Dashboard

  • Fix
    pressing ? while the finder line was already open broke the search you then typed

    ? opens finders; pressing it again added a second one, and from there everything went wrong at once. The guard that swallows a lone space looks at what follows the first ? — now a ? rather than nothing — so spaces began landing in the query, and the whole thing was searched for literally: typing jordibrw.nl looked for ??JORDIBRW.NL. Once you are in finders the key has nothing left to do, so it now does nothing.

  • New
    the finder line says when no finders exist yet

    An empty list fell through to the ordinary "No matches found" with an offer to save what you typed as a bookmark — but on a bare ? nothing was typed, and there was nothing to match against. It now says so and offers the way to fix it, which opens Config → Pages & tags → Finders.

  • Fix
    Escape threw away your selection while closing a popover

    The grid's key handler stands aside for the action popovers, listed by id, and three were missing from that list: the multi-select Tags and Checking popovers and the date popover. So Escape closed the popover and ran the grid handler, which saw a live selection and cleared it — you pressed Escape to dismiss the tag list and lost the twenty rows you had picked to tag. One Escape closes one thing now.

  • Fix
    the Checking popover would not close when you clicked away from it

    Every other action popover binds the shared outside-click close; this was the one that never did, so it stayed over the page until you found Escape, and the click meant to dismiss it went to whatever sat underneath.

  • Fix
    typing in the filter box made every widget disappear

    The filter hides a block once nothing in it matches, and it counts matches by the bookmark links inside. Widgets carry the same category class the grid measures and drags by, but hold no links at all — so every widget counted as empty the moment a first letter was typed, and the clock, the weather and the rest vanished while you were filtering your bookmarks. The filter now walks categories only and leaves the widgets where they are.

  • Fix
    long category titles never shrank to fit

    The title fitter measures the smallest allowed size by asking the page what the xs font setting works out to, then steps the title down toward it. It asked using a loose element, but the size is set on body — so the answer came back as the size the title already was, the floor met the ceiling, and the loop that shrinks the text exited before its first pass. Measured against body now, which is where the setting lives, so a title that does not fit shrinks the way it was meant to.

  • Fix
    a page with nothing on it kept the previous page's masonry columns

    The empty-state path cleared the other layout classes but not packed-masonry, so the "nothing here yet" panel was laid out as a column in a grid built for blocks that were no longer there.

  • Fix
    custom widgets redrew from a stale copy after a refresh

    Clearing the widget caches cleared every kind except the custom one, so a manual refresh handed back whatever was last fetched instead of going out again.

  • Fix
    Alt+←/→ on a category header did nothing on a page you had never dragged

    The new position is stored in the block order, which does not exist until something writes one — and dragging was the only thing that ever did. So on a page arranged by nobody, the move looked for the category in an empty list, found nothing and gave up, while the screen reader was told it had moved. It now reads the current arrangement off the grid first, so the keyboard writes the same order a drag would have.

  • Fix
    the quick-action toolbar (add / search / commands / finders / recent / help / fold) followed you into Config, Inbox and Health

    It, its keys (+ > : ? * .) and the search-flow hint that advertises them are dashboard-only; they now hide and go inert the moment a full-container view opens, and come back the moment it closes. The ! cheat-sheet shortcut, Shift-letter view switches and 1-9 page switching are unaffected. The / tag-cloud toggle had the same gap — it filters the bookmarks grid, so it is gone and inert outside the dashboard too.

  • Fix
    opening Config, the Inbox or Health threw away an active tag filter

    Making the / toggle dashboard-only folded two different questions into one answer: whether the tag cloud can be used at all, and whether it belongs on the screen you are looking at. The tag cloud drops an active filter when the first goes false — the setting turned off, no tags left, a phone-sized window — and that check now ran on every view transition, so stepping into another view read as "the feature is gone" and cleared the filter on the way. The two are asked separately now: the button still hides outside the dashboard, and the filter is still there when you come back. The header chip that exists to show an active filter in exactly those views has something to show again.

Health

  • Fix
    Config → Advanced's replay button for the Health tour did nothing

    The tour's id moved to V2 when the view was rebuilt, so anyone who saw the old one is shown the new one once; the list of tours the replay panel is generated from kept naming V1. Clearing it therefore cleared an id nothing reads any more, and the tour it promised to bring back never appeared.

  • New
    the documentation follows the rebuilt Health view

    Config → Help describes the left column, its readouts and Monitors as a section of its own rather than the tiles and toolbar that are gone; the Health tutorial gains a step on finding your way around, and is shown once more to anyone who saw the old one, since it taught a layout that no longer exists. The manual's Health and Inbox sections follow the same change.

  • New
    a review session can put a link aside for a month

    The card offered Re-check, Open, Delete and Skip, so a link that is broken on purpose — a service off for the winter, a host that only answers from another network — had no honest answer: Skip brings it back tomorrow, Delete is not what you meant. Ignore 30d (z) is that answer, and it makes the same write the row menu's z makes, so a link silenced here is silenced everywhere and returns on the same day. The row leaves the session afterwards, for the reason Delete's does: it is answered, and a session that keeps showing what you have dealt with is not counting honestly.

  • New
    Health has the same left column as the Inbox

    Every filter is a row there with its count, and the tiles that repeated those counts above the list are gone. Score, the trend, the broken count and the report's age sit above the filters as plain readouts. A filter with nothing in it drops out of the list and comes back when it fills; Broken, Content, Duplicates, Unchecked and All always stay, and Monitored appears as soon as there is anything that could be monitored.

  • New
    Monitors is a place of its own in the rail now, not a filter

    Opening it swaps the list for the fleet panel — pooled uptime, the worst performers, recent outages — rather than narrowing the list the way Monitored still does. It has its own address, #health/monitors, so it is bookmarkable and returns you to the same view on reload; picking a filter leaves it and goes back to the list.

  • Fix
    the Sections row read as the same thing as the Filter row above it

    Filter → Monitored and Sections → Monitors sat one above the other with the same count and near-identical labels — the exact fault the shell's design spec opens by naming, "the tiles and the filters are the same control, drawn twice" — even though they lead somewhere different: one narrows the list, the other swaps in the fleet panel. The section now reads All monitors, matching the fleet panel's own heading, so the two rows are readable without clicking either.

  • New
    the header stays put while you scroll

    Work through, Rot report, the ⋯ menu and the ℹ explainer live there now, so they are reachable from anywhere in a long list instead of only from the top. The trend chart moved into the ⋯ menu, as Healthy over time.

  • New
    Health rows can be compact or comfortable

    , using the setting the Inbox already reads.

  • Fix
    typing in the search box no longer rebuilds the whole view behind the cursor
  • Fix
    arrow keys can step past the first filter neighbour again

    A second → used to land back on the same row the first one reached, because focus never actually moved there; fixed in the shared shell, so it also applies to the Inbox.

  • Fix
    the title's Smart Why explainer opens by keyboard again

    The trigger had no way to receive focus, so the popover's focus handler could never fire.

  • Fix
    the rail's Uptime 24h reading is no longer always "0%"

    It read the fleet's {ratio, samples} window as a plain number, which is NaN no matter what the fleet was actually doing; it now reads the same figure through the formatter the fleet panel's own tiles use, and reads "no data" instead of a percentage while nothing has been sampled yet.

  • Fix
    the trend sparkline is back, under the trend row in the left column

    It drew in the tile row before the tiles moved into the rail; only the button that opens the full chart came with them, so the line itself had no callers left. A compact redraw sized for the 200px column sits under the trend figure now, and the full chart is still one click away in the ⋯ menu.

  • Fix
    the shared list shell's summary row no longer takes raw HTML

    It accepted a string and set it with innerHTML, trusting every caller to escape first; the shell now takes a built extraNode and appends it, so a future caller handing it a bookmark title or a URL cannot inject markup through it. The one caller, the trend sparkline, is unaffected — it draws the same line either way.

  • Fix
    the rail's filter rows, filter group and summary card get their modern-layout surface back

    Moving the tiles and filter pills onto the shared shell deleted the modern layout's card treatment for them (rounded surface, shadow, hover lift, active ring) without replacing it, so both Health and Inbox rendered a flat list in the modern layout no matter which row was active. Restored in the shared shell rather than per view, shaped for the rail's vertical rows instead of the old horizontal pill strip. The same change also gives the rows back the modern focus ring that went missing with them, and fixes a second, older bug it uncovered: the ring's classic-mode fallback was missing entirely, so keyboard focus on a filter row was invisible in the classic layout too, not only modern.

  • Fix
    the same missing classic-mode fallback also blanked the header actions and the density toggle

    .lvs-filter/.lvs-section got their fallback above; Work through, Rot report, the ⋯ menu, ℹ and the two density buttons carried the identical unguarded var(--layout-focus-ring) and lost their keyboard focus ring in the classic layout the same way, on both Health and Inbox. Same fallback, same reason: var(--layout-focus-ring, 2px solid var(--accent-primary)).

Inbox

  • New
    the inbox has a left column

    The filters moved there as a list with their counts, and This week sits above them as a plain readout — it was the one figure that never had a filter behind it. The row of tiles above the list is gone, since it showed the same counts a second time; Snoozed and With note now appear in the filter list only when there is something in them, and drop out again once there isn't.

  • New
    the header stays put while you scroll

    It shrinks to a single bar as it sticks, so Triage stays reachable from anywhere in a long list. The left column stays with it, so the filters are one click away wherever you are in the list rather than a strip of empty space.

  • New
    the left column becomes one scrolling line on a narrow screen

    The figures move up under the title and the ℹ explainer joins the ⋯ menu, so a phone gets the list instead of four rows of controls above it.

  • New
    rows can be compact or comfortable

    It is one setting for the whole app rather than one per view, so it is already the setting the other lists will read as they move onto the same shell.

  • Fix
    typing in the search box no longer rebuilds the whole view behind the cursor
  • Fix
    the site filter no longer sends the hostname you picked to analytics

    It reports a fixed marker instead, under the same event name as before.

Tests

  • Fix
    the overview's release spec assumed every spotlight leads into config

    It reads the top feature row's own data-overview-go so it survives the next release, but then asserted config.section no matter what that button said — and a spotlight can also carry {view}, which leaves config for Health or the Inbox. It follows whichever shape the button names now.

  • Fix
    two health specs that the rail migration went past

    health-ignore asserted the Ignored filter was absent until something is ignored, but the rail now declares every filter and hides what is empty, so the pill is in the DOM from the first render — the assertion asks for hidden instead. health-rot-tools dismissed the onboarding dialog and the tour before waiting for dashboardInstance, so on a slow run neither was there yet to dismiss: Quick setup and What's new in Health opened afterwards and swallowed the click on Group by site. It waits for the instance first now, the order the other health specs already use.

Themes

  • Fix
    a theme's dark variant no longer wears a different backdrop shape than its light one

    The backdrop's shape is picked by hashing the theme id, and a "-light"/"-dark" pair is two different ids, so 111 of the 224 built-in themes had their two variants land on two different recipes — a diagonal wireframe on one side, a glow from below on the other — while only the colours were meant to change with Quick mode. A "-dark" id is now hashed as its "-light" counterpart, so the pair always shares a recipe; the plain light/dark defaults and every custom theme are unaffected. This changes the look of 111 dark themes, each now drawn with the shape its light half already had.

Only docs and tests changed in this release.

v1.5.0 Changes in Themes. +4 2 fix

Changes in Themes.

Themes

  • New
    a theme can be more than a palette

    Seven optional fields on a theme give it a character beyond its thirteen colours: surfaceAlpha (how solid a raised surface is), surfaceBlur (the backdrop-filter behind it), surfaceGlow (how much accent bleeds around it), radiusScale, and labelTransform / labelSpacing / labelWeight for the category headings. Every one is a clamped number or a word from a fixed list, so no CSS crosses the boundary and the sanitising is a clamp rather than a parser. The zero value of each is exactly today's behaviour, so all 214 existing themes and every hand-made one render unchanged.

  • New
    Glass, a fourth theme depth

    Beside Flat, Soft and Rich, in Appearance → Theme. It turns raised surfaces translucent with the page showing through — in the classic layout as well as the modern one, the modals and the search overlay.

  • New
    a theme glows without being told to

    Four themes out of 222 declared surfaceGlow, so 218 were flat by omission rather than intent. It is now derived from the theme's own palette: how much colour the accent carries (chroma in OKLCH, not HSL saturation, which calls #58A6FF fully saturated on one channel touching 255), how light it is, and how dark the page behind it is. That gives 89 of the 222 a glow of their own — terminals and neons at the top, editor greys around 0.20, paper at nothing. A theme that names its own still gets exactly that.

  • Fix
    the two new spotlights carry their translations

    They were added to the feature catalogue with locale keys but only English fallbacks, which the JSON validator catches: a key a catalogue references has to exist in every locale, or four languages quietly fall back to English.

  • New
    the faint inks are derived from the surface they sit on

    A theme picks three text colours against background-primary and never adjusts them, while the surface ladder rises above it — so every layer costs contrast that nobody sees coming. Measured across the 107 dark built-ins, tertiary text was under 3.0:1 on surface-3 for 33 of them. Secondary and tertiary are now derived per surface with oklch(from …), holding their distance wherever they land.

  • Fix
    the faint text meets WCAG AA on every theme again

    The derived inks sit a fixed step off the surface they are on, and at 0.44 the dark theme fell short: its top surface (#1F2937) is a step lighter than the rest of its ladder, so tertiary text reached only 4.05:1 there — under the 4.5:1 floor for body text. The step is now 0.47, the smallest that clears the floor on every shipped theme and every surface (4.56:1 at worst). The stylesheet, the server default and the test that measures it move together; TestDerivedInkClearsContrastFloor checks the whole register.

Tests

  • Fix
    two specs that the theme work moved past

    The widget readout compared a row's colour against --text-tertiary read off documentElement, which still holds the plain hex while the faint inks are now derived per surface — so it measured the root's colour rather than the tile's, and could only pass while the two happened to agree. It now reads the ink where the rows are, with the probe placed beside them. The v1.4.0 setting drawings asserted three theme depths; glass is a fourth the server accepts and the drop-down offers.

Only docs and tests changed in this release.

v1.4.8 Changes in Widgets, Health, Dashboard, Inbox and Under the hood. +13 7 fix

Changes in Widgets, Health, Dashboard, Inbox and Under the hood.

Widgets

  • New
    widgets can keep their own refresh clock

    The machinery that kept the custom widget current was gated to that one type by name; it is now a table of which types poll and how fast, so a built-in widget can refresh itself. One clock per tile however often it is redrawn, nothing at all for a tile that draws from figures the dashboard already holds, and the custom widget's own ttl and 30-second floor untouched. A hidden tab still asks nothing.

  • Fix
    one bad widget no longer empties the page

    Saving a page's widgets shared its cleaning with the code that reads them, which drops whatever it cannot draw so a file written by another version still opens. On a write that meant a request carrying one unknown type had every other widget silently discarded and was answered 200 — a dashboard losing its tiles to a single bad entry. Writes now refuse: the page is left exactly as it was, the response is a 400 naming the type it could not store, and the panel repeats that instead of "Could not save the widgets". Too many widgets for one page is refused the same way rather than quietly truncated. Reading keeps its tolerance, which is what it was written for.

  • New
    the widgets tab works like the bookmarks tab

    The same toolbar: a search across names and types, a page picker, a sort, and the one button that adds something. Sorting defaults to grouped, under the same headings the catalogue uses — fourteen rows in one column is a list to read, four short groups is a thing to scan — with order on the page, name and type as the alternatives.

  • Docs
    the system widgets are written up in full

    Config → Help gains a panel of their own covering which mount each needs and why, the three variables, the Unraid template rows, and what the tiles will and will not tell you. The manual carries the same as a reference section with the full variable table, and the README's Quick Start now shows the compose block and an Unraid table beside it. The counts that said "thirteen kinds" and "the only widget that talks outside" are corrected wherever they appeared.

  • New
    every page's widgets in one list

    The page picker gains All pages, which answers "what have I actually got" without visiting each tab in turn — a widget on the page you are not looking at is the one you forget you are running. Each row says which page it lives on, and an edit is written back to that page rather than to whichever one the tab was showing. Adding is not offered there, since it has no answer to "where".

  • New
    widgets can be moved to another page, and acted on in bulk

    Tick any number of rows and show, hide, move or delete them at once. A move writes the destination first, so a failure leaves the widgets where they were rather than nowhere; ids travel with them, so a moved widget keeps the sign-in and the collapsed state filed under its id. Ticks are held by id, not row position, so re-sorting cannot retarget them.

  • New
    ↺ resets a widget to its defaults

    One click clears every setting in the panel, into the draft, so Save or Discard still decides. Offered only when something is actually off its default. The title and the Shown box are left alone: those are not settings with defaults, and quietly renaming a widget is not what a reset should mean.

  • New
    the ℹ is on every kind of widget setting

    It was wired to number fields alone, so a tickbox or a choice that needed a paragraph had nowhere to put one. Now on all of them, and still only where there is text behind it.

  • Fix
    a change that saves without a Save button now says so

    Renaming a widget and the Shown box write straight to the server, while the settings panel below has its own Save. Two ways of saving in one row, one of them silent, is what made the tab feel like it might not have taken.

  • New
    a containers widget

    How many containers run against how many exist, with the figures you pick: running, stopped, paused, unhealthy, total, images. Tick nothing and you get them all, so a figure added later is not hidden from everyone who once saved the panel. Two more toggles name what is failing and what just restarted — a count sends you looking, a name does not, and a container up for minutes while the rest have run for days is the shape of a crashloop. Deliberately no per-container CPU or memory: one /stats call measures a full second, so twenty containers would be twenty seconds of polling a beat. It needs the Docker socket, and the panel says plainly what read-only access still grants before you add it.

  • Fix
    a row of figures no longer leaves empty ground

    Every stat grid was laid out in four columns on a wide tile, which is right for four figures and wrong for two, three or six: a widget whose figures the reader chooses left half a row blank, or two patches under a row of six. The column count now divides the figures it was given.

  • New
    a memory widget

    How much memory is really in use, against the total, with a bar and the figures beside it. Used counts what the machine cannot hand out — the page cache is reported separately, as the spare room it actually is, rather than folded into "used" the way that makes a healthy Linux box look permanently full. Swap gets its own line and bar when asked for, and a machine without swap says so instead of drawing an empty one. Given two columns the figures sit abreast instead of wrapping.

  • New
    a disks widget

    Free space per disk you name, with the pool as the headline and used, free, total and percentage beside it. Each disk carries a bar and, optionally, how full its file table is — inodes run out on their own, so a disk can refuse a write with gigabytes showing free. Free counts what can actually be written: reserved blocks belong to root and are neither used nor available. A disk that cannot be read says so on its own row rather than blanking the tile, which is what an array with a drive spun down needs. Given two columns the totals spread across the width instead of stretching. Its settings carry the mount to add.

  • New
    a processor widget

    How busy the CPU is and the load average behind it, as a built-in widget with its own refresh interval (one second at the fastest), and optional load-average and core-count figures. Given two columns the tile fills the width with more figures rather than stretching the same ones. It reads the host through an opt-in read-only /proc mount (NEXTDASH_HOST_PROC): nextDash runs in a container, so without that it would be reporting on itself. Unmounted, the tile names the setup step instead of showing zeros, and the percentage stays blank until a second sample exists rather than claiming an idle machine.

Health

  • New
    the review offer can be put away for a month

    The "10 links to review" card had one way out, "Not today", which expires overnight — right for a postponement, wrong for someone who is not doing maintenance this month. Remind me in 30 days stamps nextdashHealthReviewSnoozeUntil and the card stays away until it passes, then returns on its own. Deliberately not called ignore: the health view's per-row Ignore "Broken" mutes what a bookmark reports, server-side, while this touches no bookmark at all and only decides whether the corner asks. It sits as a quiet text link rather than a third button — a long label wraps onto its own row, where a bordered full-width button would read as the heaviest choice on a card whose primary action is Start.

  • New
    quiet action styling on notice cards

    NoticeCard.define() accepts quiet: true beside primary, rendering an action as an underlined text link. For an answer that belongs on the card but not in the row of choices.

  • Fix
    the settings item in the ⋯ menu carries a capital

    , like Export rows, Retest all and Checking off beside it. English, Dutch and French; German already had one and Chinese has no case to change.

Dashboard

  • Fix
    adding a bookmark works before the search bundle has arrived

    The :new form travels in the lazily fetched search stack, and the keys that fetch it are >, :, ?, * and /. Add-a-bookmark is none of them, and the toolbar button is not on the hover-prefetch list either — so for the first seconds of a visit +, Shift+B, Ctrl+Shift+A and the button each found no handler and returned: no form, no message, and the press was not queued, so it stayed lost once the bundle landed a moment later. Measured rather than argued: with the bundle held back the click opened nothing, and the bundle had arrived by the time the test gave up. All four routes now ask the loader for the stack and open when it is there — which is the promise the loader's own comment already made for the keys it did cover.

Inbox

  • Fix
    Escape on the snooze picker no longer leaves the inbox with it

    One press closed the picker and the view underneath. The guard that stops a view from eating an Escape meant for something layered over it named the menus it knew about, and the picker — added later — was on nobody's list.

Under the hood

  • New
    one place decides who owns Escape

    Every view binds a document-level Escape handler in the capture phase when it opens, before anything inside it exists, so the view always sees the key first; each then had its own hand-written list of what might be on top, and a menu added later was on none of them. That is four bugs so far. shared/escape-owner.js turns it around: anything that can be layered says so while it is up, and a view asks one question instead of naming the answers. Two roles, because the views already told them apart — an owner was opened deliberately and keeps the key, something ambient appeared on its own and is dismissed by the press without keeping it. The inbox and health are migrated and the setting promo registers as ambient. Config's chain stays where it is on purpose: its order interleaves the search, inline-edit and typing guards between the menu and the selections, which a flat registry cannot say, and the attempt to make it fit cost the test that pins exactly that ordering.

  • Fix
    the CI actions are off Node 20

    checkout, setup-node, setup-go and upload-artifact were all being forced onto Node 24, with the same eight deprecation warnings on every job. All four are on their current majors and the warnings are gone.

Tests

  • Fix
    five overlays and one release tag

    The config intro tip shows for fourteen seconds in the bottom-right corner, which is where the activity chart's last bars are, and it arrives after the overlay dismissal has been and gone: four hover tests across two spec files were racing it. The what's-new modal decides to open before it fetches its own module, so on a release whose cache token has just moved it lands after the dismissal too. A setting promo anchored in the bookmarks panel covered the sort chip. And the version pattern on the newest release tag ended at three parts, so it called every four-part release the project has ever shipped malformed — 16 of 169 tags, including the one that broke it.

  • Fix
    reads that landed on a replaced element

    getComputedStyle on a detached node answers "" for every property without complaining, so a chart test failed as though both series were the same colour when the panel it measured had simply been swapped out underneath it. Held the repaint at the door to prove it: 20 failures out of 25, every one carrying connected:false while the live document had the colour.

  • Fix
    seeds that waited for the view to notice them

    Two inbox specs POSTed through the API and then waited for a background refresh to spot the rows. They now ask for the list. The oldest flake on the board went from failing under load to 56 of 56.

  • Fix
    four helpers read searchComponent before it existed

    Three wrote quickAddWidget?.open?.() ?? searchComponent…, and open() returns nothing on success — so the fallback was never a fallback, it was the path, and it only passed when the lazily fetched bundle happened to be there already.

  • New
    a failure says which overlay was in the way

    A modal that arrives mid-test intercepts every click and hover, and Playwright names the element but elides the part that identifies it. Four flaky tests in one run shared that line and nothing else. The harness now asks the page while it is still there — what is on top at the centre of the viewport, what #app-modal holds, any notification — and logs it beside the failure.

  • Fix
    six seconds of sleeping per test, in three config helpers

    They waited out Quickstart's favicon sweep; waitForFaviconPrefetch already waits for exactly that by asking. One file went from 2.8 minutes to 1.2. Two more helpers with the same sleep were left alone: they each failed once in the runs with the change, in blocks that fail on the current code too, and where a pre-existing flake could not be told apart from a settle that had been removed, the sleep stays.

Only docs and tests changed in this release.

v1.4.7.1 Changes in Search. 1 fix

Changes in Search.

Search

  • Fix
    / works when the overlay says to press it

    The hint "Press / to search names" is only ever shown with Switch Search Mode off, and the / handler returned early in exactly that state — so the key the overlay named was dropped, and nothing switched. It also prefixes the query rather than appending: _hasModeSwitchPrefix reads the first character and the hint's own Enter action builds /${query}, so a trailing slash would have landed in the box and still switched nothing.

Only docs and tests changed in this release.

v1.4.7 Changes in Search, Themes, Statistics, Dashboard, Inbox, Health and Config. +6 24 fix

Changes in Search, Themes, Statistics, Dashboard, Inbox, Health and Config.

Search

  • New
    a no-match search offers your finders

    A plain search that matches nothing now lists your most-used finders under the "no matches" line, carrying the query already typed. Clickable, and reachable with the arrow keys like any other row. The block was already built and wired for both; it was missing the one check that asks whether the reader wants finders in search at all, so it appeared even with the setting off.

  • New
    includeFindersInSearch defaults on

    New installs start with it on, and existing ones are moved once through IncludeFindersInSearchMigrated. The config default marker in dashboard-config.js moved with it, so "reset to default" agrees.

  • New
    Brave Search ships as a finder

    https://search.brave.com/search?q=%s&source=nextdash on b, seeded for new installs beside DuckDuckGo and added to existing ones once via BraveFinderSeededMigrated. Matched on the search.brave.com host rather than the whole URL, so a reader who added Brave themselves keeps their own name, shortcut and parameters; the marker means deleting the seeded one keeps it deleted.

  • Fix
    a space directly after ? no longer breaks finder mode

    addToQuery() appends the key before asking whether space should complete a shortcut, and a bare ? trims to "", which no finder is keyed on — so the check fell through and left "? ". Everything typed after landed past that space and was searched as literal text against finder names.

Themes

  • New
    Shift+A opens the theme browser

    Straight to openThemeBrowser(), the same modal Appearance's "Browse themes" opens, over whatever view is on screen. A for Appearance, matching Shift+I, Shift+H and Shift+S; Ctrl+Shift+A (new bookmark) is a different modifier and unaffected.

Statistics

  • New
    pinned, last edited, last saved copy, and how long the longest-standing break has lasted

    All four came from fields the install already recorded and none of them surfaced: pinned, updatedAt, archiveCheckedAt and brokenSince.

  • New
    a growth panel on Content

    Added-per-month from each bookmark's createdAt, last twelve months, with a note naming how many of the total carry a date — anything imported before nextDash recorded one is excluded rather than folded in silently.

  • Fix
    the headline, insights and shortcuts panels honour the page scope

    All three read allBookmarks directly while dividing figures that computeStats() had already narrowed, so a scoped numerator sat over an unscoped total.

  • Fix
    duplicates are counted on one key

    ensureDuplicateUrlSet() keyed on a plain lowercased URL while Statistics used canonicalStatsUrlKey(), so a trailing slash or fragment made the panel and the list disagree about the same pair.

  • Fix
    the Bookmarks tiles count the library, not the Statistics scope

    They fell back to computeStats(), which statsPageFilter narrows for the whole session.

Dashboard

  • Fix
    Alt+↑ / Alt+↓ moves a bookmark again

    moveCurrentBookmark() resolved the list with row.closest('[data-category-id]'), and every row carries that attribute itself — closest() tests the element first, so the "list" was the row, no siblings were found and the shortcut returned false on every press. Shift+Alt+←/→ had the same root cause with a worse outcome: an unqualified selector matched categories, lists and rows alike, so "the category beside it" was usually the next row.

  • Fix
    switching pages reuses what is already loaded

    Health status writes land in bookmarks-*.json, which GetDataRevision() hashed, so every ping moved the revision and dropped the client's page cache — three fetches on every switch. The revision now hashes bookmark content via bookmarkContentFingerprint(), leaving status out.

  • Fix
    a dropped block list no longer empties a page of its widgets

    blocks became null on a failed request and _applyLoadedPageData read that as "this page has no widgets"; undefined now means "not answered" and keeps what is on screen.

  • Fix
    status writes are batched

    One write per result outside a checking round, and the viewport observer starts one check per row scrolling in; they are collected for 400 ms instead.

  • Fix
    the sort-locked drag hint follows the sort mode

    The guard flag was one-shot on a DOM element the incremental render reuses, so the tooltip named whichever mode the category was first given, and returning to manual order left a hint saying dragging was impossible.

Inbox

  • Fix
    marking a link unread survives a fetch in flight

    fetchItems() snapshots read stamps before its request and re-applies them after; a deliberate unread in between was overwritten by the stale stamp.

  • Fix
    Shift+↑ at the first row no longer selects everything

    moveKeyboardSelection wraps, which is right for a plain arrow and wrong while extending a selection.

  • Fix
    triage reports the run it walked

    renderDone counted queue.length, but afterAction splices out every delete, snooze and promote; a fully-cleared run closed without showing the panel at all.

  • Fix
    undo after "clear read" restores only what was deleted

    Snapshots were taken for every target before the deletes rather than only for the ones that succeeded — the same defect bulkDelete had already fixed and documented.

  • Fix
    a stale selection anchor is cleared with the ticks

    Six sites cleared checkedIds on a filter change and left checkAnchorId standing.

Health

  • Fix
    a failed preview is retried in the next session

    _previewFailed was never cleared and the focus instance is cached for the tab's lifetime, so one network blip left a card blank until a full reload — the opposite of what the comment beside it promised.

  • Fix
    restoreKeptPlace() is not overrun by a smooth scroll

    The animation kept running for hundreds of milliseconds after the three-frame settle gave up.

  • Fix
    a failed refresh reaches the caller

    fetchReport's refresh-join used .finally(), which resolves with the original promise's value and left the inner rejection unhandled, so the caller saw a success and showed no error.

Config

  • Fix
    the Collections tab's list keyboard works

    renderCollectionStats() emits read-only .config-crud-row items with no key, and being first in the DOM they took index 0 where listRowKey() answered null — up, down, g and Enter were all dead on that tab. getListKeyboardRows() now offers only rows that have a key, which also puts the keyboard legend under the list the keys actually drive.

  • Fix
    the right-click menu keeps its own keys

    Both the menu and the config view bind a capture listener on document, and the config one is registered at startup so it always ran first: Enter on "Delete" opened the bookmark and stopImmediatePropagation() meant the menu never saw the key. The check-mode submenu's o and m accelerators went the same way.

  • Fix
    a full list repaint keeps focus on its row

    repaintBookmarksList() replaced every row without preserving focus, so "Select" from the menu dropped it to <body> and j/k walked the section rail instead of the list.

  • Fix
    a tab does not refresh against its own settings save

    Nothing recorded a save made locally in _serverSettingsRevision, so the next focus read the tab's own change as another device's and ran a full settings refresh, discarding anything typed but not yet committed. saveColorsData() got the same treatment, since colors.json is hashed into the same fingerprint.

  • Fix
    the storage-sync drain is reachable

    It sat after the try/finally, and both branches return from inside the try — a return runs finally and then leaves the function, so the drain was dead code on the path that needed it.

  • Fix
    a help fetch in flight is not reused for another language

    _helpLoading carried no language, so a request for German could join an English fetch and merge English prose into the German bundle, stamping it as loaded.

  • Fix
    a promo no longer eats the Escape that was leaving the view, or pulls an open menu out from under the pointer

Docs

  • Fix
    SaveSettings no longer discards a migration marker set in the same call

    The "preserve markers from the stored file" block read the file as it was before the save and overwrote the incoming value with it. GetSettings() flips a marker in memory only and never writes, so the first save after any migration ran carried a marker this block replaced with the stale false still on disk — leaving the migration eligible to run again, for all seven markers, not only a newly added one. Markers now only move false → true.

  • New
    hideFromModal is lifted from every release that carried it

    v1.4.5.2 was the last one holding it. The flag and the code that reads it stay, but no release uses it: a reader stepping back through the notes should not find a version missing between two that are there.

Only docs and tests changed in this release.

v1.4.6 Changes in Link previews, Keyboard and Under the hood. +3 3 fix Read the post

Changes in Link previews, Keyboard and Under the hood.

Link previews

  • New
    the preview picture is fetched by nextDash, not by your browser

    Hovering a bookmark used to make your browser ask that site for its picture directly, which told the site you were looking at your own dashboard. It also failed outright against a host that refuses to serve its image to other origins — claude.ai was 2 of the 16 pictures in a real cache, and the third-party traffic was all 16. The server now fetches the card's image and the site's icon, stores them under data/preview-images/, and the card draws from your own address. The first hover on a bookmark shows the card without its picture: the download runs in the background so one slow host can never hold up the card, and the picture arrives on the card that is already open, without a reload.

  • New
    none of it is compulsory

    Unticking Image in the card's row checklist under Config → Appearance → Display stops the pictures being drawn and being fetched — the checklist and the card's mode are read on the server before anything is downloaded — and setting preview cards to Off stops all of it, icons included. An install that wants none of this stores nothing and contacts nobody.

  • New
    Config → Icons & previews says what the picture cache is using, and can empty it

    A size to cap it at (50, 200 or 500 MB) and a button to remove every stored picture. Nothing is lost by clearing: each one is fetched again the next time it is needed, because the address it came from is kept.

  • Fix
    the grey tooltip no longer sits on top of the preview card

    The card removes the native tooltip from the row, but since v1.4.4 the text also sat on the row's label and on the whole category list when a sort order locks dragging — and a tooltip on a child wins over an absent one on its parent. Both now stand aside when a card is coming. With preview cards off the tooltip is unchanged, and the drag hint still appears as a notification when a locked row is dragged.

Keyboard

  • Fix
    a digit switches pages again instead of opening the search palette

    Both answered the same keystroke on the same element, so which one won came down to load order, and the dashboard's own handler stands down whenever the palette is open. Pressing 2 could therefore open the palette and leave you on page 1. The palette now leaves a digit alone when it names a page that exists; a digit beyond the last page still reaches it, and on Inbox, Health and Config a digit is unchanged.

Under the hood

  • Fix
    the bundle's source map is accepted again

    Safari reported both dashboard.js.map and search.js.map as having an invalid sourcesContent and dropped them, so a stack trace named dashboard.js and a line number nobody could place. The map set sourcesContent to null, and the spec makes that key an optional array. The originals are served from disk under their own URLs, so the key is now left out.

Only docs and tests changed in this release.

v1.4.5.3 Changes in Dashboard. 1 fix

Changes in Dashboard.

Dashboard

  • Fix
    a deleted bookmark leaves the page there and then

    The delete always persisted, but the row stayed on screen until a reload — and stayed bound to a bookmark that no longer existed, so it then ignored its own context menu. Adding a tag showed the same damage for a moment. ensureCategorySortControls() found the chevron with titleEl.querySelector(), which matches at any depth, then passed it to titleEl.insertBefore(), which requires a direct child. The chevron moved into .category-title-trailing in v1.4.4, so the call threw NotFoundError and took down the patchBookmarkData() pass with it, leaving every category it had not reached yet holding stale rows. The controls go in beside the chevron now, in the wrapper the full render already builds.

Only docs and tests changed in this release.

v1.4.5.2 Docs and tests only. docs

Docs and tests only.

Only docs and tests changed in this release.

v1.4.5.1 Changes in Pages & tags. 1 fix

Changes in Pages & tags.

Pages & tags

  • Fix
    one row at a time carries the keyboard cursor

    listRowKey() knew five row kinds — page, category, tag, finder, collection — but not the widget rows interleaveWidgetRows() splices into the categories list, which carry data-block-row. Those returned null, and applyListKeyboardSelection() compared with === against a stored key that is also null until an arrow key is pressed, so every widget row matched at once: thirteen of twenty-four rows wore the cursor accent the moment the tab opened. Widget rows have a key of their own now, and a row without a key is never the cursor regardless of what is stored. The same null guard was applied to the bookmarks list, which had the identical comparison.

Only docs and tests changed in this release.

v1.4.5 Changes in Widgets and Health and inbox. +7 6 fix

Changes in Widgets and Health and inbox.

Widgets

  • New
    every service signs in the way it actually wants

    Four presets take their key in the query string and offer no header form — SABnzbd, Tautulli, Pi-hole v5 and Plex — and one, qBittorrent, has no key at all: it hands out a session cookie that expires. All of them showed no sign-in block, so the key box vanished and the reader was left editing the address by hand. They ask for the key in the same box as everyone else now. The value goes to the credential file like any other, the address keeps a placeholder, and the server fills it in per request. qBittorrent asks for the username and password instead, signs in for the cookie, and signs in again when it lapses — a refusal is what says the session has gone, which is correct where a timer would only be a guess. The cookie is held in memory and never persisted.

  • New
    a stored key can be looked at

    A key typed into a widget went into the credential file and never came back, so an Authorization header missing its Bearer prefix looked exactly like a correct one and the service answered 401 either way. There is an eye beside the box. GET /api/health/credentials/reveal is narrow on purpose: only widget: ids, one named field per request, behind the write token, and every reveal logged by id and field rather than by value. The presets seed the scheme too — Bearer , Token or PVEAPIToken=, whichever that service takes — and saving a box holding only the scheme is refused.

  • New
    a path can name a list entry the way the service names it

    Home Assistant answers /api/states with every entity in one array, so naming one by position meant [150] — an index that moves the moment a device is added. A path can say sensor.temperatuur_beneden now and find that entry wherever it sits, then carry on into it for an attribute. The explicit form, [entity_id=…], does the same and stays for a list keyed by something unusual.

  • New
    a Found column beside each path

    The trial always knew what every figure read, but it said so in a block below the address, the sign-in and often the fold. The answer sits in the row now; a path that matched nothing says so where it is being typed.

  • New
    the answer can be searched

    A service answering with hundreds of entries is not something to scroll. Typing part of a key shows the lines that mention it with two lines of context either side, and nothing is asked again — it filters what already came back. The shown body grew from 16 KB to 256 KB, because searching what was cut off finds nothing.

  • New
    four more formats

    Speed reads a line rate in bits and thousands, the units a connection is sold in: 1.046 Gbps rather than 124.703 MB, and it scales down to 94.000 Mbps on its own. Power scales watts through kW and MW and keeps the sign, so a P1 meter exporting reads -1.03 kW. Temperature carries °C or °F from the weather setting and does not convert — the sensor already reported in its own system's unit. Data size asks which unit the service counted in, because Size reads bytes and SABnzbd reports megabytes.

  • New
    decimals per figure

    Auto, or 0 to 3. It applies to any figure carrying a number, text included, and the value is brought to the scale its unit names before the places are counted.

  • Fix
    trying an address uses the key on screen

    The payload carried only a credentialId, a reference to what is stored, so a widget being set up for the first time tested itself anonymously and got a 401 — indistinguishable from a wrong key, which is the one conclusion the panel exists to rule out. The typed sign-in travels with the request now, in whichever form the service takes, and is written nowhere.

  • Fix
    a refused trial says which refusal it was

    Every failure read "check your write token", including the rate limit reached after a few minutes of filling in a widget. The status decides now: 429 says to wait, 401 and 403 keep the token wording, 400 points at the address, 5xx at the log.

  • Fix
    the figures table lines up

    The header and the rows are separate grids given the same track list, and an auto track measured an empty span in one and a Delete button in the other — so every heading sat above the wrong control.

  • Fix
    a preset says which part of its address to fill in

    Home Assistant names an entity and Proxmox a node, and neither has a default; left as YOUR_SENSOR the service answers 404 and the note talked only about the token.

Health and inbox

  • Fix
    opening the health view shows the top of it

    The active filter pill was brought back into view with scrollIntoView on every render, and that moves every scrollable ancestor including the page — so the header scrolled away to bring a pill nearer the middle of a row that was usually not overflowing.

  • Fix
    the inbox toolbar takes the health view's two-row shape

    Pills on a full-width row, search and the selects beneath. The two views are read one after the other, and the inbox's search box used to move every time a pill appeared or went.

Only docs and tests changed in this release.

August 2026

v1.4.4.1 Changes in Widgets. +5 2 fix

Changes in Widgets.

Widgets

  • New
    a custom widget can be tried before it is saved

    The tile is the only place a custom widget's answer was ever visible, and all it can say about a path that matched nothing is —; four of them look identical whether the address is wrong, the key is wrong, or the JSON simply nests one level deeper than the boxes say. Config → Widgets → Settings now carries a Try it block under the figures: Ask now makes the request the panel describes — the address as typed, GET or POST, the credential it would name once saved — and shows the document that came back, indented and in the service's own key order, beside the figures the tile would draw from it. The facts of the request sit above both: method, host, status, how long it took, how much arrived, and whether a sign-in went with it, which is the difference between the key is wrong and no key was sent. A service that explains a 401 or a 404 in its body is shown that body, which the tile reads and throws away. POST /api/widgets/custom/test, widgets_custom.go, dashboard-config.js.

  • New
    Keep watching repeats the request while you look at it

    Every 5, 10, 30 or 60 seconds, with the figures that moved on the last beat marked for a moment — for a queue draining or a service coming back up. Chained rather than an interval, so a slow service is asked again after it answers instead of accumulating a queue of requests behind it; nothing is asked while the tab is in the background, exactly as the tile asks nothing there; and it stops itself after five minutes, saying so rather than going quiet. One panel at a time. Every beat is a request to a machine that never agreed to be polled, which is also why the interval is a list starting at five seconds rather than a number box.

  • New
    GET or POST is a setting again

    The server has accepted both since the widget shipped and the manual said so; the panel offered neither, so the only way to give a widget POST was to edit bookmarks-N.json by hand. It is a dropdown beside the address now. Nothing is sent with either method — POST is for the services that answer a statistics endpoint on that method and no other, not so a tile can change something.

  • Note
    the test route takes a config rather than a widget id

    The tile's own route deliberately does not: the address is stored, so it cannot be talked into fetching something by asking. This one is behind the write token, and whoever holds that can store the same config on a widget and press refresh at it — so it reaches nothing that was not already reachable, and saves saving a widget that is still being written. The same sanitiser, the same address checks, the same outbound client, and no cache is written: a draft that was never saved must not become what the tile draws.

  • New
    a stored key can be looked at, from the panel that stored it

    A key typed into a custom widget goes to the credential file and never comes back: the panel is drawn from the shape around it, and the box over a saved one says Set — type to replace. That rule keeps the secret out of bookmarks-N.json, out of every export and out of the browser, and it is right about all of those — but it is also why an Authorization header missing its Bearer prefix is invisible, since the service answers 401 exactly as it would to a wrong key. There is an eye beside the box now. GET /api/health/credentials/reveal is the one route that hands a secret back, and it is narrow on purpose: only widget: ids, so a shared sign-in stays write-only and the store cannot be walked; one named field per request; behind the write token, like PUT and DELETE; and every reveal logged by id and field, never by value. An unknown id and a shared id give the same 404, so probing the route reveals nothing about which sign-ins exist.

  • Fix
    a service whose key goes in the address asks for it like any other

    SABnzbd, Tautulli, Pi-hole v5 and Plex take their key in the query string and offer no header form, so the panel showed no sign-in block at all: the API key box vanished and the reader was left replacing YOUR_KEY in the address by hand. The value goes to the credential file like any other, the stored address keeps its placeholder, and the server fills the parameter in per request — so the key stays out of bookmarks-N.json and out of every backup and export.

  • Fix
    a preset fills in the scheme its API key needs

    Choosing Speedtest Tracker gave an address, three paths, a header name and a tile that answered 401: an Authorization value takes a scheme in front of the token, the box asks for "API key", so the token goes in bare and nothing on screen distinguishes that from a wrong key. The presets carry the scheme now and seed the box with it, shown rather than masked — it is not the secret, it is the half that was missing. Per preset, not a constant: Paperless takes Token , Proxmox takes PVEAPIToken=. Saving a box holding only the scheme is refused, since that would file the word "Bearer" as the key and send a header that looks filled in and authenticates as nothing.

  • New
    a Speed format, in the units a line is sold in

    data.download is bytes per second, so a gigabit connection read 124.703 MB beside the word down — the same measurement as the 1 Gbps on the contract, expressed so differently the two cannot be compared at a glance. The new format reads bits and steps in thousands: 1.046 Gbps, scaling on its own so a slower line reads 94.000 Mbps rather than 0.094 Gbps. Three decimals, because a connection is compared against itself and one decimal rounds this week's 1.046 and last week's 1.038 to the same figure. The Speedtest Tracker preset points at download_bits and uses it.

Only docs and tests changed in this release.

v1.4.4 Changes in Languages, Search, Dashboard and What's new. +4 10 fix

Changes in Languages, Search, Dashboard and What's new.

Languages

  • New
    Chinese is nextDash's fifth language

    简体中文 joins English, Dutch, German and French, and it is the whole of the interface rather than a partial pass: the dashboard and its cheat sheet, the command palette, the setup wizards, every config tab from widgets to backups, the statistics, the health view and its reasons, and all 209 headings and 19 prose bodies of the Help tab. Nothing falls back to English on the way through. locales/zh.json, extension/locales/zh.json.

  • Fix
    locales/zh.json is valid JSON again

    A merge was committed with its conflict still in the file, leaving seven hundred lines between markers — so the file stopped parsing and every consumer stopped with it, the locale validators included. Both sides held the same 349 keys and no key existed on only one of them; what differed was the values, one side carrying the translations and the other the English placeholders they were written over.

  • Fix
    the theme browser speaks every language

    Its title, search box, the All / Light / Dark / Favourites segments, the {shown} of {total} themes count and the trait words each card is described by — warm, cool, vivid, muted, high contrast — were English in all five locales. A screen added after the last translation pass, invisible because every call carried an English fallback that read perfectly well. Thirty-one strings in all, the merge-duplicates and open-broken dialogs among them. locales/*.json.

  • Fix
    zh.health drops 124 keys nothing reads

    The section was cut back to the nineteen the code actually looks up; zh had never been through that pass and kept an older, larger lot.

Search

  • New
    results group by why they matched

    One letter filled the screen: typing g put Gmail and widGetonderzoek in the same column, in the same style, in an order nothing explained. The scorer already knew the difference — a name that starts with the query scores 700, one that carries it mid-word scores 300 — but kept only the number, so the list was honest and useless at once. Every result now carries the reason, which cannot be read back out of the score (an exact domain match is 1000 × 0.3 = 300, exactly what a mid-name substring earns). The strong matches stay open, the weaker fold behind a heading and a count. One kind of match renders flat with no heading at all; if every group is shut the strongest opens itself; an open group stops at twelve rows and offers the rest. fuzzy-search.js, search.js, search.css.

  • New
    the ranking learns what you open, and what these keystrokes meant

    openCount and lastOpened are on every bookmark and drove the smart collections, the stats page and the opened: filter — everything except the search that ranks them, where the tiebreak between two equally-shaped names was whichever happened to be shorter. Usage settles it now, worth at most 90 against tiers 200 apart, so a favourite can order its equals and never overturn them. Separately, a pick is written against the exact query that produced it, so mail becomes your own alias for Gmail without a shortcut for it. That memory is a floor rather than a bonus, capped at 1090 against the 1099 an exact name scores: typing a thing's full name still gives you that thing. Stored in settings, so a backup carries it and a second browser inherits it. internal/app/models.go.

Dashboard

  • Fix
    switching a bookmark to Periodic says so

    Choosing Monitor confirmed the change and choosing Periodic showed nothing, so the click read as ignored while the write had in fact landed. Two faults stacked: the one-time search-mode tip was sent as info rather than promo, and AppNotification only steps aside for a promo that is on screen, not one waiting in the queue. A real notification now drops any promo still queued. app-notification.js, dashboard-promos.js.

  • Fix
    a tab stops reloading itself over its own config change

    publishConfigSync stores its payload in localStorage, whose event fires only in other tabs, and in sessionStorage so a tab hidden during the write picks it up on return. The storage handler drops a payload carrying its own tabId; maybeRefreshAfterConfigReturn did not — and a tab is never hidden during its own write. So after any save it found its own marker and ran the whole refresh on every tab switch: invalidate the page cache, loadData, loadPageBookmarks, loadAllBookmarks, renderDashboard, and the health report with them. dashboard-config-sync.js.

  • Fix
    a number that was never stored is not a changed setting

    Config → Overview counted settings the reader had never touched. isFieldDefault compares a numeric field with Number(value) === def, and almost every numeric setting is omitempty on the Go side, so one sitting at its default of 0 is absent from the JSON the browser receives — and Number(undefined) is NaN, which equals nothing. certWarnDays, healthCheckTimeoutSeconds and bulkFaviconConfirmFrom all read as changed on a fresh install. dashboard-config.js.

  • Fix
    a health row's menu is clamped to the window rather than cut off

    The button path asked only whether the menu overflowed below and set --up if so, which anchors with bottom: 100% and has nothing to stop a menu taller than the space above it. Ten items, 452px, a wrap 450px down a 720px window: too tall either way, flipped up regardless, the first entry gone. Both directions are measured now, and when neither fits the menu sits against the top margin. Closing it clears that placement again: closeAllMenus only cleared the inline coordinates a right-click had written, because it tested for the --at-cursor class the clamp does not set — so a clamped menu kept its top into the next open and the ⋯ button put it where the clamp had left it. dashboard-health.js.

  • Fix
    a deep link to the health view or the inbox lands there

    loadData() opened them from the hash, before init() rendered the grid, so an arrival on /#health raced its own dashboard. Routed at the end of init now, where config already was. dashboard.js.

  • Fix
    the Monitored tile stops printing a sentence across the row

    1 of 6 not responding rendered under the count so the down state needed no hover, and took 227px where the other tiles hold 89 — on a row of seven that pushed the whole set sideways, and read as the row's headline rather than one tile's detail. The tile carries its count now; the count still turns red the moment a monitor is down, the title and the aria-label both name how many (aria-label replaces title rather than supplementing it, so it has to), and the fleet panel below prints the sentence in full. dashboard-health.js.

What's new

  • New
    the release list says new or fix in words

    A filled or hollow dot stood in front of every entry, which says two of them differ without saying how. The dot had replaced a chip for two good reasons — width, and a "new" tint drawn from --accent-success that on a green accent matched the version tag beside it — and both are answered rather than reverted: 0.62rem in a fixed 2.4rem track, and neither badge takes an accent at all. New is --background-primary on --text-primary, fix is --text-tertiary in a hairline border, so filled against outlined reads at a glance on any theme. Every release already carried the distinction in its data, so it is back on all of them. whats-new-modal.js, modal.css.

  • Fix
    v1.4.3's entry for shortcutDisplay said it defaults to hover

    It defaults to always, as the line below it already said.

Only docs and tests changed in this release.

v1.4.3 Changes in Widgets, Dashboard, Search, Health and Assets. +15 2 fix

Changes in Widgets, Dashboard, Search, Health and Assets.

Widgets

  • New
    Every figure on a custom widget can have its own size

    Normal, Large, Small or Bar, stored per figure. The custom widget was the only tile drawing its own flat rows rather than using the panel and parts every other tile uses, which is why it looked flat beside them. The bar is offered on a percentage and nowhere else: it draws a share of a whole, and a count carries no whole to be a share of. Its colour comes from the theme's own tokens. dashboard-widget-custom.js, dashboard-widget-presets.js, dashboard-config.js, dashboard.css.

  • New
    A Milliseconds format takes a value in seconds and shows whole milliseconds

    the AdGuard tile printed avg_processing_time as 0.0051589999999999995 under a label reading "avg ms": the field was formatted as text, which prints a float's full tail, and the value is in seconds, so the label was off by a factor of a thousand. The AdGuard preset uses the new format; any other service answering in seconds can. A widget already on a page keeps the format it was saved with. internal/app/widgets_custom.go.

  • Fix
    A figure on a custom widget can be edited again

    opening one for editing left the form empty, so correcting a figure meant deleting it and adding it back.

  • Fix
    The figures down a widget's rows line up

    each row measured its own numbers, so a column of them sat at a different distance from the edge on every line.

Dashboard

  • New
    shortcutDisplay replaces the showShortcuts boolean

    always | hover | never, defaulting to always. The boolean answered one question (is the letter on screen) and the useful answer was a third one. In hover the label is out of the row's flow, so the grid's shortcut track collapses and the name takes that width back — about five characters a row — and it floats in over the right end of the name while the pointer or keyboard selection is on it. The aria-label names the shortcut in all three modes, never included. The control carries the chrome handler it always needed, so it comes off the KNOWN_BROKEN list in config-behavior-realtime-coverage.spec.js and takes effect without a reload.

  • New
    The shortcut letters are on for every install

    a fresh one starts at always, and ShortcutDisplayAlwaysMigrated turns them on once for existing installs, including those whose legacy showShortcuts boolean said no and the never that would otherwise have been derived from it. A shortcutDisplay already in the settings file is an answer to this question and is left alone, so someone who picked hover keeps it; the marker keeps the migration to one run, so switching the letters off afterwards sticks.

  • New
    The floating button bar stops letting the page read through it

    bookmark rows scrolling underneath showed through the bar.

  • New
    A row builds only the marks it draws, and search waits for the key that opens it

    two rendering costs paid on every load that nothing asked for.

Search

  • New
    interleaveMode moves from Appearance → Layout to Behavior → Search, as Switch Search Mode

    the checkbox read "Interleave categories across columns" and no renderer has ever read the field: search.js is its only consumer, the Go comment on it says search, and the statistics page already called it "Interleave search mode". Ticking it to rearrange columns changed how a bare query is read and moved nothing.

  • New
    Shift+Q toggles the search mode from the dashboard

    toggleSearchMode() on the dashboard writes the same stored value the checkbox does, tells the running search component directly rather than waiting for a reload, and raises a toast naming the mode. A failed save puts the setting back rather than leaving the screen and the file disagreeing. The key is registered in dashboard-setup.js beside the other global Shift+letter keys, and is on the cheat sheet.

  • New
    The Switch Search Mode info panel said ;

    left over from the prefix introduced and withdrawn earlier the same day. It reads / in all four locales, and the sentence explaining that / does the same as ; went with it.

  • New
    A missed shortcut points at the names it did not search

    with Switch Search Mode off a bare query looks for a shortcut only, so typing a bookmark's name reported nothing while the bookmark sat on the page behind the overlay. When the shortcut search comes back empty and a name search would not, the overlay appends one row naming the count and the key; Enter or a click runs the query the other way. With no name match either, "nothing found" stays the answer.

  • New
    A query that arrives from outside is searched by name

    a query from the address bar, a deep link or a shared URL was matched against shortcuts only. Arrived queries are widened to names; shortcut matches keep the top of the list.

  • New
    ; was introduced as a second mode-switch prefix and taken back out in the same release

    it already opens the inline editor on a bookmark row and has since v1.1.1. The check that cleared it read the cheat-sheet registry, where that binding is deliberately undocumented, so the wrong list gave the wrong answer. / is the only mode switch, as before. The _hasModeSwitchPrefix / _stripModeSwitchPrefix helpers introduced alongside it are kept: they fold four scattered startsWith('/') tests into one question. tests/search-mode-switch-prefix.spec.js pins that ; is not a prefix.

Health

  • New
    A round of checks is one write, and it follows the bookmark

    each result was written on its own, so a round interrupted halfway left the report describing a mix of two runs.

Assets

  • New
    A stack trace out of the bundle names the file it came from

    source maps survive the bundling step.

  • New
    The stylesheets and scripts changed this week are served

    the hash table had drifted from the files on disk.

Only docs and tests changed in this release.

v1.4.2.4 The browser's Back button works, a triage run can be finished, and the two +3 12 fix

The browser's Back button works, a triage run can be finished, and the two

Navigation

  • New
    Back and Forward move through nextDash

    Opening the inbox, health or config, or switching bookmark page, now leaves a history entry. Before, none of it did: history.length never moved, so Back stripped the address bar and left the view standing — the URL said one thing and the screen another. Worse, from a full-container view a numeric hash was actively reverted, so Back to a bookmarks page did nothing at all.

Inbox

  • Fix
    a triage run can be finished

    Three faults at once. The queue held every link the filter showed including ones already read, so an inbox of 5 unread and 35 read handed back all 40 and asked you to decide again on work already done; it now walks only the unread, with the active filter still applying. The last card ends the run — "That is the lot. You went through 12 links." — instead of silently looping back to the first. And promoting a link returns you to the run where you left it: before, promoting closed triage, so clearing a backlog of 40 meant pressing t forty times.

  • New
    the inbox header reads like the health view's

    The two are siblings — same pills, same j/k, same shape of list — so the work that pulled health's rows up the page reached the inbox too. The count moved down to the subtitle line, where it sits level with health's score badge instead of a line above it. Triage and a new ⋯ get their own full-width row under the filters, so the button that matters most is where its health counterpart is. Mark read, Clear read, CSV, JSON, Import and Stats moved behind the ⋯, and the ℹ went to the far right where it cannot be hit while reaching for an action.

  • Fix
    five things the inbox knew and did not say

    Rows show where a link came from — extension, import, share sheet — with paste left unlabelled, since that is how most links arrive and saying so on every row is noise. A weekly trend line reads "N arrived and N were dealt with this week", with a link through to the full chart. Mark unread and tags were right-click only, which a phone has not got: they are now u and l, both listed in the keyboard legend. An empty filtered list gains a Clear filters button. And a tag filter matching nothing no longer claims "Inbox zero, nothing is waiting" while the links sit there hidden — the empty-state check counted the search box and the site filter and forgot the tag.

  • Fix
    the promote rate counts what left, not what was read

    It is labelled "of the links you decided on, how many became bookmarks", but the denominator also held every mark-read — and a link marked read is still sitting in the inbox with the decision to come. Two consequences: links that had gone nowhere counted as decisions, and any link read before being promoted counted twice. A store of 40 added links reported 43 of them decided. Promoted and deleted are the two ways a link leaves, and they are the whole denominator now. The figure on your install will change, in some cases substantially.

Health

  • Fix
    the summary reads as a line, not a wall of cards

    Ten bordered tiles became one compact strip of figures, asserted under 48 pixels tall. Six of the ten repeated a filter pill sitting directly beneath them. Clicking a figure still filters, and the strip wraps rather than scrolling sideways.

  • Fix
    every filter is on screen

    The pill row wrapped instead of scrolling: at 1280 pixels four filters — Missing category, Missing preview, Certificates and Healthy — were cut off past the right edge with nothing to say they existed. Fifteen pills, roughly seven visible. The one-time "this row scrolls" hint went with it, since there is nothing left to explain.

  • New
    the toolbar keeps what you use and files the rest

    Work through and Rot report stay on the bar; Export rows, Re-test, Checking off, Open broken, Merge duplicates, the bulk-enable buttons and the settings link moved behind a ⋯. Eight buttons across two lines became two and a menu. The menu opens under its own button rather than at the window's far edge, where it read as belonging to something else.

  • Fix
    the filter note explains a filter you chose

    "Every bookmark, whatever its state" told a reader of an unfiltered list what they were already looking at. It stays on every other filter, where it explains a real rule — what makes a bookmark stale, why one counts as unused.

  • Fix
    three ways the view moved without being asked

    A re-check finishing after you left no longer wipes the bookmark grid and paints the health list over it: health owns the app's slow work, a re-check of an unreachable host runs 10-20 seconds, and the render that landed afterwards never checked whether health was still on screen. The Monitored list keeps your place across its sixty-second refresh and its refresh on returning to the tab — measured, a reader at 400 pixels was put back at 266. And the duplicate-group menu no longer leaves a click handler bound for the life of the page, or a merge waiting on a promise that never settles, when a re-render takes it away.

Config

  • Fix
    previewing a theme shows that theme's backdrop

    Scrolling the themes changed the colours and left the texture behind, so the preview showed a new palette wearing the old theme's pattern — a combination matching no theme at all. The backdrop's shape (scanlines, grid, hatch, dots) is chosen by rules that key on the theme's name, and the preview kept the old name. Both routes were affected, the dropdown and Browse…; picking Random never was, and that is what pointed at the fix.

  • Fix
    Escape closes the theme picker on the first press

    With a promo card on screen — the ordinary state until they have been dismissed — the first press cleared the promo and left the picker open, still previewing; only a second press closed it and put your theme back. The picker was opened deliberately and is showing a live preview, so it takes the key first.

  • Fix
    four ways config said one thing and did another

    One click on Export produced two CSV files, every stats action button having been given two click listeners. Changing an Appearance control dropped focus to the page body, so the next Tab restarted at the top. Switching page threw away unsaved Widget edits without asking — Widgets being the one section that does not save as you go — and now asks, putting the page selector back if you decline. And the archive URL said "Saved" while the server had quietly substituted the default, which it does when the address carries no {url} placeholder; the field now shows what was actually stored.

  • Fix
    eight settings can tell you they changed

    A setting with no declared default reports itself unchanged whatever it holds, so it never offered its ↺ and never counted towards the Overview's "N settings differ from the default". Of the 93 fields the Behavior schema renders, 90 had a default and nine did not; eight now do. Keep settings on this device only stays the documented exception, since it lives in this browser rather than in the settings file and there is no stored default to compare against.

Housekeeping

  • Fix
    the inline bookmark editor is gone

    757 lines of JavaScript and 193 of CSS that could not run. Editing moved to a modal long ago and left the old editor behind with its gate permanently shut. Nothing changes on screen.

Docs

  • New
    hideFromModal is lifted from every release that carried it

    v1.4.2.1, v1.4.2.2, v1.4.2.3 and v1.2.1. Each was held back while it was fresh, so a round of additions would not push aside a large release. Four had accumulated, which is more than the flag was meant to cover: between them they hold the guided-tour replay and every theme's backdrop, neither of which is a footnote. They are announced now, along with v1.4.2.4 itself, so the modal says what this changelog has said all along.

Only docs and tests changed in this release.

v1.4.2.3 A tour can be asked for one at a time, and the two hundred themes that all +3 1 fix

A tour can be asked for one at a time, and the two hundred themes that all

Behavior

  • New
    each guided tour can be replayed on its own

    Six tours exist and five could be seen exactly once: Health, Inbox, Fresh, Widgets and the column-spread hint each record a tip id on first run and never offer themselves again. The only way back was Show quick-start card again, which calls clearSeenTips() and empties the list wholesale — right when handing an install to someone else, far more than "show me the Health one again" asks for.

Appearance

  • New
    all 107 theme families choose a backdrop

    --theme-pattern-image defaults to dots for every theme and the block below it named fourteen exceptions, so 200 of 214 variants painted dots — the theme browser changed the palette and left the texture identical, which reads as three backdrops that do not work. Each family now names one in theme-depth.css, assigned by character: hatch for paper, cloth and earth, grid for circuitry, editors and steel, lines for screens, neon and signal, dots for mist, water and cool. Final spread across the 214: 56 hatch, 54 grid, 54 lines, 50 dots. data-pattern="auto" still means "whatever the theme asks for", and anything chosen in Appearance → Backdrop still overrides every theme.

  • Fix
    four screen themes lost their scanlines in their light half

    retro-crt, neon-grid, cold-cathode and static-noise named only their -dark selector, so switching one to light dropped the lines and left it looking like any other theme wearing the same name. Both halves are named now. Found by the new spec rather than by eye — at 214 variants, reading the file is not a check.

  • New
    tests/theme-backdrop-variety.spec.js walks every one of the 214 variants and fails on two things that are otherwise invisible

    a family nobody assigned (falls back to dots and looks deliberate) and a family whose halves disagree.

Only docs and tests changed in this release.

v1.4.2.2 The refresh interval added in v1.4.2.1 turned out to be unusable without +2 1 fix

The refresh interval added in v1.4.2.1 turned out to be unusable without

Widgets

  • New
    Refresh now, in the widget's own menu

    refresh=1 has been on the server since the custom widget shipped, behind the write token, and nothing in the app ever sent it. So a reader who corrected a wrong API key kept seeing the same error for the thirty seconds a failure is held for — a hold that is right, since it stops a service that is down being retried by every open dashboard, and wrong only for the one person who has just fixed the reason. refreshCustomWidgetNow in dashboard-render-core.js sends it, writes the answer straight into the tile's own store so the redraw does not spend a second call at the service, carries the keyboard cursor across, and restarts the clock so a beat does not arrive a second later. Offered only on custom: every other tile draws from what nextDash already holds, and a menu entry that does nothing is worse than no entry.

  • New
    the interval says what it accepts, and an ℹ says how to choose

    The bounds were on the <input> element, where a browser can read them and a person cannot. The field now carries a hint line — Between 30 seconds and 24 hours. Leave empty for 5 minutes. — and an ℹ opening the same AppModal dialog every setting in config uses, reached through a new info property on the widget field table rather than through FIELD_META, which is keyed by settings-field name and cannot see widget keys. The label changed from Ask again after (seconds) to Refresh every (seconds): the old name described the cache, which has been half the story since the tile started refreshing itself.

  • Fix
    a number outside its range is clamped, not dropped

    sanitizeWidgetConfig stored an int only when it was already within field.Min..field.Max, so ttl: 5 vanished from the saved config and the tile fell back to undefined || 300 — five minutes, with nothing on screen saying the value had been refused. It clamps through clampInt now, for every int field: rows, days, warnDays and ttl alike. A negative is still refused rather than clamped, and so is a string or a fraction: those are a caller sending the wrong shape rather than a reader choosing badly, and absent is what the renderer reads as "use the default". Both existing tests that pinned the old behaviour were rewritten rather than deleted — TestOutOfRangeValuesFallBackToTheDefault became TestOutOfRangeNumbersAreClampedAndNonsenseIsDropped, and the custom-widget test now asserts the floor instead of absence.

Only docs and tests changed in this release.

v1.4.2.1 The one tile that reads from outside now keeps itself up to date. +1

The one tile that reads from outside now keeps itself up to date.

Widgets

  • New
    a custom widget refreshes itself, on its own clock

    Every other widget reads something nextDash already holds, so a repaint brings it up to date; the custom tile is the only one that asks the outside world, and nothing on a dashboard left open ever asked again. Its ttl was a cache expiry, not a schedule, so the figures stayed at whatever they were when the page loaded.

Only docs and tests changed in this release.

v1.4.2 Widgets answer to the right-click and the keyboard the way categories do, Health +11 10 fix

Widgets answer to the right-click and the keyboard the way categories do, Health

Widgets

  • New
    a widget is renamed, resized and closed from its own header

    Right-click a widget title for rename, one-column/two-column, fold, settings and close. Rename reuses the category long-press/F2 route rather than a second one, so the same input, the same Escape and the same save path serve both; the name it writes is the one Config → Widgets shows. Close is disable in Config → Widgets, not a delete, so the widget and its settings survive being put away. dashboard-category-menu.js gained bindWidget/showWidget, and saveWidgetPatch in dashboard-render-core.js sends only the widgets key, rolls back on failure and guards on the page still being the one that was edited.

  • New
    the keyboard goes into a widget instead of around it

    Arrow keys step into a widget body and move through its rows the way they move through a category's, Enter opens the row under the cursor, and every action in the right-click menu has a key. keyboard-navigation.js now counts widget-body buttons as navigable, and the cursor is captured and restored across a widget refresh so a live-updating tile does not throw the reader out.

  • New
    a tour of what a custom widget can reach

    , opening the first time Config → Widgets is visited. Seven steps with a CSS hero animation; static/js/widgets-tutorial.js and its stylesheet, loaded lazily.

  • Fix
    the uptime tile fills itself in

    It rendered Open Health once to fill this in until the Health view had been visited, because the tile read a store that only that view populated. ?view=facts now carries uptime7d, downSince and a per-bucket heartbeat string, and the row filter keeps monitored rows that have no samples yet rather than dropping them.

  • Fix
    a width change leaves the block where the reader is looking

    Switching one column to two rebuilt the grid and sent the page to the top. redrawKeepingPlace anchors on the block's viewport offset and settles in a bounded loop.

  • Fix
    three ways the grid lost track of a widget

    The rename input's keys reached the header handler, so Delete deleted the category being renamed and Backspace closed the widget; Shift+W was swallowed because the width toggle built a category id from a widget id; and only an address is opened by the menu's open action, http(s) only.

  • Fix
    thirty-nine widget strings were looked up where they were not stored

    They resolved to their own key names on screen. A label() helper also returned the literal "undefined" for a missing key, since t() answers a non-string with String(key).

Status & health

  • New
    a bookmark can be told to stop reporting one condition

    n or z on a row, or the row menu, sets aside a stale, unused or broken flag for a bookmark you have already judged. The bookmark stays in the collection and keeps being checked; only that flag stops being raised. An Ignored filter lists everything set aside and one click puts a bookmark back. internal/app/health_ignore.go with add/remove/clear/untilMs, Bookmark.HealthIgnored, and HealthIssue.IgnoredFlags so the tiles and the filters cannot disagree.

  • New
    the filter row says once that it scrolls

    A one-time popover, shown only where the row actually overflows (scrollWidth - clientWidth > 8).

  • Fix
    acting on a row leaves you at that row

    Saving a copy or changing a setting scrolled the list back to the top. The first attempt at this landed the row at 299px where it had been at 727px, because scrollIntoView({block:'nearest'}) is not the same as staying put; the offset is captured and restored instead.

  • Fix
    the row menu is short enough to read

    It had grown past the height of many screens, so the entry you wanted needed a scroll to reach.

  • Fix
    a capture says why it failed, how big it may be, and when it is blank

    The monolith failed: exit status 1 message carried no reason: the quiet flag was suppressing the one line that said what went wrong. The limit moved from 32 MB to 52 MB. And a page that captures as an empty shell is detected rather than discovered on opening — captureTextScanner walks the file counting only text outside tags, script and style, because reading a fixed head of the file counted 129,805 characters of CSS as prose. The threshold of 500 characters was measured against real captures: 6 and 225 for two shells, 7,894 for an article.

Bookmarks

  • New
    every saved copy can be cleared at once

    Config → Bookmarks → Local copies gained a delete-all, confirming with the count and the space it frees.

Data & backups

  • New
    every log line carries a level and a component

    internal/app/logx.go wraps the standard logger with logError/logWarn/logInfo/logDebug and thirteen component constants, writing one shape: LEVEL component message. The floor is an atomic read, so a level that is switched off costs a comparison rather than a formatted string thrown away. A guard test forbids log.Printf outside that file.

  • New
    all 67 existing log calls were rewritten

    Not a search and replace: each got a level, a component, and a sentence written for someone who runs nextDash rather than one who reads its source. Request lines keep their established shape through logRequestLine, since the viewer reads their level from the status code.

  • New
    eight silent subsystems now say what they did

    A check round, a feed poll, an import, a capture, backup pruning, a failed write to the data directory, a custom widget's outbound fetch, and webhook delivery. writeFileAtomic is the one funnel every write to the data directory passes through, so it is where a failed one is finally reported — several callers had been dropping the error.

  • New
    Detail level and Activity trail, in Data & backups → Server log

    Quiet, Normal and Verbose decide what is written at all, taking effect on the next line rather than at the next restart; twelve channels decide what goes into the JSON trail, with Reset panel restoring the default pair. Settings.ServerLogLevel and Settings.ActivityChannels, applied by applyLogSettings at start-up and on save. NEXTDASH_LOG_LEVEL and NEXTDASH_ACTIVITY_LOG keep working and are overridden by the settings when those are set.

  • New
    the activity trail leaves the container log

    logActivity gained a sentence: the JSON goes to the trail file and the buffer, and the container log gets prose instead of activity: {…} between its readable lines. With twelve channels the old arrangement would have made docker logs unreadable. Security events log at WARN. Debug lines never reach the trail — it exists to be read back later, and a line per checked bookmark would make it useless within a day.

  • Fix
    the viewer reads the level a line declares instead of guessing it

    parseServerLogLine now takes the level and component from the line itself, falling back to inference only for lines that predate this and for the Go runtime's own output. That fixed a real misreading: checked 110 bookmarks, 2 failed was filed as an error because it contains the word failed. The Activity only filter matches on the channel names rather than on the word activity, which no longer appears in a trail line.

The dashboard

  • Fix
    coming back to the window leaves you where you were

    Switching to another window and back sent the app to the top of the page.

  • Fix
    a failed load says why, and only when you asked for one

    Failed to load bookmarks for this page had been appearing unprompted while nothing was wrong.

Only docs and tests changed in this release.

v1.4.1.2 A gesture widgets should have had from the day they arrived, and a health check +1 1 fix

A gesture widgets should have had from the day they arrived, and a health check

The dashboard

  • New
    a widget folds away like the categories beside it

    A widget is a summary, and a page carrying several of them has the problem a page of long categories has: the block you want is below the fold because the ones above it are open. Categories have folded since long before widgets existed, so this is the same gesture on the same header rather than a second one to learn — click it, or Enter/Space with it focused. Built out of what categories already have: the state goes into the same collapsedCategories map under the same page-scoped key (widget ids prefixed w_ so they cannot collide, and the existing prune of stale keys covers them without knowing they exist), the body moved inside the same .category-body wrapper so the collapse animation is the one already written, and Fold all picked widgets up for no new code at all because it works on data-collapsed. One rule did not follow for free: the body reserves min-height: 3.5rem so the packed layout does not shift when its figures arrive, and it is later in the stylesheet and equally specific, so a collapsed widget stopped 56px short of closed. The reservation answers a question that does not exist while the block is folded, so it lifts at data-collapsed="true" — measured at 0px closed against 154px open.

Status & health

  • Fix
    a site behind a login is not a page that does not exist

    Two bookmarks on a tailnet were reported down with Page says it does not exist while both sites were up. Neither said anything about being gone; it was the control-URL test in health_soft404_control.go that condemned them. A gated site sends every address it does not hand out to the same sign-in page, the probe's random path included, so the probe comes back 200 and the bookmark's body is that sign-in page — identical in length, well inside the fifth the comparison allows, and short enough to pass for a notice. Both signals agree and both are wrong. What separates the two cases is where the probe went: a not-found template answers on the address that was asked for, a gate redirects elsewhere. softControlVerdict now records that landing address — without its query, since a gate puts the path it turned away into a returnUrl — and a bookmark landing on the same address ends the comparison before length is consulted. A real soft 404, answering on its own address, is untouched.

Only docs and tests changed in this release.

v1.4.1.1 A round of fixes on v1.4.0, and three of them were things that had been quietly +1 10 fix

A round of fixes on v1.4.0, and three of them were things that had been quietly

What's new

  • Fix
    an upgrade shows its release notes again

    Two settings record that onboarding is over — quickStart.dismissed for the card, onboardingCompleted for everything allowed to appear afterwards — and an install can hold one without the other. That install goes quiet in both directions: quick start does not run because it is dismissed, and no unprompted card appears either because canShowUnpromptedUi refuses while onboardingCompleted is false. The release check said there is something new here on every load and the prompt was even scheduled — should true, timer set, canShowPostOnboardingPrompts false — and then nothing asked, for the lifetime of the install, with nothing in the interface able to fix it: the one thing that sets the flag is dismissing a card that no longer appears. Dismissing the card is finishing onboarding, so the two are reconciled when the disagreement is met.

  • Fix
    Replay onboarding brings the card back, not just the flag

    It cleared onboardingCompleted and left dismissed true, which is the same disagreement: the reader was promised the welcome tour and got nothing, and the install was left in the state that silences every unprompted card. Both are cleared now; setupDone is left alone, since replaying the tour is no reason to ask again for a language and a theme already chosen.

  • Fix
    the unseen-release fast path was unreachable

    schedulePostOnboardingPrompts takes a 120ms delay and prefetches the modal when there is a release the reader has not seen, but the branch sits behind else if (Number.isFinite(options.delay)) and the only caller passed delay: 900 — which is the default the branch exists to shorten. Measured at 900ms with no prefetch before, 120ms with the modal already fetched after. The caller no longer names the default, and the trap is written down where it is set.

Overview

  • Fix
    all ten posts from nextdash.cc reach the overview

    Three caps disagreed about how many there were. The parse stopped at exactly ten, which matches a feed of ten only until an eleventh is published and the oldest silently stops arriving; the byte ceiling was 512KB against a feed measured at 172KB whose tenth item starts at 97% of the file; and the window held six rows shared with releases and features. The parse cap is twenty and the ceiling 2MB, so ten is a floor rather than a ceiling, and the window is fourteen rows with ten reserved for posts. The reservation itself was wrong at that size — it asked whether the window held a post at all, which was fair while two were reserved and let one post stand in for the other nine at ten. Measured at nine before, ten after.

Appearance

  • Fix
    nineteen settings strings were never translated

    The Depth and Backdrop controls, every option in both (Flat/Soft/Rich, Follow the theme/Dots/Grid/Lines/Hatch/None), Browse… beside the theme, the widget title label, the message a source shows when it needs a token, and the On/Off pair — all present only as English fallbacks in t(key, fallback), in all four locale files. Two of them, themeDepth and backgroundPattern, are prefixes for keys built by concatenation, so the option names were missing too. 19 keys × 4 languages.

  • Fix
    a category spanning two columns says so with its rule

    The line under a category title fades out at 85% of its width, which is right for one column and lands well short of the edge across two, so a wide category looked like a narrow one whose line happened to be long. A wide category now gets a gradient that carries further and holds its colour longer — 70% accent against 55%, a full hairline where the old one had been transparent since 85%, reaching the end rather than stopping short of it. On a 752px title that is the last ~113px, which is exactly where the second column begins.

The dashboard

  • Fix
    only a scroll the reader asked for closes the category menu

    The menu closed on any scroll event. A re-render of the grid empties a column for an instant, the document gets shorter, and the browser clamps scrollTop back into range — which fires scroll exactly like a real one and took the open menu down with it. Wheel, touch, pointer and key are the marks a reader leaves; the clamp leaves none. Watched in the capture phase so a scroller that stops propagation still counts, and registered after the menu's own key handler so moving through the menu never reads as scroll intent.

Under the hood

  • New
    the Go sources moved to internal/app/

    259 files sat in the repository root, which put the entire server in the same listing as the README, the Dockerfile and the compose files. They are one package still — a move, not a split, which would mean exporting every identifier crossing a new boundary and breaking whatever import cycle models.go and handlers.go share. main.go stays in the root because it has to: //go:embed patterns resolve relative to the file that declares them and cannot climb out with .., so the directive has to sit beside static/, templates/ and locales/. Three things broke quietly on the way: the embed reached the package as a parameter, so under go test — where nothing calls Run — it sat at nil and every read through it failed; seven tests read static/… relative to the working directory, which go test sets to the package directory; and the Docker build stamped the version with -X main.buildVersion=, naming a package those variables had just left, which the linker does not object to. TestBuildVersionLdflagPathMatchesPackage reads the Dockerfile and fails on that mismatch now.

  • Fix
    the monitor interval fallback named 60 where everything else says 15

    dashboard-inline-edit.js fell back to 60 minutes when window.CheckMode was absent, against DEFAULT_INTERVAL_MINUTES = 15 in check-mode.js, defaultMonitorIntervalMinutes = 15 on the server, and 15 at the two other fallback sites. Latent rather than active — check-mode.js loads with defer and a bookmark is created on a click, so the fallback never fired — but it would have quartered the check frequency of that bookmark, silently, from the moment monitoring was switched on.

  • Fix
    formatBytes was defined twice in DashboardConfig

    The second definition silently overrode the first; measured over 0–1MB the two produced identical output, so nothing displayed differently, but the first was unreachable and editing it would have had no effect. The dead one is gone.

  • Fix
    the unused-locale-key check could not see a key built with +

    It recognises ` config.${x} but not 'config.backgroundPattern' + option…`, so every key in such a family was reported unreachable while being used on screen. It reads both forms now, and still reports a genuine orphan — verified by planting one.

Only docs and tests changed in this release.

v1.4.0 The largest release so far: seventy changes across twelve areas, four of them new ground. +53 52 fix Read the post

The largest release so far: seventy changes across twelve areas, four of them new ground.

Themes

  • New
    a theme browser

    . One card per family with a light/dark switch on it, which turns 214 items into 107 and makes visible the pairing Follow system dark mode already relies on — a family is exactly what getPairedThemeVariant swaps between. Search, segments for all / favourites / light / dark, and a star per family kept in FavoriteThemes as an ordered list rather than 214 booleans, bounded because it arrives from a browser. It deliberately does not reimplement the preview: config already previews on the real dashboard and restores on leaving, and that logic is handed in as callbacks.

  • New
    AccentPrimary split from AccentSuccess

    The accent was the success colour because there had only ever been one, so this link answers and this is a Mulberry Silk install were the same value. All 214 variants carry their own now. The field is optional and empty means the old behaviour, so a custom theme written before this keeps accenting in its success colour rather than losing its accent.

  • New
    a depth layer derived from what a theme already declares

    . Rather than ask 148 themes plus every custom one for more colours — and a theme field cannot hold a gradient anyway, since sanitizeCSSColor turns a linear-gradient() into transparent — the tint, the surface ladder and the sheen are computed from the two surfaces and the accent. Two scalars, --theme-tint and --theme-depth, are set from ThemeDepth: flat, soft or rich. flat is the dashboard as it was, which is what makes this a setting rather than a fork.

  • New
    two accent washes behind the page

    , on body rather than a pseudo-element, since ::before is the dot grid and ::after the custom background. Large, soft and low — 7% and 5% scaled by depth — so it is not a visible gradient but the page not being one flat rectangle. The second uses the warning hue: a single hue reads as a mistake, two related hues read as light. A custom background switches it off entirely.

  • New
    BackgroundPattern

    : dots, grid, lines, hatch or none, with auto meaning the theme decides, and none as its off. It replaced ShowBackgroundDots outright rather than sitting beside it — two settings that both switch the backdrop off was one too many, and every theme already names its own dot colour.

  • New
    four drawings added to the SettingArt vocabulary

    the grid, density and margin controls already draw from: depth, pattern, widgetSpan and themeGrid. They open the four Help topics this release adds, sit beside the widget width, and carry the two claims the Sources and Webhooks tabs make — service → preview → your page, and an event crossing the boundary out. Depth and backdrop were briefly drawn choices in place of their selects and went back to selects: the drawings were not an improvement on a list where the reader already knows the five names. The elevation in the depth drawing is structural — plates offset behind the card — because a first pass built it from a tint, a soft shadow and a wash, all three real and all three invisible at 3.4rem on a dark theme.

  • New
    thirty-three new families

    , each light and dark: Rosé Pine, City Lights, Tomorrow Dusk, Cobalt Ink, Iceberg Drift, Owl Hours, Polar Night, Zen Ember, Great Wave, Bamboo Panda, Synth Sunset, Andromeda Drift, Cosmic Editor, Deep Lagoon, Editor Default, Forest Everglade, Fox Night, Hermetic Teal, Horizon Glow, Jungle Neon, Mirage Sand, Moonlit Steel, Oceanic Steel, Pale Night, Pastel Mountain, Retro Groove, Slate One, Solar Flats, Vampire Castle, Velocity Ink, Violet Shades, Vivid Hyper, Commit Grey. 74 families to 107; 214 variants.

  • New
    an invitation to open the theme browser

    , once, on the dashboard. Two hundred themes behind Config → Appearance → Browse is three clicks from anywhere anyone looks, and the browser previews on the real page — so the card opens it rather than describing it, through config's own openThemeBrowser reached across the lazy loader's proxy. Built on NoticeCard.define, so the corner etiquette, the transition and the retry loop are the shared ones. A first draft gated it on "still on the packaged default", which hid it from exactly the readers who care about themes: :theme, the Appearance dropdown and the setup card all change the theme without ever showing the grid. repaintAppearanceBody returns early when config is not the active view, since the browser's onPick lands there and its fallback would have drawn the whole config view over the dashboard.

  • New
    ThemeLoader.DEFAULT_THEME is exported

    , so a caller can ask whether a stored theme is still the packaged one without spelling the id a third time.

  • Fix
    favicon harmonisation is on unless a theme says otherwise

    It is stored per displayed theme id and a fresh install can only seed the two ids it starts on, so an absent entry reading as off meant the feature worked for Retro CRT and was silently off for the other 214. Choosing a theme in setup — the first thing a new install invites you to do — turned it off with no switch moved and nothing on screen saying so. normalizeEntry reads an absent entry as on; only an explicit enabled: false, which is what the toggle writes, turns it off. Visible on upgrade: an install on a theme with no entry gets harmonised favicons without asking.

  • Fix
    one default theme, not two

    theme-loader.js carried a bare dark while the server seeded Retro CRT, so an install with no stored choice showed whichever got there first — invisible except where the default is the only thing there is. theme_default_agreement_test.go asserts the two against each other rather than against a rendered page.

  • Fix
    choosing a theme in the browser leaves that theme on screen

    A preview fired during the modal's teardown and arrived while the choice was still in flight, and the old theme's class stayed on body beside the new one. Choose Moss & Stone from Retro CRT and get Marigold Dusk.

  • Fix
    the dark and light themes are called ThinkDashboard

    , not Old Default. The Dutch, German and French names were Klassiek, Klassisch and Classique; it is a product name, so only the bracketed half is translated, like every other packaged theme. The theme ids are unchanged, so nothing stored moves.

Widgets

  • New
    a new install arrives with a Health widget already on the page

    Widgets were a feature you had to hear about before you could see one: the default install had none, so the first dashboard looked exactly like the previous version and the section in the rail read as a settings screen for something absent. The seeded tile leads the block order on page one, above the categories, and reports on the bookmarks that ship with it. Which turned up a second problem worth its own entry, below — the tile it draws had four zeros on it.

  • Fix
    healthy means nothing is known to be wrong with the link

    The health tile counts broken, down now, content and healthy, and the fourth was counted from status, which is the first condition in a priority order that housekeeping also feeds — never opened, no preview yet, a check gone stale, a duplicate, a shortcut clash. A fresh install is nothing but never-opened, preview-less bookmarks, so the tile read 0 broken · 0 down now · 0 content · 0 healthy about eight links that were all fine. Healthy is now the absence of what the other three tiles count. status is untouched, so the Health view still groups a never-opened bookmark under Unused, and the healthy flag moves with the counter so a figure on the tile is still reachable by the filter of the same name.

  • New
    a page block can hold something other than bookmarks

    A widget is drawn among the categories, dragged into place like one, and stored in the same order they are: blockOrder is one array of ids for both. widgets.go holds the register, GET/PUT /api/pages/{id}/blocks the routes, and each type gets a renderer under static/js/widgets/.

  • New
    thirteen types, each reading data nextDash already keeps

    Health and Uptime from the health report and the sample history, Trend from health-trend.json, Inbox from the inbox store, Neglected from lastOpened, and Sources, Feeds and Certificates from the three registers whose failures were previously visible only by going looking for them.

  • New
    a custom widget

    . It fetches an address that answers with JSON and draws the fields named in its settings, through the server rather than the browser: the address and any stored credential never reach the page. The alternative was a codepath per service — Homepage ships about a hundred and sixty of those and felt Pi-hole v6 rewrite its API underneath them.

  • New
    settings per type

    The register carries a schema, and Widget.Config is a map[string]any the editor fills: which page to count, how many rows, the title, the width. Before this the health widget had read config.show since the day it shipped and nothing in the app could write it.

  • New
    a widget can be two columns wide

    , at most. It reuses the span rule the grid already has for a wide category rather than growing a second way to be wide, and narrows itself again on a single-column dashboard.

  • New
    a tile says how many rows it left out

    Six of them cut their list to a chosen row count and every one cut it silently — five of twelve looked exactly like five of five.

  • New
    Widgets is a section of its own

    in the config rail, under Data & backups. It had sat as a tab under Pages & tags when it was a list of names; it is a settings panel per type now.

  • Fix
    a figure on a tile opens the rows behind it

    The tiles called dash.health.openWithFilter(), which exists nowhere; the optional call swallowed it, so clicking a count did nothing at all. It is openHealthFiltered() with ?hv_filter=.

  • Fix
    delete deletes the widget you pressed it on

    The button carries its index on data-widget-delete and the handler read data-index, so Number(null) made every delete ask for block 0 — normally a category, where the isWidget check refused without a word. Broken since widgets shipped.

  • Fix
    one order, not two

    The category array's own order placed categories and blockOrder placed widgets, and a single drag wrote both: a widget dropped into second place came back fourth. The arrows on the Categories tab were reordering an array nothing reads for placement.

  • Fix
    the per-page count read a field that was not there

    summary.rows sits beside summary, not in it, so the health widget always fell through to the collection's figures under a setting that said this page.

  • Fix
    a tile redraws from fresh data when its settings change

    The fetching tiles cache their answer on the dashboard object, which is right while nothing changes and wrong the moment a widget is edited. The cache clear had also landed below refreshDashboardBlocks' early return, so editing another page's widgets left its stale answers in place.

  • Fix
    refreshAllCategorySpans stopped stomping widget widths

    It sweeps .category[data-category-id], and a widget block carries both.

  • New
    a catalogue of 28 services for the Custom widget

    A preset fills in the address, the figures worth reading and the header its API wants, in four groups, and everything stays editable afterwards. The alternative was a codepath per service; this is the same escape hatch with the tedious half filled in.

  • New
    the Widgets section has sub-tabs

    , the strip every other section carries: the widgets you have, and the kinds there are. The Types tab explains the Custom widget at length — what it reads, the paths, the six shapes a figure can take, the list variant, where the sign-in is kept, the schedule and the presets — with what it will not do stated as plainly. Every number on that page is one the server enforces.

  • New
    the catalogue is a door, not the page

    It sat open on the Widgets tab at 900px on a 900px viewport, which put the list of widgets you actually have 412px below the fold: choosing a kind added something you could not see, and said so with a toast in the opposite corner. It opens as an overlay now, the way the theme browser answers the same question, and the new row is scrolled into view, marked for a moment and holding the caret in its title. The Types tab adds too, from where each kind is described, and switches to the list to show it.

  • New
    the tiles read as instruments

    A figure and a label stacked in a paragraph is a paragraph; the tiles are laid out to be read at a glance from across a room.

  • Fix
    a saved widget can be renamed

    , and the service picker remembers which preset a widget came from rather than resetting to the top of the list on every open.

  • Fix
    a preset's path survives the host being replaced

    Typing your own address over a preset's threw away the path it had filled in, so the widget asked the right host the wrong question.

  • Fix
    a percentage on a custom tile reads as a percentage

    The format printed the float's shortest exact representation, which for a service reporting a ratio meant 43.729183739999996% on a tile the size of a stamp — the 0..1 branch multiplies by a hundred, and that arithmetic turns a clean input into a value no shortest-representation format tidies up again. One decimal, with a trailing .0 dropped. count had the smaller version of it: int64(number) truncated, so a service answering 9.99 showed 9.

  • Fix
    the Custom widget has a name

    dashboard.widgetType.custom was missing from all four locales, so its card fell back to the raw type and read a lowercase custom among thirteen proper names.

Where bookmarks come from

  • New
    sources.json, one register for every service that sends bookmarks

    Modelled on feeds.json, with two differences: it is written 0600 because it holds tokens, and it is not in the backup allowlist. Each entry records its cursor, its last result and where its bookmarks land, so a later source is only a parser. GET /api/sources, PUT/DELETE /api/sources/{id}, POST /api/sources/{id}/run.

  • New
    GitHub stars

    Pages through GET /user/starred, resumes from its cursor, and previews what it would write before writing it. The star date needs Accept: application/vnd.github.star+json, which changes the response shape, so the parser reads both.

  • New
    Raindrop.io

    , and a Sources tab of its own between Backups and Icons. Named Sources rather than Import because Backups & data already has import buttons: those read a file once, these are places bookmarks keep coming from.

  • New
    Hacker News, YouTube and Mastodon

    , none of which needs a token: hnrss.org, youtube.com/feeds/videos.xml and a Mastodon account's own RSS are public XML at a predictable address.

  • Fix
    an import the screen never showed

    After writing stars the config called this.dash.loadBookmarks?.(), a method that exists nowhere in the codebase, and the optional call swallowed it. It is refreshBookmarksAfterWrite(), the path every other write in config takes.

Import and export

  • New
    the Netscape bookmark file, read and written in Go

    . One format, thirty years old, that Chrome, Firefox, Safari and Edge all export, and that Pocket, Pinboard, Raindrop, linkding, Shiori, Linkwarden and Karakeep all speak. POST /api/bookmarks/import-html takes the file itself and GET /api/bookmarks/export-html hands the collection back in it; folders become categories, and ADD_DATE, TAGS and the description survive the trip.

  • New
    parseBrowserBookmarks() is gone from the config module

    The browser posts the file whole, which is what lets the tags, notes and dates in an export arrive at all — reading them in the browser was pointless while the browser was still deciding what to send.

  • New
    Export bookmarks (HTML)

    beside the CSV pair, through writeFetch rather than a plain <a href> so it carries the write token.

  • Fix
    the CSV route dropped the tags and notes it promised

    The manual named that as the reason to prefer it over the browser file. parseBookmarksCSV had built rows with tags, note and shortcut since v1.0.2, but the request struct on /api/bookmarks/import-browser declared three fields and the rest fell on the floor.

  • Fix
    the browser-import confirmation asked nothing

    Are you sure? Import — browserImportConfirm held the bare word in all four languages, and has since the initial commit, on the one dialog between a reader and two thousand rows. Its sibling csvImportConfirm had always carried {n}.

  • Fix
    a folder whose name has no letters in it keeps its name

    slugify keeps a-z0-9, so 📚 or 读书 produced an empty id and the folder was skipped: no category, every bookmark inside uncategorised, and — because the edit form matches a bookmark's category against the page's list — uneditable afterwards.

Keeping a copy of a page

  • New
    Save Page Now

    . POST /save with an archive.org S3 key pair captures a page the day the bookmark is saved, rather than hoping somebody else captured it before it died. The job id is kept, so archive_status.go can answer what became of a capture.

  • New
    the CDX index

    , which answers with a row per capture and its status code. The availability API answers about any capture including the ones that archived a 404, which for a dead link is usually exactly what comes back. Reading CDX gives the health view the last capture that was a real page, and the date the web lost it.

  • New
    archive.today

    , through its Memento TimeMap. The two archives disagree by design: the Web Archive honours a robots.txt that turns it away and drops what a site later withdraws, archive.today keeps what it captured. For a link that died behind a paywall, no copy from the first is routinely not no copy. Its mirrors are not interchangeable and its capture URLs sit on a fourth domain over plain HTTP, both of which the client now expects.

  • New
    local copies through monolith

    : a whole page — text, styling and images — as one file in the data directory, so it stays readable when the site and the Web Archive are both gone.

  • New
    three surfaces for all of it

    Config → Data & backups → Sources gets a Web Archive panel with the switch, the key pair and a one-page test capture; a Local copies panel beside it; and Config → Bookmarks → Local copies lists what is on disk, grouped by the bookmark it belongs to. Copies whose bookmark is gone get a group of their own rather than disappearing.

  • Fix
    the capture the health view could not find

    Reading CDX moved url, timestamp and available under a snapshot object while the health view still read them off the top level, so recover from archive stopped working without failing: HTTP 200, fields somewhere else.

  • Fix
    the capture receipt was thrown away

    archiveNewBookmark discarded the job id, so a queued capture was indistinguishable from one the archive quietly refused.

  • Fix
    what archive.org actually says

    Measured against the real service rather than a stub: no keys answers 401 with a JSON message, and keys it does not accept answer 403. Both now reach the reader, with a retry.

  • Fix
    a spent daily allowance arrives as HTTP 200

    A sixth capture of the same page in a day comes back looking like success. It reads as the refusal it is now.

Statistics

  • New
    Uptime

    , as a reading rather than a count of monitors. The server pools it by check across every monitor — 24 hours, 7 days, 30 days, mean response, outages, how many are failing now — and none of it was shown. A window with no samples says so, which is not the same as one that was down.

  • New
    Certificates near expiry

    , by host, on the reader's own certWarnDays so the panel and the notification agree about soon. Only the ones that matter: expiringCertificatesWith drops anything still ok before the report leaves the server, so a total of certificates seen is not a figure this data can give.

  • New
    Archive coverage

    , counted off the report's own rows. A dead link with a copy kept here is readable; one without it is gone, and that difference was only ever on a widget you had to have added.

  • New
    Beyond bookmarks

    on the Content tab: widgets by kind, feeds, import sources, the trash and the automatic backups. Five small requests, each failing soft — a figure that cannot be read is left out rather than shown as zero, since none and could not ask are different answers.

  • Fix
    the healthy share counts every state

    The denominator was healthy + broken + unchecked, which leaves out monitorDown and content — the two the server splits out precisely so the totals add up. Measured: 67 healthy, nothing broken and two monitors down reported Healthy 100% directly above a row reading Monitors down 2. It is 97% of 69. Drift stays out on purpose, since it layers on whatever status a bookmark already has.

  • Fix
    a bookmark answering while failing its own expectation is visible here

    loadStatsHealth never read contentCount off the summary, so a whole class of failure was missing from this section while the Health view, the health widget and the review notice all showed it. Drift and orphaned categories get a row too.

  • Fix
    the cleanup score names the reader's own threshold

    stale90 is counted with bookmarkStaleDays, a setting between 7 and 365, and the label was the constant 90. On an install set to 7 the panel read 120 bookmarks have not been opened in 7 days and, four lines below, 120 not opened in 90 days.

  • Fix
    category panels label by name

    The labeller reads _bmCategoriesCache, which only the Bookmarks section warmed — so going straight to Statistics gave dev and docs where the same visit after opening Bookmarks gave work · Development and Docs. The page prefix that tells two same-named categories apart never appeared either, and the CSV export carried the ids.

  • Fix
    the timestamp is on the reader's clock

    It asked Intl for whatever the locale prefers and ignored the Time format setting, so a 24-hour install read It's 15:10 in the header and Worked out at 03:10 PM under the figures. shared/clock-format.js is now the one clock in the app; the four places that each asked their own way go through it, the header line included.

  • Fix
    the panels fed by the health report survive their own fetch

    loadStatsHealth patched one element, which was enough while the report fed one panel; it feeds four now, and the three that render to nothing while the fetch is in flight were left absent for good.

  • Fix
    the rule under the Statistics sub-tabs runs the full width

    It belonged to the tab strip, which is a flex item sized to its own content on this screen, so it stopped under the last tab — measured at 443px against a panel 812px wide.

Health

  • New
    check a service that wants you signed in

    . A self-hosted service bookmarked at its web interface answers 401 to an anonymous check, so the row read broken while the service was fine, and the only way to stop that was to stop monitoring the bookmark most worth monitoring. Credentials are named and reusable, kept in their own 0600 file outside the backup allowlist, never handed back to a browser; the bookmark stores only an id.

  • New
    buttons on a downtime alert

    ntfy is the one configured service that can carry them, and only in its JSON form, so the topic is split back out of the configured address and the message is posted to the server root. Every button is a view action: an http one would carry a credential through a notification travelling over someone else's server. Priority follows the event — a failure above default so it breaks a quiet-hours rule, a recovery below it. An address for this install can be given under Downtime alerts; without it the button that would need it is left off.

  • New
    three fetching actions on a whole selection

    Rebuild previews, Refresh favicons and Save a copy on this disk were each on a row's own menu; a filter that finds forty bookmarks with no preview is exactly the case for doing them at once. Sequential, with a counting overlay, for the reason bulkRecheck already is: twenty parallel requests from one client is a burst a small server reads as an attack. Favicons are grouped by page before writing, since there is no per-bookmark write — row by row, three rows on one page would be three loads and three saves of the same list and the last save would carry only the last icon. A 412 from monolith stops the sweep rather than proving the same thing forty times.

  • Fix
    a bot check is not a dead link

    Pew's linkrot study counts a page as gone only on the codes that say the page or the host no longer exists and treats the rest as unknown. That is the difference between a monitor people trust and one they switch off.

  • Fix
    the health report cache notices a write

    It held an answer built before a bookmark was added, so a fresh bookmark was missing from the report until something else invalidated it. Every mutation passes through one place, which is where the generation counter now lives — invalidating from the call sites was the other option, and adding a bookmark was already the path that forgot.

Cards and previews

  • New
    what a page says about itself

    The fetcher read a title, a description and an image; pages state a good deal more in their <head>. Publisher, author and publication date now reach the card, and the video providers' oEmbed discovery link gives a player that can be started from it. Third-party players are bounded with a named frame-src rather than a sandboxed srcdoc: the sandbox gives a null origin, which is why the first attempt drew a black rectangle.

Finding things

  • New
    the browser's address bar as a nextDash search box

    #search?q= runs the query the search overlay would run, and /opensearch.xml describes it to the browser. The query is captured at script load rather than read when the router runs: restoring the bookmarks view rewrites the hash to the page index during bootstrap, so a search arrived at from the address bar was gone by the time anything looked. The template is absolute and honours X-Forwarded-Proto and X-Forwarded-Host; a browser refuses a relative one, and an install behind a proxy would otherwise describe an address only the container can reach.

Telling other programs

  • New
    outgoing webhooks

    . A bookmark added, changed or removed, and a monitored bookmark going down or coming back, are pushed once to whoever subscribed. Signed with the Standard Webhooks scheme rather than one of our own — the receivers this is aimed at already verify it — over {id}.{timestamp}.{payload}, so a redelivery can be recognised and a replay refused. Keys live in webhooks.json at 0600 beside the health credentials, and travel back to the screen exactly once, in the answer to the save that generated them. A failure is retried twice with a growing gap; a 4xx is not retried at all.

  • New
    an MCP endpoint

    , off unless switched on. One POST /mcp carrying JSON-RPC 2.0, four tools — search the collection, look one bookmark up, list the tags in use, add a bookmark. Adding delegates to the handler the browser posts to, so the duplicate check, the URL validation, the activity entry and the outgoing webhook cannot be forgotten in a second write path. Origin is checked, because a browser will POST to localhost from any site on the internet. Written against the standard library: what is needed is a JSON envelope, four tool descriptions and a switch.

Backups

  • New
    a backup carries the whole data directory

    Files had been left out one at a time, each for a reason that held alone — a trend re-records daily, a feed re-polls, a cache regenerates — until together they made a restore an install that had lost its history and had to earn it back over weeks. health-trend.json needs three days before its chart appears and thirty before the window it claims is real.

  • New
    two switches under *What a backup carries

    : local copies, by far the largest thing in a backup, and the files that hold tokens. They read as include* and are stored as exclude, so a settings file written before they existed keeps making the fuller backup rather than quietly thinning it. importFileMode restores sources.json, health-credentials.json and webhooks.json at 0600, since a ZIP carries no permissions.

Config and the dashboard

  • New
    What's new opens on the release

    Measured at 1440×950: 283px of a 918px modal and 32% of the visible scroll area went to three bordered panels before the first word. The version is a headline, modalLead its subtitle, sections are an eyebrow with a count, and an item is a title with an explanation that folds at three lines. The new/fix chips are a filled and a hollow dot — they cost seven characters of a narrow column, and drew their tint from --accent-success, which equals --accent-primary on a green accent. Older releases are one row each, opened on request, which replaced a lazy loader that appended whole releases as you scrolled and a "scroll for 49 more releases" hint sitting between two that were already on screen. The 50-release cap went with it.

  • New
    the panels on Sources and Backups & data fold

    Native <details>, so the keyboard behaviour comes for free; sources all shut, backups with the Backup panel open since that is why the tab gets opened. Fold state is remembered, because <details> state is DOM state and a repaint would otherwise shut what somebody is working in.

  • New
    progress on the actions that take time

    Refreshing link previews is one page fetch per bookmark — 1.3 seconds against eight seeded bookmarks, so well over a minute for a real collection — and it ran as one request with no feedback and a proxy free to time it out halfway.

  • Fix
    the Widgets tab is laid out

    It was built on the shared .config-crud-row, a flex line with no wrap, and the settings panel carried grid-column, which does nothing there: the type name landed on the shown toggle and the panel opened beside the row instead of under it. Also this.escape does not exist on DashboardConfig — it is this.dash.escapeHtml — so the settings panel threw and the whole tab render died silently.

  • Fix
    one list arranges the page

    The second category list in config still reordered the category array, which nothing has read for placement since blockOrder became the single order.

  • New
    a fifth setup step, for bringing your own bookmarks in

    The card ended on how would you like to begin?, where one answer is start from scratch — and whoever picks it is then looking at an empty dashboard with nothing in the app saying they need not type it all in. Two ways in, because they answer different questions: a file you already have, and a list that keeps arriving. Both open the screen rather than importing from the card, and following either finishes the setup first, since everything answered in the four steps before it is still only a draft.

  • Fix
    the seventy-odd translations whose key has a dot in it

    t() split a key on dots and walked nested objects, so it never reached a key stored as one literal name with a dot in it — about three hundred translations across the four languages were written, kept in step and never once displayed. What a reader saw instead was the English hardcoded beside the call, which is why it looked as though nobody had translated any of it. Checked across all four files first: no key is reachable both ways, so nothing that resolved before resolves differently now.

  • Fix
    the lists and the overview are made of blocks too

    The shared list row — pages, categories, tags and finders — had a background only under the modern layout, so on Classic every one of those tabs was a column of empty rectangles. Config → Overview was worse: its panels carried a modifier that stripped them to nothing, leaving About the developer, At a glance and the news stream as bare text between hairlines while every other section is made of cards.

  • Fix
    one line under a spread category header, not two
  • New
    Help has a Widgets tab

    , five articles with a drawing each: what a widget is, the thirteen kinds grouped under the question each answers, adding one and where it sits, the Custom widget at length, and the twenty-eight services it already knows. It was one paragraph under Pages & bookmarks, which is where the Custom widget went unnoticed. The section list in the Configuring article gained Widgets, per language against its own anchor.

  • Fix
    :config <section> names the config that exists, and arrives at it

    The list was the config of two rewrites ago — General settings, Theme & colors, Pages, Categories, Tags, Finders, Collections — of which one is still a section, and it never offered Overview, Appearance, Behavior, Widgets or About. Every row also landed in the same place: the action was location.href = '/config#<id>', and /config is the pre-v1.3 page that answers 302 to /#config — a redirect whose target carries its own fragment replaces the one that was asked for, so the section was dropped and all eleven rows opened Overview, after a full page load of a view that lives in the same page. Ten call sites now go through one helper that sets the sub-tab and opens in place. The names that became sub-tabs are kept and carry their tab, so typing what you remember still arrives somewhere sensible.

Appearance

  • New
    a new install starts with the button bar in the bottom-right corner

    It began centred above the bookmarks, floating over the thing people open the dashboard to look at. Only for a settings file that never named a position; anyone who chose one keeps it.

Under the hood

  • Fix
    titles are trimmed by character, not by byte

    trimToLength and truncateForState sliced at a byte offset, so a cut landing inside a multi-byte character stored half of one and it reached the page as U+FFFD: trimToLength("ééééé", 3) gave éé and a replacement character. Every caller is trimming text some other site supplied — a page title, an oEmbed author, an error message a foreign server wrote — so the multi-byte case is the ordinary one. truncateRunes already existed for exactly this.

  • Fix
    an atomic write is flushed to the directory too

    The rename is atomic against a concurrent reader, but until the directory entry itself reaches the disk a power cut can leave the file at its old contents, or under neither name. Best effort, and its failure is not returned: the write did land either way.

  • Fix
    off the deprecated crypto/elliptic calls

    Marshal, Unmarshal and ScalarBaseMult have been deprecated since Go 1.21 and each call carried a //nolint. crypto/ecdh was already imported for the Web Push key agreement; only the VAPID side had not moved. NewPrivateKey brings the 0 < d < N range check that was written out by hand beside it. No stored key changes — the wire formats are the same bytes, which is what the existing round-trip and signature tests check.

  • Fix
    one HTML escaper instead of fourteen

    Fourteen files had written their own and they had drifted: eleven escaped five characters, three escaped four and left the apostrophe alone. Which one a file got was down to when it was written, and shortcut-format.js published the weaker one on window. shared/escape-html.js is the answer now; bookmark-form-preview.js keeps a copy on purpose, since it is synced verbatim into the Chrome extension, and it escapes the apostrophe like everything else.

  • Fix
    the last three parseInt calls without a radix — the page index from the location hash, and the column count on both branches of :columns
  • Fix
    the Go test suite writes to its own data directory

    ResolveDataDir falls back to data when NEXTDASH_DATA_DIR is unset and TestMain never set it, so go test./... in a checkout ran against the working directory's store — a developer's live install. It does not merely read it: constructing a store seeds a fresh one, so a run overwrote bookmarks-N.json, settings.json, pages.json, colors.json, the inbox, the finders and the icon cache. Which exposed nine test files spelling data/… instead of asking for it, and seven tests leaning on what earlier tests had left behind.

  • New
    make reset-data, make doctor and make rescue-data

    ./data is a bind mount, and deleting it while the container runs is a trap with no sign of having been sprung: the host loses the name, the mount keeps the directory alive, and the container writes into something that no longer exists until the next restart. doctor names that state because nothing else will, and rescue-data gets the data back out with tar rather than docker cp, which resolves the mount to the host path that has gone.

Security

  • Fix
    the API answers this dashboard, not every page on the internet

    Access-Control-Allow-Origin: * was the default, and the read routes need no token: any site open in a tab could ask a nextDash on a guessable LAN address for the whole collection. The default is now same-origin, with an exception for extension origins — a Manifest V3 extension with host permissions is granted cross-origin access by the browser with CORS never entering into it, so refusing the header would not stop one and allowing it does not enable one that lacks the permission. NEXTDASH_CORS_ORIGINS=* restores the old behaviour in one value, and a value that names nothing usable now means nothing rather than falling through to the wildcard.

  • Fix
    the webhook list answered a GET before checking the write token

    An endpoint URL is not a description of a webhook, it is the webhook: a receiver acts on whatever posts to it.

  • Fix
    webhook delivery goes through the guarded client

    , with zero redirects. The URL is checked against the SSRF rules when it is saved, but a name is resolved again at delivery, so a receiver that answers 302 reached an address the save had refused.

  • Fix
    a stored health credential does not follow a redirect off its host

    net/http copies headers onto the redirect it follows, so a monitored host answering 302 received the install's API key at whatever address it named. The headers are stripped at the host boundary rather than the redirect refused, so a service that legitimately redirects to a login host is still checked, anonymously. Custom widgets follow the same rule.

  • Fix
    a custom widget's url and credentialId are withheld

    from the page-blocks route unless the request carries the token. The route is open because the dashboard has to draw the tiles, and the tile fetches by widget id precisely so the browser never holds the address.

  • Fix
    refresh=1 on the custom-widget route is behind the token

    It skips the cache including the short TTL a failure gets, so an open dashboard could become a retry loop against somebody else's service with a stored credential on every request.

  • Fix
    saving blocks to a page id that does not exist

    minted a block list nothing could draw and reported a missing page as a server fault. A page's widgets are also capped at twenty-four on read: the body limit bounds the bytes, not the number of blocks the grid then draws on every render.

  • Fix
    /opensearch.xml varies by proxy header and points at an icon that exists

    It named /data/icons/favicon.png, a path nextDash never writes, so browsers drew the search entry without one; it asks manifestIcons now. Without Vary, a shared cache would hand one browser a template built from another's claimed host.

Only docs and tests changed in this release.

v1.3.3.5 A modal that had thirteen CSS rules written for it, on a page that never loaded any of them. 1 fix

A modal that had thirteen CSS rules written for it, on a page that never loaded any of them.

Saving a link

  • Fix
    the paste-choice modal is styled on the dashboard, where it appears

    Pasting a URL opens Save this link, and it drew as raw markup: .paste-choice-url printing over .paste-choice-lead, and the two .paste-choice-card buttons collapsed onto a single line with their <kbd> shortcuts stranded below. The rules existed — thirteen of them — but lived in static/css/dashboard-inbox.css, which sits inside the bundle:css-views markers in templates/dashboard.html and is therefore fetched only when Inbox, Health or Config is opened. This modal opens on the dashboard itself, on paste, so on a fresh load not one of them had arrived; measured against the running app, zero paste-choice rules were reachable from document.styleSheets. Moved to static/css/dashboard.css, which rides in the main bundle. The inbox sheet keeps its own half of the shared 520px media query, which the two files had been sharing. The spec counts the reachable rules and then measures the geometry the modal actually produces — the URL's bottom edge against the question's top, and the two cards sharing a y but not an x — because a stylesheet reaching the page is not something the markup can assert about itself.

Only docs and tests changed in this release.

v1.3.3.4 Three buttons that had never been styled, and were only ever on screen while nobody was looking for them. 1 fix

Three buttons that had never been styled, and were only ever on screen while nobody was looking for them.

Health

  • Fix
    the filter-specific buttons carry the toolbar's own shape

    Fetch previews, Open broken links and Merge duplicate group had no CSS rule at all, so each rendered as the browser's default: square, 2px outset, grey, in a row of buttons with a 1px border and a 0.4rem radius. They appear only while their own filter is on screen, which is why it survived — and why a visibility check would never have caught it, since the button is there. All three join the secondary set beside Export rows and Rot report, in classic and in modern, with the hover, the focus ring and the disabled state that set already had; Fetch previews and Open broken links both disable themselves while they run, so the dimming is load-bearing. The spec reads the computed padding, border, radius and font size off Rot report and asserts the fetch button matches, rather than asserting it is visible.

Only docs and tests changed in this release.

v1.3.3.3 Two tiles in the health view that looked like the ones beside them and could not do what those do. +2 2 fix

Two tiles in the health view that looked like the ones beside them and could not do what those do.

Health

  • Fix
    the Certificates tile is a filter

    It was drawn with no key on purpose: certificates are counted per host rather than per bookmark, so the comment above it reasoned there was nothing to filter on and that clicking would appear to do nothing. It sits in a row of six tiles that are all filters and looks exactly like them, so "deliberate" reads as broken — and the rows were reachable all along, since certFor() already maps a row to its host's certificate to draw the badge. The count still reads in hosts; the list it opens is the bookmarks on them, which is what someone clicking a warning is after.

  • New
    Missing preview carries the one action that can empty it

    Re-check and Retest all run the availability check — update-status and cache-scan, not one preview call — and the flag is read from what is stored on the bookmark rather than from the preview cache. So eighty-seven rows sat under two buttons that could not move the number above them however often they were pressed, and nothing on screen said so. Fetch previews calls /api/previews/refresh, the same route Config → Data & backups → Icons & previews offers, behind a confirm that says it is one request per bookmark; afterwards the bookmarks and the report are both re-read, since the flag comes from the stored field. Fetching itself was never broken — a server against 9to5google.com and ad.nl, two of the rows reported as stuck, returns a title and description for both.

Config → Overview

  • New
    both are in the news stream and under About → News & features, with a way straight to the Missing preview filter
  • Fix
    a release published today could not be marked read

    A release carries a date rather than a moment, and the stream stamps it at noon UTC so the day sorts sensibly wherever the reader is — which puts a release published this morning, or read from a timezone ahead of UTC, in the future by its own clock. Reading the stream marked it seen at now, so the dot and the count on Overview stayed until noon UTC whatever the reader did. It marks past the newest row instead.

Docs

  • New
    Config → Help describes both

    The health article now says that every tile narrows the list, Certificates included, and that Re-check asks only whether a link answers — which is why Missing preview has a fetch of its own. In four languages, and the version note it carries was two hotfixes behind.

Only docs and tests changed in this release.

v1.3.3.2 A font size that could not be chosen with a mouse, a template drawing itself without an icon, and a test suite that stopped needing six machines. +1 4 fix

A font size that could not be chosen with a mouse, a template drawing itself without an icon, and a test suite that stopped needing six machines.

Appearance

  • Fix
    choosing a font size works with a mouse

    Hovering a size previews it on the dashboard behind the panel, which is what it is for — but applyFontSize() puts the class on <body> and the config panel reads the same six --font-size-* variables, so the panel resized too, including the button under the pointer. That is a loop rather than a cosmetic fault: the button grows, slides out from under the cursor, fires pointerleave, which reverts, which slides it back under the cursor, which fires pointerenter. Logged at the document with capture on: ten enter/leave pairs in a row and no click at all. holdConfigTypeScale() copies those six values onto .config-view before the class is swapped, so the panel stays put while <body> changes under it; the click and the revert both release it, so taking a size still resizes everything. The keyboard and touch never entered the loop, which is why it went unnoticed.

Config → Overview

  • Fix
    the project's own posts keep their place in the six rows

    The stream is in date order, which is right for the list and wrong for a six-row window: two hotfixes shipped in one afternoon carry two release rows and the settings they introduced, all stamped that day, and between them they fill it — so the posts, the one source that is not about a version number, fell off the page the day after they went up. Up to two of the newest keep a slot; the window is still six rows and still in date order, and a source filter reserves nothing, since the reader has already said which kind they want.

  • Fix
    a release that brings no features no longer spends the window

    Features from the two most recent releases join the stream; counted in releases, two hotfixes emptied it of everything a reader could act on. It counts the two most recent releases that actually introduced a setting instead.

  • New
    the font-size choice is in the stream

    , with a way through to Appearance.

Unraid

  • Fix
    the Community Applications template draws its icon

    It pointed at favicon.png in the repository root, which is not there, so the entry appeared blank. It is static/nextdash-logo.png now. Project links to nextdash.cc rather than to the source — Support and ReadMe still point at GitHub, where an issue and the readme actually live — and the fifth screenshot joins the four that were listed.

Tests

  • New
    the suite runs a server per worker

    workers: 1 was not a property of the tests but of the harness: one go run. and one data directory meant a second worker would delete the first one's bookmarks mid-test. Each worker now gets its own port (18080 + workerIndex), its own data directory and its own server, started from a binary the global setup builds once — so nothing is shared and nothing can interfere. A full run took about an hour and a half and needed six CI machines to come in under twenty minutes.

  • Fix
    22 specs lost their fixtures import in a merge

    and silently went back to sharing whatever the previous file left behind — invisible while everything ran against one server, and an immediate ERR_CONNECTION_REFUSED once each worker had its own.

  • Fix
    three tests took a handle on a row in the bookmarks list and used it after the list had repainted itself, failing about one run in three with Element is not attached to the DOM. And config-bookmarks-editor never marked what's-new as seen, so the promo card landed mid-test and shifted the Save button a few pixels — five tests in that file were passing only on retry. One of its assertions was also asking for something the app does not promise: openCount seeded into the browser's copy of a bookmark, expected back after a save the dashboard does not send it in

Only docs and tests changed in this release.

v1.3.3.1 A hotfix. +3 6 fix

A hotfix. Four things that only worked with a mouse or did not work at all, and the overview's news arriving while it is still news.

Keyboard

  • Fix
    a command with an argument could not be typed

    searchActive was set by showSearch(), which runs from the debounced updateSearch(), so for the first characters of a query the app still believed nothing was open — and every guard that reads it let a key through that belonged to the palette. In :buttons cheatsheet the c opened add a category and the h went into the name field it had just created, leaving :buttons eatsheet. The session is marked open at the first keystroke now, with the overlay still drawn at the debounce, so nothing on screen changes.

  • Fix
    a space ran the highlighted row

    instead of separating two words. The row takes focus and a focused row is a button, so :buttons + space applied the first entry. Space is text while a query is being typed; Enter still activates, which is the deliberate way in.

  • Fix
    a category's ⋯ menu opens with the keyboard

    The button carries aria-haspopup="menu" and a handler for ArrowDown, but a bare arrow starts grid navigation from anywhere and that handler runs first, in capture — so the key moved the cursor into the bookmarks and took focus off the button on the way. The grid leaves the sort controls alone now.

Fixed

  • Fix
    a page no longer jumps to where you once were

    takeRememberedScroll is named for consuming the offset and its comment says so; it only ever read it, leaving the entry in the Map and in sessionStorage. Every later visit to that page — from a tab, a shortcut, anywhere — landed halfway down with nothing on screen to explain it. It is taken from both stores now.

  • Fix
    a release that changes only wording reaches the browser

    /locales/ is requested with the app-version fingerprint appended precisely so a deploy makes the URL new — and assetFingerprint() hashed CSS and JS only. A release that rewrote text and added a key therefore served the old file from cache until something else happened to change: the rewritten line stayed as it was, and the new key came back empty. The translations are part of the fingerprint now, read from disk-then-embed the way they are served, with a test that fails if a wording-only edit leaves the token where it was.

  • Fix
    the setting that marks rows which publish carries its ℹ

    It sat in the field map with a default and no explainer, so the panel offered to restore a default it never named. Four languages.

The overview's news

  • New
    the stream is refreshed while it is still news

    The server held its copy for six hours and the browser kept whatever it had for the whole session, so a post could go up and a dashboard that was open all day would not show it until a reload. The server's window is 90 minutes and the browser refetches after 30; the two are deliberately out of step, so a browser that asks halfway through still gets what the server has. Asking is nearly free — the fetch is conditional, so the common answer is a 304 with no body, once per server rather than once per reader.

  • New
    release notes open the moment a new version does

    The prompt was scheduled 900 ms after boot, chosen for a prompt that might not appear at all; on an upgraded install that read as the dashboard settling and then interrupting. When the release is unread the modal's own code is fetched at once and the notes open on the next tick.

  • New
    four more of what v1.3.2 and v1.3.3 added are in the stream

    , each with a way straight to the setting: the rebuilt hover card and what it knows about a link, its three modes and the calm hover delay, the site's posts on the overview, and the two-column add form.

Tests

  • Fix
    the suite was red on every shard, and most of it was the tests being behind

    Six files described a trend chart that moved into the tile row, three a feature carousel that no longer exists, three a button bar that was given its own tab, plus an overflow filter menu that went, a templates/config.html that was deleted, a CSV that gained a reason column, and an About that became a ninth section. Four specs depended on data another spec happened to leave behind, three raced the dashboard's own construction, and one seeded statistics onto a different row than it edited. All of them now pin what the product actually does — the five failures above are the ones that were pointing at something real.

Only docs and tests changed in this release.

v1.3.3 The overview, rebuilt around one question: what is happening with nextDash, and what is happening in your install. +10 44 fix

The overview, rebuilt around one question: what is happening with nextDash, and what is happening in your install. It used to answer "what is new" in three places at once — a carousel showing one of forty-nine feature spotlights, a Latest update panel repeating the release named directly above it, and the project's own posts below both, starting below the fold on a 900-pixel screen. It is one dated stream now, and the figures about your own library sit beside it rather than on top of it.

Overview, rebuilt

  • New
    one dated stream, three sources

    Posts from nextdash.cc, releases, and the settings each release introduced, in one list, newest first, every row carrying a source label and its own way in: read the post, show what's new, or open the setting. Six rows fit where one sixty-word spotlight used to, which is the whole gain — not more space, six times the number of things you can act on. Source chips narrow it to one kind and back; that they can hide the site's posts is what keeps a news block in a self-hosted tool from reading as an advert. dashboard-news-stream.js, fetched with config.

  • New
    the stream leads the page

    The act zone still comes first — nothing displaces "this wants you" — and then the stream, in the wide column directly under it. The side column beside it opens with About the developer — the project's site, its feed, GitHub and the author's own site as four addresses rather than two buttons — level with the top of the stream, since it belongs to the same zone. Under it a Your install line heads the two blocks that describe your own: At a glance, and what differs from the defaults. Figures about your own library are looked up, not met on the way in, and moving them is what lifts the stream above the fold: it now starts at 474 pixels rather than 936.

  • New
    a green dot and a count on Overview

    in the section rail, for anything published since you last read the stream. A first visit stamps the moment rather than counting everything ever published, or the badge would read 156 on day one and be ignored from then on.

  • New
    the drill-in

    : All news & features opens About → News & features, which carries the stream in full, the same chips, and the forty-two features from before the catalogue was dated. Under it, Follow it from your own dashboard saves nextdash.cc as a bookmark so Fresh counts its posts — the product following its own feed, which is also the shortest demonstration of what Fresh is for.

  • New
    the site feed carries a summary

    and ten items rather than five: the WordPress description, stripped of its markup and cut to 160 characters on a word boundary. Fetches are conditional now (ETag / If-Modified-Since) and the result is mirrored to site-news.json in the data directory, so a machine that reboots nightly does not go back out to the site every morning. DISABLE_NEWS_FEED=true switches it off server-wide, beside DISABLE_TELEMETRY and DISABLE_UPDATE_CHECK.

  • New
    features carry the release they landed in, which is what lets them take their place in a dated list

    Seven are dated from the file's own history; the forty-two imported in one go stay undated on purpose rather than being guessed at, and sort to the drill-in. npm run validate:overview-features fails on a broken entry and reports the undated ones.

  • Fix
    the source labels sit in a column of one width

    Every row is its own grid, so an auto first column sized itself per row — nextdash.cc is twice the width of release — and the titles started at a different place on almost every line. One fixed width, the label filling it, and a longer source name added later is clipped rather than shifting the list.

  • Fix
    the carousel is gone, and with it stepOverviewFeature, repaintOverviewNewFeatures and its keyboard handlers

    a control that needed forty-eight clicks to show what it had was never going to be used, and nothing measured whether anyone tried.

Analytics

  • Fix
    every number an event carries is now rounded into a band

    The privacy setting promises exactly that, and the two snapshots kept the promise while the action events did not: a bulk recheck reported count: 37, a health export rows: 1274 — a figure more precise than the question needs, and on a small install a fingerprint. The rounding sits in nextdashTrack() itself, the one function every event passes through, so a new event cannot reintroduce an exact figure by forgetting to bucket it. Bands are 0, 1, 2, 5, 10, 25, 50, 100, 100+; a page position and a walkthrough step are deliberately exempt, being small fixed ranges that describe nothing about a collection. Pinned by npm run test:analytics-buckets.

What's new

  • New
    a new version shows its release notes once, by itself

    The machinery has been in place for a long time — a release token in the stub, a "seen" stamp written when the modal closes, a prompt scheduled after onboarding — but nothing pinned it, and the manual said the opposite: release notes never open by themselves. It is a contract now, with a test: an install that last read an older release gets the notes on its next visit, closing them records the release, and no later visit reopens them. A browser meeting nextDash for the first time is exempt on purpose — quick start is running, and notes for a version that reader never used would be noise.

Fixes to the rebuild

  • Fix
    a failing feed request now says so

    /api/site-news answering 500 came back in the same shape as a cleared setting, so the stream reported Site news is switched off to someone who had switched nothing off.

  • Fix
    reading the stream marks it read

    The marker was written to storage but not to the page, so the green dots came back on every repaint and the count on Overview kept its first number until a reload. It is now set where the stream is drawn rather than where it is fetched — loading it from the Privacy switch or from About no longer clears dots for a page nobody looked at — and it moves after the render, so the dots stay visible on the pass that draws them.

  • Fix
    About → News & features is addressable

    The tab was in the sub-tab state map but not in the list of tabs that can appear in the address, so #config/about/news opened the colophon and choosing the tab never reached the hash — the one sub-tab in config that could not be linked to or remembered.

  • Fix
    the drill-in fills itself when opened directly. The stream repaints the overview when it lands

    About had no such repaint, so going straight there left "Loading…" on screen until an unrelated render happened along.

  • Fix
    a post's summary was unescaped twice, so a post about &lt;script&gt; showed <script> — the text it quoted rather than the text it wrote

    The unused encoded field went with it.

  • Fix
    the carousel left 78 lines of CSS and seven locale strings behind, and the preview card a wants() nobody called

Locales

  • Fix
    765 unreachable strings removed from all four locale files

    , out of about 5,500: everything left behind by panels, buttons and whole views that had been rewritten. Found with a new npm run validate:locale-unused, which is deliberately conservative — a key counts as reachable when its name appears anywhere in the source, when it fits a template a call site builds (t(\config.${field}Label\)), or when it belongs to a family looked up by a value, like a theme id or a layout preset. Two more checks keep it that way: validate:locale-parity fails if the four files stop carrying the same keys, and a spec walks every config section and sub-tab, plus health and inbox, failing on any text that reads as an identifier rather than a sentence.

  • Fix
    the 199 strings the feature catalogue reaches came back

    The scanner skipped every directory called data — meant for the runtime one, which says nothing about the source — and took static/data with it, where overview-features.json names four locale keys per feature and is the only place they appear. They were reported as unreachable and removed, which left About → News & features drawing all fifty features from their English fallbacks in Dutch, German and French. The skip is by path now, and the three checks that would have caught it — the catalogue, locale parity, duplicate keys — run in CI rather than only when someone remembers them.

Menus

  • Fix
    the Pin entry in the context menus is drawn, not typed

    Every other entry is a glyph tinted with the accent colour — ⧉, ✎, →, ◉ — and Pin was 📌, painted by the system font in its own red and yellow on every theme, and deaf to the red a destructive row is given. It is a small SVG in currentColor now, shared by the grid's menu and the config list's through js/shared/menu-icons.js, which is also the only place markup is ever assigned into a menu's icon slot. The pin on a config row and the paste-choice card still carry the emoji: they are labels rather than menu entries, and are left for a separate pass.

The bookmark form

  • New
    the add/edit form is two columns on a window wide enough for them

    Eleven fields stacked at full width made it 735 pixels tall to add and 763 to edit; a 1366×768 laptop leaves about 660 once the browser has taken its share, so the form scrolled and the save row sat below the fold on the machine most people use. The fields fall into two groups of nearly equal height — what the bookmark is (name, address, icon, note) and where it goes and how it is watched (page, category, tags, shortcut, pinned, availability) — and side by side the dialog comes to 435 pixels, adding or editing alike, which fits a 640-pixel window with room over. The columns are real elements, so Tab still runs down one and then the other; below 860 pixels of window they dissolve and the single column returns unchanged.

  • New
    the form explains itself without printing the explanations

    Pinned and the three availability pills say what they are, not what they do, and their descriptions lived in a hover title and behind an info button — no use at all on a touch screen. Each now opens a bubble on hover, on focus and on tap: Pinned says what pinning does, a mode pill describes that mode, and the i names the choice and describes the mode currently set. A screen reader gets the same sentence whether or not the bubble is open.

  • Fix
    a warning no longer moves the form

    Every message the form could show — a shortcut already in use, a letter the grid also claims, Name is required, Valid URL required — appeared under its field as you typed and pushed everything below it down. On an empty Add form one keystroke in the name was enough to make the address complain and shift the column by nineteen pixels. They are all the same bubble now, in the error colour, with the field keeping its red border, and they open only once a field has been used or a save has been refused — the form no longer greets you by pointing out that you have not filled it in yet. Each message is a live region, so a screen reader still hears it as it appears.

  • New
    a phone gets the short form

    Icon and Note are hidden below a fine pointer: four buttons for a favicon that is fetched from the page anyway, and a textarea under a keyboard that covers half the screen. They are hidden rather than dropped, so editing a bookmark on a phone leaves the note and the icon it already had exactly as they were. The two columns are a fine-pointer layout too — a landscape phone is nearly 950 pixels wide and is still a phone, where one column you scroll beats two you pinch at.

  • Fix
    adding a bookmark starts in the address field rather than the name

    The address is the one thing only you can supply; the name usually arrives with the page title. Editing still starts on the name, which is what is nearly always being changed.

Your data

  • Fix
    an import that carried no bookmark page emptied the library

    Committing an import deletes every bookmark page the archive does not name, so a ZIP of unrelated-but-valid files — settings, themes, icons — cleared data/ and still answered 200. An archive with no bookmarks-*.json in it is refused now, before anything is replaced.

  • Fix
    merging duplicates could delete a bookmark that was not part of the merge

    Two identical source refs were both validated against the pre-merge snapshot and then removed one after the other from a slice that had already shifted, so the second delete took an innocent neighbour — and the keeper's open count was added twice.

  • Fix
    a failed delete left the page holding every removed bookmark twice

    The error path re-inserted bookmarks that the save had already rolled back; it restores the pre-delete copy instead. The inline editor had the same gap the comment above it already promised was closed: a write that failed still recorded a trash entry, still said deleted, and offered an undo that made a real duplicate. The tag filter's rollback repairs allBookmarks too, having no snapshot of its own.

  • Fix
    a save from a tab that was open before a bookmark started failing no longer erases the down since history

    BrokenSince is carried across the save beside LastError.

Access

  • Fix
    the data directory is no longer served whole

    /data/ was a plain file server over the data directory, directory listings included: settings.json, every bookmarks-N.json, inbox.json, trash.json, health-history.json and the automatic backup ZIPs could be read without the write token, while /api/backup hands out that same content only behind it. Only data/icons/ and an uploaded favicon or font are served now. Icons are content-named and never reused, so they go out immutable on the way past — they had no cache header at all, and there is one per bookmark.

  • Fix
    the trash validates what it takes in

    A restore splices the stored bookmark straight back onto its page, so trash-then-restore was the one route that could keep a javascript: URL, a private address with allow localhost bookmarks off, or a client-chosen icon path — the hole the inbox closed for itself a release ago.

  • Fix
    listing and downloading an automatic backup need the write token

    , the way running, restoring and deleting one already did. Both client paths already carried it.

  • Fix
    /api/health/check-url applies the SSRF rate limit every sibling that fetches a caller-supplied URL applies

    On the default install there is no write token, so that limit was the only thing in front of it.

  • Fix
    an X-Forwarded-For value that is not an address can no longer become a rate-limiter key
  • Fix
    Send test alert worked on an install with a write token

    The button did not go through the token-carrying fetch, so its handler answered a flat 401 — on exactly the installs most likely to be alerting on something.

Monitoring

  • Fix
    outage alerts went silent on Pushover and browser push

    Alerts were dropped whenever no webhook URL was set, before a single transition was looked at — but Pushover is configured with an application token and a user key against a fixed endpoint and never sets that URL, and browser push is an independent sink reached before the webhook target is read at all. So an operator who picked the preset for which the config UI does not even render a URL field, or who only switched push on, got no alert for an outage of any length. Send test alert does not pass through that gate, so the setup looked correct. It is gated on the sinks that actually resolve now.

Keyboard

  • Fix
    ,, + and & can be typed again

    The three shortcuts sat above the printable-character branches without the not while searching guard the key right below them already had, so they could never reach a search field, a filter, or a :new https://x/?a=1&b=2 command — where & opened the quick-add omnibox on top of the command palette.

  • Fix
    :columns no longer strips a view of its layout

    It assigned the grid's class list outright, and that element is shared with inbox, health and config: running the command over one of those took its layout class with it, and on the grid it dropped the density, layout and packed/masonry classes. It goes through the sync helper that guards exactly this.

  • Fix
    Tab no longer stops at the wrap-around

    The focus trap tried to focus the search overlay's clear button, which carries [hidden] while the query is empty — a silent no-op, after the trap had already swallowed the key.

  • Fix
    g + a digit lands on the first row that is really there

    It jumped to the first row in document order, so with a category's first bookmark filtered out the jump aborted without a word.

Browser extension

  • Fix
    a duplicate lookup that rejected — a proxy error page, an auth redirect — surfaced as an unhandled rejection in the service worker, and neither the keyboard command nor the context-menu entry awaits it. Both routes have the badge as their only feedback, so a save that failed said nothing at all
  • Fix
    one shared hide timer for the popup's message

    Each message set its own without cancelling the last, so a saved shown five seconds after an error vanished a tenth of a second later.

  • Fix
    an IPv6 host was bracketed twice — [[::1]]:8080 — so the extension's duplicate key never matched the server's, which is what the comment above it says it does
  • Fix
    the shared bookmark form's preview module is back in step with the dashboard copy

    the two are required to be identical and the extension's had stayed behind by a feed line.

Speed

  • Fix
    the font preload never reached the page

    It sat inside the block the CSS bundle replaces with a single <link>, so rel="preload" appeared zero times in the served HTML and the font was discovered only after the stylesheet had downloaded and parsed.

  • Fix
    packed masonry reads every height, then writes every span

    Interleaving the two forced a full grid re-layout per category on every render — and continuously while the window was being dragged. The measurements are unchanged; only their order is.

  • Fix
    bookmark and category icons decode off the main thread

    One synchronous favicon decode per row during paint is visible jank on a large page; the preview card already did this.

  • Fix
    the generated theme stylesheet is built in a buffer

    Around 150 blocks appended one at a time reallocated and copied the whole 76 KB string on every append, on every dashboard load.

Under the hood

  • Fix
    the inbox's newest-first order is stable

    , with insertion order as the tiebreak. Timestamps have millisecond resolution, so items written in the same millisecond — a seeded inbox, an import, a batch the extension replays — sorted differently from one read to the next, and at capacity the trim evicted whichever tied item happened to fall last rather than the one added first.

  • Fix
    two leaks: the rate limiter kept an entry for every client address seen since boot, and a host looked up once and never revisited kept its pinned IP for the life of the process. Both are swept opportunistically, under a lock that is already held
  • Fix
    a capture that pushed the inbox past its cap stranded one favicon in data/icons/ per capture

    The evicted items are returned precisely so the caller can clean up their icons, and the caller was dropping the list.

  • Fix
    naming an automatic backup is bounded

    A permission or I/O error made every candidate name look taken, and the loop only ended on file does not exist — spinning forever while holding the lock restore and delete also need.

  • Fix
    the first update check runs inside its own goroutine, where every other scheduler in the tree already runs it

    Called before the listener started, it held boot for the full ten-second timeout whenever egress to api.github.com is blocked — long enough to fail a container health check.

  • Fix
    Vary is added rather than set, so the Accept-Encoding the compression middleware had just written survives

    The ETag is computed over the uncompressed body, so a shared cache in front could otherwise hand gzipped bytes to a client that never asked for them.

  • Fix
    the asset-hash generator writes formatted Go, and the twelve assets these fixes touched carry their new hash

    On a production build the map is read from the embed rather than recomputed, so a returning browser would have been handed the URL it already had cached and gone on running the old JavaScript.

Docs

  • New
    the audit is written down where someone would look for it

    The protected-endpoint table names the automatic-backup routes and the health view's check-a-URL; the self-hosting section says what /data/ publishes and what it no longer does; Data & backups says an archive with no bookmark page in it is refused, and the trash section says what is checked on the way in. Config → Help carries the same three points, in all four languages.

  • New
    README and MANUAL describe what is actually measured

    The analytics section had been written before the content snapshot, the walkthrough and tip events, Fresh, category spreading, right-click menus, and two thirds of what Health reports; all of it is listed now, alongside the fact that a bookmark can also be opened from the health view. The claim that counts are bucketed is true again — see above. The inline-editor passages in both files described a full-page blur that no longer exists, the search filters left out status:feed, Shift + V was still documented as a toggle rather than the pinned card it opens, and Config → Statistics was described as it stood before v1.3.1.

Only docs and tests changed in this release.

v1.3.2 The hover card, rebuilt. +8 15 fix

The hover card, rebuilt. It was seven stacked divs that printed the address twice, hid the one state worth acting on, cut itself off at 360 pixels without saying so, and chased the cursor while claiming to be reachable — on a dashboard where the row underneath already showed more than the card explaining it. It is three bands now, in a fixed order, each absent rather than blank; it knows what the rest of the app knows about the link; and how it is reached is a choice rather than a switch.

Link preview cards

  • New
    the card is rebuilt around three questions

    : what this is, what it says, and what you know about it — a header with the favicon, the title, one address and a status pill; then the picture, the fetched description, your note and the tags; then a facts strip. Every band is absent rather than blank when it has nothing to carry, so a bare link is a short card instead of eighty percent empty space. The address is stated once: the old card printed the full URL in mono and then its hostname on the next line, two of seven rows saying the same thing, neither clickable.

  • New
    the card knows about nextDash

    Last check and ping, uptime over thirty days, a certificate about to expire, the Fresh count, opens and last opened, the shortcut and the page it lives on. All of it read from what the app already holds in memory — hovering a row still makes no request; only a card you asked for may fetch the health figures, once.

  • New
    peek and pinned are separate

    Hovering gives you something to read: the card takes no pointer events and carries no buttons, so there is nothing to aim at and no reason for it to move. Shift + V pins it — focusable, with Copy, Refresh and Edit in a footer, closing on Escape and handing focus back to the row.

  • New
    three ways to reach it, not a switch

    Off, On hover (the new default) and Keyboard only, for people who want what the card says without a panel appearing under the pointer — their only answer used to be off, which throws away the whole feature to avoid one behaviour of it. Beside it a checklist of the eight rows the card may draw, and the card itself, drawn from one of your own bookmarks and redrawn as you tick.

  • New
    uptime and an expiring certificate show on hover

    , not only on a card you pinned. The dashboard already fetches the whole health report on every load to put a number on the health icon — a row per bookmark, carrying monitor stats and certificate expiries — and read twelve counts out of it before dropping the rest. The badge keeps the four facts worth carrying now (uptime over thirty days, certificate expiry, how long something has been failing, and the error), keyed by canonical URL, and the card reads them. No new request: a hover still costs nothing, and the pinned-mode fetch is left as the fallback for a dashboard with the health icon switched off. The health view's own report wins when it is open, since it is the fresher of the two, and a refresh there updates what the cards quote.

  • Fix
    the card no longer chases the cursor

    It was repositioned on every pixel of mousemove while claiming to be reachable, so moving toward the refresh button moved the card away, and on a dense grid it slid across the rows underneath. It is anchored to the row it describes, which is what the keyboard path always did.

  • Fix
    "never opened" is a row

    if (openCount > 0) hid the usage line, so the most interesting state a bookmark can be in — you saved it and never went back — rendered as nothing at all.

  • Fix
    a dead thumbnail leaves no gap

    The image was hot-linked with no onerror and its wrapper shown before it loaded, so a rotted og:image drew the broken-image glyph in a 150-pixel band — in the one app that exists to notice rot.

  • Fix
    nothing is cut off silently

    The card was max-height: min(360px, …) with overflow: hidden: a picture, a title, a description, a note, tags and three more rows passed that easily and the last rows simply were not there. The blocks clamp themselves now, so the card is only ever shorter for a reason you can see.

  • Fix
    the note is your note

    It was rendered in the same tertiary grey as the site's marketing copy and truncated twice — cut at 140 characters in JavaScript, mid-word, then clamped to three lines in CSS. It is labelled, marked with a rule in the accent colour, and clamped once.

  • New
    the hover delay starts calm

    , at 250 ms rather than 150. A card that opens the moment the pointer crosses a row opens on every row you were only passing over on the way somewhere else — and with the card now carrying six kinds of information, the cost of opening one you did not ask for is higher than it was. Fast and Balanced are still there. An install that has already chosen a delay keeps it.

  • Fix
    the hover delay offered delays it would not accept

    The list read Instant, 200 ms, 400 ms, 700 ms, 1 s while the code took 100, 150 or 250 and quietly rewrote everything else to 150: four of the five options did nothing. It offers the three that work.

  • Fix
    turning cards on no longer takes the description away from screen readers

    The card removes the row's title so the browser tooltip does not sit on top of it, and hovering is mouse-only — so assistive tech was left with nothing. The text moves to a hidden element the row points at with aria-describedby, and a pinned card is a real dialog.

  • Fix
    the payload the card draws was assembled by hand in three places — hover, the keyboard toggle and the refresh button — so every new field meant three edits, which is why there were none. One buildPreviewPayload() now, and the sample in the setting is drawn by the card's own code rather than a mock-up free to drift from it

Fixes

  • Fix
    an edit no longer resets a bookmark's statistics

    The dashboard saves a page by POSTing the whole list back, built from what the browser had in memory — so anything the server had written since the page loaded was silently absent from it, and the save wrote its absence. Open a bookmark, then edit any bookmark on that page, and the open count went to zero; the last check, its error, the fetched preview text and the certificate host went the same way. carryServerOwnedBookmarkFields() puts back every field the payload does not carry, matched on the canonical URL. A value the payload does carry still wins, so an import keeps its own counts and a check still clears an error it has just re-tested.

  • Fix
    "Show in Health" lands on the row you asked for

    The health list selects the row under the pointer, and a row arriving under a cursor that never moved is not a hover — but the browser reports it as one. Opening a bookmark in Health left the pointer wherever the menu item had been, the list drew beneath it, and the row you asked for lost its selection to whichever row landed there. Hovering now has to be earned by an actual pointermove after a row is focused by name; the same applies to a ?hv_id= deep link.

  • Fix
    the inline editor takes the clicks aimed at it in Safari

    Every non-editing row's children carried filter: blur(), which gives each column its own compositing layer — and WebKit hit-tests those in paint order rather than by z-index, so a blurred neighbouring column was painted over the tall inline form and ate every click on its fields. pointer-events: none does not help; WebKit hit-tests the layer regardless. At 18% opacity the blur was doing almost nothing visible, so it is gone — the same fix that settled this bug class in the check-mode popover. The rows stay dimmed.

  • Fix
    the health badge fetched the entire health report on every dashboard load — a row per bookmark with names, tags, scores and reasons, plus the duplicate groups, the daily trend and the fleet view — to read twelve counts out of it. It asks ?view=facts now: the counts plus only the bookmarks that have something to report. Measured against a real library: 8,424 bytes down to 458. The health view still loads the full report, which is the one screen that draws it
  • Fix
    bookmarksLoading and bookmarksKeysHint were each written twice in the same locale object, in all four languages

    A JSON parser keeps the last one and says nothing, so the earlier line was a string that looked live and could never render. npm run validate:locale-duplicates now fails on any key written twice, reported by path and line — the check that would have caught the three delay labels added and withdrawn during this release.

  • Fix
    :preview off followed by :preview on no longer moves someone who chose keyboard only onto hover

    The command is a switch, so it puts back the mode it took away.

  • Fix
    the twinkle that marked this release's new setting still pointed at Appearance → Layout, two releases after the setting it introduced

    A mark that outlives its release teaches people to ignore the mark, so the trail is cleared until the next one earns it.

Config

  • New
    Appearance → Display → Link preview cards

    is a panel of its own: the mode as three labelled choices, the hover delay, the eight-row checklist, and a live card drawn from one of your own bookmarks — the setting you otherwise had to leave the screen and hover something to understand. It names Bookmarks → Link preview and Health, where the fetched text and the bookmarks without one are managed, so a reader landing on any of the three finds the other two.

  • New
    Config → Overview

    carries the card as this release's spotlight, with what it is, how to reach it and the way through to the setting.

Docs

  • New
    the Appearance help article gains a Link preview cards section

    the three bands, the three modes, Shift + V, and the checklist — in English, Dutch, German and French. The README's line about a card that "shows full URL, open count, and last-opened date" described a card that no longer exists, and the MANUAL's compatibility table said link previews were off by default.

  • Fix
    linkPreviewDelayInstant and showLinkPreviewCardsLabel were locale strings for controls that no longer exist

    both are gone from all four languages. Three delay labels were added and then dropped again when it turned out the file already carried them a few lines further down — a duplicate key in the same object, where the later one silently wins.

Only docs and tests changed in this release.

v1.3.1 Fresh, made to work. +16 9 fix

Fresh, made to work. It shipped in 1.3.0 depending on a setting most installs have switched off — link previews — so it could never find a feed, and a reader who turned it on watched a dashboard that never changed. This release makes it look for its own feeds, say what it found, and answer which bookmarks take part at all. Plus the modifier click every browser honours, given back.

Fresh

  • New
    which bookmarks take part in Fresh, three ways

    A row with a feed and nothing new was identical to a row with no feed, and the count on the tab said how many there were without saying which. The bookmark editor now shows a Feed line with the address when there is one — the place to look when a bookmark never says anything. status:feed (and -status:feed) narrows a search to the ones taking part. And Behavior → Fresh → mark rows that publish puts a quiet dot on those rows even when nothing is new; off by default, because a mark on twenty rows that are silent most of the time is the noise Fresh exists to avoid. A real count still wins over the dot.

  • New
    Fresh is a tab of its own

    under Behavior, between Inbox and Status & health. It was the fourth panel down a tab about link checking, which answers a different question — is this still there against has this moved on — and is where a reader stops looking. Behavior is seven sub-tabs now.

  • Fix
    Fresh looks for its own feeds

    It learned where a feed lived only as a side effect of fetching a link preview, so an install with link previews switched off never fetched a page, never discovered anything, and answered “nothing new” forever — which is exactly what the reader who reported this saw, with the feature on and feeds.json empty. Switching it on now reads the head of each saved page itself, records the pages that have no feed so they are not asked again for a month, and polls what it found. The panel says what came of it — 7 of 7 bookmarks asked · 0 publish a feed, and in that case a sentence saying so is not a fault — with Find feeds now beside it to repeat the round.

  • Fix
    Fresh polls on an hour of its own instead of borrowing the health recheck interval, which can be switched off entirely while Fresh is on — and was, on that same install — and runs as slowly as once a day. Every request is conditional, so an hour is unremarkable for the site on the other end
  • New
    Fresh is offered rather than hidden

    It is off by default and its switch sits four panels down a tab called Status & health, so the people it was built for never met it. A corner card now offers it once — skipped only on an all-but-empty page, and never shown to someone who already has it on — and hands over to a four-step walkthrough rather than switching anything on: what the count means, the collection it gathers into, why polling costs almost nothing (the feed was already found while a preview was fetched, and every request is conditional), and what it deliberately is not. The last step is the switch itself, because a walkthrough that ends in “now go and find the setting” wastes the one moment the reader is convinced. It is offered before those two, since it is the one thing here nobody has had the chance to meet. Same shape as the side-rail and spread-across-columns cards, and the same walkthrough is one button away in Config → Help → Monitoring, where Fresh now has a panel of its own with a state line saying whether it is on for you. No article list, no titles, no OPML — deliberately not a feed reader.

The dashboard

  • Fix
    Ctrl/Cmd+click on a bookmark opens it in a new tab

    , as it does on every other link on the web. It used to tick the row for a bulk action, with preventDefault — so the one modifier every browser honours did the opposite of what it does everywhere else, and on a Mac it came with the row menu on top of that, Ctrl+click being the platform's secondary click. The mouse route into a selection is Alt+click now, on the grid and in the health view alike; Shift+click still extends a range, x still ticks the row under the cursor, and Select is still in the right-click menu. The open is recorded by the row itself, since letting the browser have the click means the anchor's own handler never runs — without that, opening this way would not have counted, and Fresh reads the same timestamp.

Statistics

  • New
    the section says what its numbers mean

    What this says opens Overview with the three things that follow from the figures — where your opening lands, what is going unread, what is not answering — each with the button that acts on it, and nothing at all when there is nothing to report. A count you cannot act on is trivia.

  • New
    the tiles carry a direction

    The daily points the health report has been recording all along now also hold how many bookmarks were untagged and how many opens there were, and Statistics reads them through a new /api/health/trend — a file read of a few dozen points rather than the full report they used to ride with. A tile says +7 this week when it moved, and nothing when it did not: +0 is noise dressed as information. Narrowed to one page, the comparison is dropped rather than invented.

  • New
    the activity chart in a sentence

    , above the bars: how long the window is, where the busiest point sits, and how many bookmarks it accounts for. A screen reader had thirty numbers in a table and no shape; everyone else had to hover for the peak.

  • New
    most-opened and category rows hand off

    to the bookmark list the way the tag rows already did, and each tab carries a 🔗 that copies a link to it. Statistics has been deep-linkable all along and nothing on the page said so.

  • Fix
    computeStats() walked every bookmark five times over on every paint — a tab switch, a scope change, the Overview cards, the export — for figures that cannot change between two paints of the same data. It is computed once per paint now and shared by the six callers, and dropped at the start of the next one, since a bookmark's own fields are edited in place all over the app
  • Fix
    the CSV carries every tab

    Health and Inbox come from the server and load when their tab is opened, so an export from Overview silently left two of the five tabs out of a complete-looking file. It waits for them now, and writes inbox_included,0 if a fetch failed rather than dropping the rows without saying so.

  • Fix
    the note explaining that Inbox and Health cannot be narrowed to one page no longer appears on a single-page install, where there is no narrowing to explain

Health

  • Fix
    the row menu is as tall as its contents

    It capped at min(70vh, 24rem) — 384px on any window — so a row whose repair options ran long put a scrollbar inside a context menu, and a menu you have to scroll is a menu whose last item nobody finds. Sprawl was the reason for the cap, and placement answers that better: the menu flips above its trigger when there is no room below, and the cursor path clamps it inside the viewport. The window is the only cap left.

Bookmarks

  • New
    the filters are in the address bar

    The list could be narrowed five ways and the hash knew only the page, so "the 41 untagged on Work" was something you could see and not hand to anyone, and a reload threw it away. Query, category, tag, cleanup filter and sort now ride in the hash, and a link opens the list it describes. An unfiltered list keeps the short hash it always had.

  • New
    an empty list says which filter emptied it

    It blamed your search whatever was actually narrowing — a cleanup filter with nothing in it, a page with no rows, a tag nobody uses — which sent people looking in the search box for a query that was not there. Each filter that can empty a list now says so in its own words.

  • New
    a selection survives a filter change

    , so "tick the untagged, then also the duplicates" is possible at last. The bulk bar is honest about the consequence: 12 selected (3 not shown by this filter), because acting on rows you cannot see is exactly the surprise the old clearing was there to prevent.

  • New
    undo for bulk tags, pins and availability

    , on the eight-second toast the bulk delete already had. Forty rows retagged could not be picked apart by hand, and replace cannot be reversed by reasoning about what it did — so the undo restores the pages as they were rather than inverting the edit.

  • New
    the three orders people use are chips

    , not options five and seven of a menu: page order, recently added, most opened, with the rest still in the select. Beside them, Changed in the last week — the question after an import or an afternoon of tidying, which every bookmark has carried the timestamp for and nothing could ask.

  • New
    the keys the list answers to are written under the toolbar

    j/k, x, Enter, Esc. They worked; nothing said so.

  • New
    the list draws a screenful, not the whole library

    Infinite scroll answered how much is fetched and nothing about how much is painted: a row is thirty-four elements, so a thousand rows is thirty-three thousand nodes and four megabytes of markup, and five thousand is a third of a second of layout on every repaint — a tag added, a row ticked. The rows near the viewport are drawn and the rest are two spacers of the right height, so the scrollbar still describes the whole list and nothing jumps: two thousand rows go from sixty-seven thousand nodes to about a thousand, and the build from 88 ms to 3 ms. Off below a hundred and twenty rows, where the arithmetic would buy nothing, and off while a row is expanded into its editor, whose height the spacers cannot know. j/k walk the loaded rows rather than the drawn ones and drag the window with them, and focus is put back on the row it was on — otherwise closing a menu would drop the list's keyboard navigation.

  • New
    the bookmark list is its own file

    , dashboard-config-bookmarks.js, fetched when config opens rather than carried by every visit to any other section: twelve methods and four hundred lines that draw rows, the bulk bar, the tag cloud, the chips and the crumbs. Same prototype, same methods, moved verbatim — only the moment they arrive has changed. Opening the section waits for them rather than flashing a placeholder and repainting over it, which would tear down whatever the reader had already reached for; the placeholder is what a failed fetch leaves, and it says the list is on its way. Split one section at a time on purpose: lifting the whole of config out at once failed on forty-one tests, and the failures did not name the method that had moved.

  • Fix
    typing in the search box no longer throws away how far you had scrolled

    Refining a query is a narrowing of what you are already looking at, and being thrown back to row fifty after four hundred rows — for one letter, sometimes a letter you then delete — is what makes a long list feel hostile.

  • New
    one answer to “which bookmarks”

    status:untagged in the search bar and the cleanup filter Without tags here are the same question, and they were written twice, so they were free to disagree: a tag that is nothing but spaces counted as a tag in one place and not the other, and the statistics panel had a third opinion about a note of whitespace. Fourteen of those questions — untagged, noted, never opened, opened once, insecure, no icon, changed, stale and their negatives — now come from one registry, bookmark-predicates.js, loaded before the search bar, the config list and the statistics. Only Duplicates stays local: it is the one that has to know about every other bookmark's address. The search bar also learned status:feed and status:unfed on the way in.

  • Fix
    the visible-rows memo is dropped at the start of each paint of the list

    Bookmarks are edited in place all over the app, and none of that moves the array identity it keyed on, so the list could show a filter that no longer held.

Docs

  • New
    the Fresh walkthrough and its help article answer the question every reader actually arrives with

    The last step is If nothing shows up — an empty dashboard is the usual answer and not a fault, because most saved pages publish nothing — and both now name the count on the tab (12 of 40 bookmarks asked · 2 publish a feed) as the way to tell that apart from a broken feature. The article also says plainly that a row carries no mark for publishes, but nothing new: a badge on twenty silent rows would be the noise Fresh exists to avoid.

Only docs and tests changed in this release.

v1.3.0 Twenty-four changes across 148 files, +14,585 / −3,343 lines, and one subject running through all of it — the life of a link. +32 8 fix

Twenty-four changes across 148 files, +14,585 / −3,343 lines, and one subject running through all of it — the life of a link. How it gets in when you are not at the desktop that has the extension; how you find out it has rotted; how the tidying becomes something you can finish rather than a number you learn to ignore; and how a page you saved tells you it has published something. The fourth strand is speed: the dashboard's first load is about five times lighter than it was.

Capture — from wherever you are

  • New
    PWA share target

    . Installed as an app, nextDash appears in the phone's share sheet; a shared link lands in the Inbox and the app opens on it. Android often puts the address inside the shared text rather than in the URL field, so the first http(s) address in either is used, with trailing sentence punctuation left to the sentence.

  • New
    GET /add?url=…&title=…

    , and a bookmarklet built for you in Config → Help → Inbox carrying this install's origin. Both routes are plain GETs because neither a share sheet nor a bookmarklet can set a header; on an install with a write token, NEXTDASH_CAPTURE_TOKEN opens these two routes and nothing else.

  • New
    integrations/

    : a shell script, two Raycast commands (one for a URL, one for the frontmost tab in five browsers), a Dropzone action, a Ulauncher extension, and Alfred and Apple Shortcuts recipes. No binary bundles — steps you can read instead.

  • New
    manifest shortcuts

    for Inbox, Health and Config, so a long-press on the installed app opens the view rather than the dashboard.

  • Fix
    duplicate detection looks everywhere, not only at the page being saved to, and answers with the conflicting bookmark's name, page and category rather than a bare 409. Same page is refused; another page asks, with the existing bookmark as a link and Save anyway to file a second copy. Moves send allowDuplicate, since a move is an add followed by a delete

Link rot

  • New
    broken since

    : the first failure of a run is recorded, so a row can say failing for three weeks rather than only broken. Carried into the filters, the row, the export and the report.

  • New
    soft 404 detection

    : a monitored check can spot a page that answers 200 while saying not found. One bounded body read per check, which is why it is a switch beside the check timeout rather than always on.

  • New
    group by site

    : one host down reads as one problem instead of forty.

  • New
    archive fallback

    : point a dead link at its last Web Archive capture, keeping the original address in the note.

  • New
    history days

    : the trend can be read over a longer window, and a window the samples cannot fill says so rather than pretending.

  • New
    Rot report

    in the toolbar: what has gone, moved or been rewritten, has been failing for over a month, is broken and never opened, and what broke this week. Everything in it was already in the report; what was missing was somewhere it added up.

  • Fix
    the Rot report button was never styled, and rendered as a bare user-agent button between four styled ones

Cleaning as a ritual

  • New
    a card in the corner of the dashboard names what is waiting — *“10 links to review

    4 broken, 3 never opened, 3 not opened in a year”* — and starts a bounded session over the worst ten in the health view's Work through. Below five waiting links it stays quiet.

  • New
    the session ends

    a count of what was dealt with, Another ten while more are waiting, and Done for today which puts the offer away until the next local day. Skipping is not handling, so the count is honest.

Fresh

  • New
    a page's <link rel="alternate"> feed is noted while previews are fetched, polled on the background re-check interval with a conditional request, and a bookmark carries a count of what has been published since you last opened it. A Fresh smart collection lists them newest publication first
  • New
    opening the bookmark clears the count

    lastOpened is the whole of the read state. No article list, no titles, no OPML — deliberately not a feed reader.

  • New
    off by default, under Behavior → Status & health → Fresh

    switching it on polls once immediately rather than waiting for the scheduler.

The dashboard, in place

  • New
    Shift + F

    filters the page you are on: a slim bar narrows the rows, hides the categories left empty, and keeps the layout, the cursor and any selection.

  • New
    the scroll offset is remembered per page

    , across a view change and a reload, for as long as the tab is open. Switch it off under Behavior → General.

  • New
    a selection can be pinned and switched to Periodic or Monitor in one action, and a bulk tag change can be undone for eight seconds
  • New
    Shift + Alt + ← / →

    moves the focused bookmark into the category beside it; smart collections are skipped, being a query rather than a place.

  • New
    what typing a bookmark shortcut does is a setting

    : open the moment it matches (default), open after a short pause, or press Enter. Inbox settings moved to a tab of their own, and Search gained the three-card control with an interactive ℹ.

  • Fix
    the default is open the moment it matches again, and v1.2.0's change to press Enter is recorded here as a mistake

    The reasoning in v1.2.0 was that an instant shortcut can swallow an ordinary word, and which words survive depends on the shortcuts you own. That is true, and it is the rare case: what the change actually did was charge every shortcut, on every use, a second keystroke to prevent it — which takes away the reason to have a shortcut at all. The collision has two answers that cost nothing when it is not happening: the two other modes, and renaming the shortcut that clashes.

  • Fix
    the new default reaches existing installs

    shortcutOpenMode is written into every settings file v1.2.0 touched, so a default change alone would have reached nobody. migrateShortcutOpenModeDefaultInstant moves installs still carrying enter — the value nobody chose — to instant once, behind shortcutOpenModeInstantMigrated; delay is left alone, because it can only be there because someone picked it, and the marker means anyone who sets Enter back keeps it through the next restart.

  • Fix
    the category header's glyph follows the favicon harmonisation setting, instead of staying at full saturation beside recoloured icons
  • Fix
    the filter bar is placed above the grid rather than inside it

    As the layout's first child it was fine while the layout was a CSS grid and wrong in every other shape: packed columns lay it out as a flex row that does not wrap, so the bar became a column of its own — squeezed to a fraction of its width and pushed off the left edge of the window (x = −21 on a three-column page). It also kept a search field inside role="grid" and gave masonry a child that is not a category.

Config

  • New
    Config → Help → Tips filters itself

    Fifty-three tips in nine groups, and the search in the header returns whole panels — the wrong grain when you are after the one key that does the thing. The field narrows to the line, counts what is left, says so when nothing matches, and hides a group whose rows have all gone. Rows are hidden rather than re-rendered, so the cursor stays where you are typing.

  • New
    a topic that continues on another tab says so

    Health and Monitoring answer different questions on purpose, but the split left no thread: seven panels now carry a Continues in line — availability to uptime and alerts, working through the list to drift, the walkthrough to expected responses and maintenance windows, and back. The button writes the same #config/help/<tab>/<panel> hash the panel's own link copies, so clicking it and following a shared link land in the same place.

  • New
    the Server log panel says whether it is on for you, like the four panels that already did

    It is off by default, which is exactly when a reader follows the prose and finds nothing where it says. Fresh deliberately has no such line: it is a paragraph inside the monitoring prose rather than a panel, and hanging the line on a panel about something else would say something untrue.

  • New
    the version panel reads the release index instead of carrying the number in four translated strings

    It read nextDash 1.1.0 for two releases after 1.1.0, because the fourth file was the one nobody remembered. The ★ modal, Overview → Latest update and this heading now agree by construction.

  • Fix
    on a narrow screen, a config section reached by hash or by a restored visit is scrolled into view properly

    The strip carries scroll-snap-type: x proximity, which re-snapped the nearest-fit scroll to the closest button boundary and left Help hanging 36px over the right edge with 112px of scroll still available. It scrolls the strip itself now, aligned to the start as the snap expects.

  • Fix
    Help opened with empty panels

    when its prose did not arrive. That text is a locale scope of its own — a third of the translation file, fetched beside the config module — and every panel falls back to nothing, so a page of headings with no text under them was the failure mode. A core locale load replaces the whole bundle, so one landing after the help scope had merged (a reload onto a #config/help link, a settings sync while config is open) wiped it, and switching help tabs repainted from the same empty bundle. The core load now keeps the help keys when the language has not changed, and every help repaint asks the bundle whether the prose is really there rather than trusting a flag.

  • New
    Appearance → Button bar

    is one tab for one object: where the bar sits (the five positions, each drawn) and what it carries (main buttons and extras, with Show all / Hide all and a count). The position was a panel on Layout and the twelve toggles were two panels on Toolbar & tabs, two tabs further along, so moving the bar and hiding a button on it were separate errands. Toolbar & tabs keeps the Header group, which is a different strip. Everything that pointed at the old homes now points here: the settings search, the side-rail card's Open button bar settings, both Overview → New features entries, Help → Appearance, the manual and the README.

  • New
    the settings search matches a setting's current value as well as its name, and shows it after the location, with switches read as On/Off
  • New
    settings that stay server-wide while Keep settings on this device only is on carry an all devices mark

    the switch itself is marked this device.

  • New
    Duplicate

    a page (with its categories, and optionally its bookmarks) or a category (with its width, icon and sort). Copies start with empty check and open history, and without the original's shortcut.

  • New
    edit a name or shortcut in the row

    : double-click the title or click the shortcut pill — including the faint + on a bookmark that has none. A shortcut already in use is named as you type it and refused on Enter, checked across every page.

  • New
    a tag in Most used tags opens Config → Bookmarks filtered to it

Speed

  • New
    99 scripts and 42 stylesheets are served as two bundles, the generated theme is inlined, Help's translations load with Help, and each view's stylesheet arrives when the view is opened. First load: 169 requests and 915 KB → 30 requests and 685 KB. NEXTDASH_BUNDLE=off restores the individual tags
  • New
    config's cold open is 74 ms → 55 ms, the bookmark list draws 2757 → 1762 nodes, and the module is 1000 KB → 884 KB with the statistics renderers loading beside their own section

Docs

  • New
    240 dead help strings are gone

    60 per language, 408 KB, describing the config that was replaced: tab groups called System/Dashboard/Extras, archiving pages, an Essentials/Advanced toggle. Nothing in the app had read them since that config went; the only things that named them were scripts/apply-help-prose.js and scripts/help-prose-content.js, generators for a help system that no longer exists, which go with them. en.json is 591 KB → 494 KB, and the 23 of those strings that were never translated into German or French stop being a translation debt.

Only docs and tests changed in this release.

v1.2.1 One fix, in the Health view. +1 3 fix

One fix, in the Health view. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.2.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those two tokens are what re-show the modal, and a one-fix release should not push a feature release off the front of it for everyone who has already read it.

What's new

  • Fix
    usage no longer decides where a row sits

    never_opened and not_opened_30_days cost 10 points each, so opening a bookmark — the action the Broken filter's own note asks for — raised its score, and under the default worst-first sort carried the row away: measured on a 200-bookmark install, position 10 of 200 became position 188 while the reader was still working through the list. Both penalties are 0 now; the flags, the Unused and Stale tiles and filters, and the reason text on the row are unchanged.

  • Fix
    the score sort's tiebreak reads the flags with the two usage ones removed (stableStatusRank) rather than the status

    Status alone was not enough: opening a never-opened row that also has no preview turns unused into missing-preview, a different rank, and the row travels on that instead.

  • Fix
    a row you have acted on keeps its position

    Opening one under Unused, or re-checking one under Broken, takes it out of what the filter selects, and the list used to close the gap under the cursor. It stays at the position it held, dimmed and marked handled, until the list is asked a different question (filter, sort, search) or reloaded on purpose with R or Retest all — and when the view is left.

  • New
    the score breakdown separates deductions from context

    reasons that cost nothing are listed under worth knowing, at no cost to the score, because a full score with a deduction printed beneath it reads as broken arithmetic.

Only docs and tests changed in this release.

v1.2.0 The keyboard release, and the one where three views stop lying about what they know. +16 9 fix

The keyboard release, and the one where three views stop lying about what they know. Typing on the dashboard used to open bookmarks mid-word; the inbox counted links it was not showing; a failed health check worked out its cause and threw it away. All three are now what they appear to be.

Typing and keys

  • Fix
    typing on the grid no longer opens anything by itself

    A bookmark shortcut fired the instant the typed query matched it exactly, so which of your words survived depended on which other bookmarks you owned: on a 200-shortcut install, eight of thirteen ordinary words were swallowed mid-word. Typing now narrows the list and Enter opens the top result, with the exact shortcut match leading it — one keystroke more, and stable against every bookmark you add later.

  • Fix
    g, j and k no longer eat the first letter of a word

    Letters reach the grid only while a row is selected (_letterMayActOnGrid); the arrows always pass, j/k stop propagation once they act, and the g/G chord paints data-grid-keys on the body instead of swallowing the keystroke. c is the documented exception: it still creates a category unconditionally, because four specs pin that behaviour deliberately.

  • New
    the mode prefix is drawn in front of the query line (> search, : commands, ? finders) with an × to clear it, and closeSearch() now clears #search-query instead of leaving the old text behind
  • New
    an optional key legend under the bookmark grid, shown after the first keystroke and hidden again on Enter

    Behavior → General → Show grid key legend, on for fresh installs (Settings.ShowGridKeyLegend).

  • New
    Show shortcut hints on toolbar icons

    is off for everyone, via a one-time migration (migrateShortcutTooltipsDefaultOff, marker ShortcutTooltipsOffMigrated). A default change alone would not have reached existing installs, which all carry the field in their stored settings.

  • New
    the shortcut field warns about the letter you are assigning

    ShortcutKeys.gridKeyNote() says what the grid does with it and when, and usedShortcutsNote() lists the shortcuts the page has already spoken for.

Inbox

  • Fix
    every count follows the active filter

    filterBaseItems()/narrowItems() feed the tiles, the pills and the badge, Mark all read becomes Mark shown read while isNarrowed(), and the first tile is Active — asleep is deliberately excluded.

  • Fix
    snoozed links have a footer saying how many are asleep and when the first wakes, and domainOptions() no longer offers a host whose only link is asleep
  • New
    Import

    beside the CSV and JSON exports (openImportPicker, parseImportPayload, importFromFile), skipping links already present and reporting added / already there / rejected.

  • New
    markUnread(id) and a row-menu entry for it, and the fetched summary (previewDesc) is rendered on the row, searched, and carried into both exports

Health

  • Fix
    a failure records its class (failureClass, HealthSample.Fail) so DNS, timeout, refused, TLS, redirect and content failures reach the incident list, the timeline and the CSV with a reason. Anything that was not an HTTP error stored Up:false, Code:0 and showed nothing
  • Fix
    a failed check is re-probed after monitorConfirmDelay and only recorded if it fails again, so one dropped check no longer dents a month of uptime
  • Fix
    buildMonitorStats reports CoveredMs, and renderUptimeTiles prints how much history is behind a window rather than labelling a week "30 days"
  • New
    certificate expiry comes from every check

    liveHosts now includes CheckStatus bookmarks, not only monitored ones.

  • New
    a recovery names its duration, TREND_SERIES gives the trend chart six series with a per-mode axis, /api/health/expectations-bulk mutes or unmutes a whole selection, and Settings.HealthCheckTimeoutSeconds replaces the fixed three-second dial timeout

Search

  • New
    negation. parseSearchFilters produces filters.not, and matchesAdvancedFilters runs the positive keys then the negative ones, so tag:dev -status:pinned is expressible in the bar the way it always was in a collection rule
  • New
    status:untagged, status:tagged, status:noted and status:unnoted

    :trash as a command onto #config/data-backups/trash; and Ctrl/Cmd+Enter on a result opens in a new tab regardless of the standing preference.

Dashboard and config

  • New
    undo for moves: single (undoBookmarkCategoryMove) and cross-page bulk (undoBulkMoveToPage), each restoring from a snapshot so every bookmark returns to its own category. showGroupedNotification translated undoCallback into nothing — the bulk-delete undo it also gates has been dead since it shipped
  • New
    category icons (openIconEditor, live preview into .category-title-icon) and Alt+←/→ to move a category, announced to screen readers
  • New
    setting-art.js draws the settings whose subject is a shape (grid, spacing, margins, density, dots, type size, layout version, bar position, flow), in config and in help
  • Fix
    a settings change made elsewhere now reaches an open dashboard

    fetchDataRevision tracks the settings revision (GetSettingsRevision) and routes a change through refreshAfterConfigSettingsUpdate.

  • Fix
    a failed automatic backup is visible

    autoBackupRunState records LastRunAt/LastRunError and the tile reports it.

  • New
    a bookmark row in config carries a page › category breadcrumb pill, each half filtering the list
  • New
    fresh installs start on Retro CRT (defaultThemeID), with fold-all and shortcut hints off

    Existing installs are untouched.

  • New
    the extension can send a link straight to the inbox

    two context-menu entries, a quick-save-inbox command on Ctrl/Cmd+Shift+U, and tags carried through postInboxLink.

Only docs and tests changed in this release.

v1.1.2 A release that exists to announce the one before it. +1 1 fix

A release that exists to announce the one before it. v1.1.1 shipped hideFromModal so it would not displace v1.1.0 on the day both landed; that call is reversed here.

What's new

  • Fix
    the hideFromModal flag is dropped from the v1.1.1 index entry, so the modal lists it again

    The flag only ever gated the modal: the release tag and Config → Overview → Latest update read index[0] and have shown v1.1.1 since it shipped.

  • New
    DASHBOARD_RELEASE (2026.08-dashboard-release-v1.1.2) and NEXTDASH_WHATS_NEW_DATA_VERSION (whats-new-v244) are bumped, so the modal reopens once for every user. Unbumped they would have left the un-hiding invisible to anyone who had already dismissed it — the two tokens are the whole re-show mechanism, which is why v1.1.1 deliberately left them alone

Only docs and tests changed in this release.

v1.1.1 Keyboard consistency, and the parts of the app that teach it. +11 9 fix

Keyboard consistency, and the parts of the app that teach it. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.1.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those tokens are what re-show the modal.

Keyboard

  • New
    the Shift+letter family is closed

    Shift+E inline edit and Shift+V preview join move, tag, delete, checking, pin, share and reveal. ; and [ still work, undocumented, the way 0 still opens the inbox. Brackets mean previous / next sub-tab in config, and one pair of keys meaning two things was the reason to move preview off [.

  • New
    share moves to Shift+L, so Shift+S always opens config

    It was the only key whose meaning depended on whether a row was selected, which took two cheat-sheet rows and a parenthesis to explain. The capture-phase handler still declines rather than swallows a key it has no row for — that is what keeps Shift+S reaching setupPageShortcuts over a selected row, and tests/shift-key-row-actions.spec.js pins it.

  • New
    bare letters act on keydown

    C_HOLD_MS and the g-chord hold are gone, and with them the whole keyup handler in keyboard-navigation.js and SearchComponent.addShortcutLetter, which had no other caller. _activateGChordMode now runs on the first g; G_CHORD_MS (3s) is the only timer left.

  • New
    j/k alias ArrowDown/ArrowUp in the grid, matching config's section rail and bookmark list
  • New
    Shift+Home focuses the category header via focusCategoryHeader(), which reuses resolveFocusedCategoryEl

    Delete on a focused header calls categoryMenu.runAction('delete', …) instead of opening the menu; Shift+F10 opens it.

  • Fix
    handleContextMenu took clientX/clientY at face value, which a keyboard-raised contextmenu reports as 0/0

    menuPointFor() falls back to the row's rectangle; the category menu's own handler does the same.

  • Fix
    resolveFocusedCategoryEl took an options argument

    :width keeps the first-category fallback because the palette names what it acts on, Shift+W passes fallbackToFirst: false and falls through.

  • Fix
    search.js kept a code-name list (KeyM/KeyD/KeyT/KeyB) that had fallen behind the keys added since

    it tests /^Key[A-Z]$/ now.

  • Fix
    setupPageShortcuts was the only typing guard in the app without an isContentEditable check

Discoverability

  • New
    DashboardContextMenu renders a kbd.move-popover-item-key per entry with a matching aria-keyshortcuts, for all eleven actions that have a key

    ShortcutFormat.ariaKeys() and .modifierLabel() are shared with the category menu, which had the chips but no aria.

  • New
    syncShortcutAriaHints() stamps aria-keyshortcuts on the toolbar, the header buttons and the first nine page tabs

    It runs independently of showShortcutTooltips: the tooltips are a desktop hover affordance that can be switched off, this is the only route the keys have to assistive technology. shortcutButtonDefs() replaces the three parallel lists that let the header row end up with tooltips and no aria.

  • Fix
    the side-rail legend printed the what's-new button's ★ glyph in the same chip as real keys

Cheat sheet

  • Fix
    buildPrintSections passed each row's printFallback to the caller's label resolver as a fallback, and generate-cheatsheet.cjs resolves from locales/en.json, where the i18n check guarantees every cheatKey exists. The short wording therefore never reached paper for any of the 23 rows that carry one. printLabel() uses it directly. validate-cheatsheet-registry.cjs gains a check built with the generator's resolver — with the identity resolver the other checks use, a printFallback wins either way and the check would pass against the bug
  • New
    printed rows for k/j, Shift+E and Shift+Home

    nextDash-cheatsheet.html, nextDash-cheatsheet.pdf and the static/ copy regenerated.

Config

  • New
    logFilterActivity is a fourth value for the log viewer's Show control, matched on Source == "activity" by logEntryMatchesFilter() rather than on severity. Activity lines already flowed into serverLogSink through log.Printf("activity: …") and parseServerLogLine already split the subsystem out; nothing about capture or NEXTDASH_ACTIVITY_LOG changes
  • New
    Help → About

    carries the wordmark and three addresses: nextdash.cc, GitHub, and jordibrw.nl. The help-signature sign-off is dropped, so each address appears once.

Dashboard

  • Fix
    .category-title centres its flex items instead of aligning them on the baseline

    The + button hangs padding and a border below its own baseline, which made every header carrying it 1.44px taller; centring costs nothing, where a line-height tall enough to swallow the button added 3px to every header. .category-title--multiline keeps flex-start.

  • Fix
    * carries the same guards as ! and ., with an exception for its own modal so it still closes the recent list

Analytics

  • New
    settings-snapshot widens from 21 to 45 fields and a new content-snapshot reports install size (bookmarks, pages, categories, tags, finders, collections, monitored, inbox totals). Every value is bucketed client-side; MAX_EVENT_PROPS = 50 is Umami's per-event limit, which is why it is two events. analytics_content.go counts server-side and returns "" when telemetry is off — analytics_content_test.go proves it with a nil store, where any counting would panic
  • Fix
    a custom theme reported its own id, which is theme-<base36>-<4 chars> and random per install

    not a name leak, but distinctive enough to follow one install across releases. It reports custom.

Only docs and tests changed in this release.

v1.1.0 The first minor since 1.0: a category can be wider than one column. +14 4 fix

The first minor since 1.0: a category can be wider than one column. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

Categories across columns

  • New
    Category.Spread marks a category as allowed to run across grid columns

    uncategorized and the smart collections keep theirs in settings.categorySpreads[pageId][categoryId], the shape categorySortModes already uses. dashboard-category-span.js owns both, so no caller has to know which applies.

  • New
    the width itself is derived, never stored

    spanForCount is min(ceil(count / categoryItemLimit), effectiveColumns, 12). It was a number the user picked in the first draft; it became a switch because the number is implied by two settings that already exist, and a stored number goes stale the moment a bookmark is added.

  • New
    applyCategoryItemLimit multiplies the limit by the span, so a spread category shows its limit once per column and stays the height of its neighbours

    refreshAllCategorySpans runs from finishIncrementalRefresh, which is what makes an added bookmark bring the next column with it rather than waiting for a reload; settleSpanChange follows that through to the "+ N more" cut and, in packed mode, to a full re-render.

  • New
    the two settings rule out each other's extreme

    spreadUnavailableReason returns unlimited-items when categoryItemLimit is 0, and the config select disables Unlimited while anySpreadCategory holds. Both say why where they are asked for.

  • New
    routes: DashboardCategoryMenu (entry flips to Back to one column, no aria-checked beside a label that already flips), Shift+W in keyboard-navigation.js, :width on|off|all, a data-cat-spread button per row in the categories editor, and Appearance → Layout → Categories across columns for the defaults and the reset
  • New
    .category--wide spans with `grid-column

    span var(--category-span) and repeats the row's track pattern once per column, so subgrid alignment survives. The inner column gap is the grid gap plus 2 × --category-inline-pad: a run of categories pads every column on both sides, a single wide box only its outer edges, and without that the inner columns sat 16px left of the grid. syncWideColumnTracks` pins the shortcut and lead tracks, which are intrinsic and were sized per repeat by whichever rows happened to land in them.

  • New
    a rule under the header spanning the block, and a ↔N badge in the header, both dropped while the category is collapsed or one column wide

Packed columns

  • New
    packed keeps its round-robin flex columns while nothing spreads, and switches to a grid (packed-masonry) the moment something does

    --masonry-span rows per category from dashboard-packed-masonry.js, grid-auto-flow: row dense, a ResizeObserver per category. Bands were tried first and left a hole the height of the tallest column beside the wide block.

  • Fix
    syncCategoriesFromDom read the columns in document order while the render filled them round-robin

    Those are not each other's inverse, so every category drag rewrote the order into one that redistributed differently and scrambled the page. readCategoryElementsInOrder is the single inverse now, keyed on what is in the DOM, and getExistingCategories delegates to it.

  • Fix
    syncDashboardGridLayout rebuilds className wholesale and dropped packed-masonry, so any settings refresh — including the one behind a window resize — left the categories as bare flex children of a row with no columns in it

Config

  • Fix
    the location memory was written only on the exits config knows about

    the header's health, inbox and page buttons switch view around it. restoreConfigHash now saves on every move inside config and setActiveView stamps it on the way out. The TTL is 5 minutes (DashboardConfig and DashboardConfigLoader both), counted from leaving rather than from the last click inside.

  • New
    type: 'action' panel controls with bindPanelActions, used for Turn spreading off everywhere

    NEW_THIS_RELEASE is the one place naming where the twinkle points, drawn on the section, the sub-tab and the panel.

  • New
    #category-context-menu sizes to its content (`width

    max-content, capped at 24rem). The shared .move-popover cap is for the move/tag/delete pickers; at 16rem the widest row here needed 274px and got 237, so the Shift+W` chip was trimmed away — and the French label is half again as long.

Config → Bookmarks

  • New
    the section gets the sub-tab strip five others already have

    List and Settings. The nine settings sat after the list — fifty rows down by default and up to five hundred as the infinite scroll loads more, which also rules out jumping to the bottom of a list whose bottom moves as you approach it. Registered in SUB_TABS, SUB_TAB_STATE, SUB_TAB_ATTR and SUB_TAB_SECTION, so the deep link, the remembered location and the arrow-key walk come for free; handleOverviewGo accepts bmTab.

Views

  • New
    Health, Inbox and Config → Bookmarks draw one card from feed-row.css instead of three copies

    The rule was written out in health-view.css, dashboard-inbox.css and config-view.css and the copies had drifted into being byte-identical — one design, three places to change it, and no way to tell whether a difference was meant. What genuinely differs is a modifier: feed-row--with-select for Health's checkbox column, and the coloured left edge each view uses for its own state, including modern layout's inset redraw of it. Classic layout also gains the row focus ring only modern had.

  • New
    the shape the three views disagreed on is settled

    Inbox rounded its filter pills and buttons where Health squared them off; rounded won. Config → Bookmarks reads as a view rather than a settings panel — a header with a count, the search box sized like Health's, and tiles matching Health's without the stripe.

Discoverability

  • New
    spread-notice.js (a NoticeCard) and spread-tutorial.js, a four-step AppModal walkthrough in the shape of the inbox and health tours, reachable afterwards from Help → Pages & categories
  • Fix
    NoticeCard bound an action with querySelector, and a card naming its × through dismissName puts that attribute on the × as well

    The × comes first, so it took the handler and the button sharing its name got none: the side rail's No thanks had been dead since the cards were unified.

Only docs and tests changed in this release.

v1.0.4 A review pass over the bookmark grid and the menus around it, in five rounds: correctness first, then consistency between routes that do the same thing, then accessibility, then performance, then cleanup. +6 14 fix

A review pass over the bookmark grid and the menus around it, in five rounds: correctness first, then consistency between routes that do the same thing, then accessibility, then performance, then cleanup. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

The grid

  • Fix
    repaintBookmarkMutationSurfaces passed `incremental

    false, the one flag canAttemptDataPatch refuses outright, so every add, edit, delete, move and tag change tore down the whole grid — every DragReorder instance, the scroll offset and the focused row — for what is usually one changed row. The incremental path's own guards decide now: canAttemptDataPatch still bails on a layout-settings change and categoryStructureMatches` on a category added, removed or reordered.

  • New
    the scroll offset is stored per page in _pageScrollPositions and consumed on return

    Consumed, not kept: takeRememberedScroll deletes the entry, so a later deliberate visit still starts at the top.

  • Fix
    the incremental renderer built a category's empty state without the + bookmark button createCategoryElement includes
  • Fix
    rows are built at tabIndex = -1 for the roving tab stop and KeyboardNavigation hands one of them a 0 only after walking the grid, which a render does not do — so Tab skipped the grid entirely from first paint. syncBookmarkGridA11y guarantees exactly one stop now, on the row currentIndex points at rather than on row 0, which would walk the tab position away from the user on every repaint

Selecting several bookmarks

  • New
    deleteSelected offers an undo toast for 8s, restoring in ascending index order (each splice shifts what follows) and dropping the redundant trash entries afterwards via dropRestoredTrashEntries
  • Fix
    a failed save left the rows spliced out of the model and the selection cleared, then returned silently

    Both are restored and showErrorNotification is called.

  • Fix
    the toolbar was prepended into #dashboard-layout, which carries role="grid"

    a role="toolbar" among rows and rowgroups is invalid. It also rendered as a 90×278 vertical strip, because the grid is a flex row and width: 100% had nothing to fill. Inserted before the grid instead: full width, 44px tall, still sticky.

  • Fix
    the tags popover bound no scroll or resize handler and drifted away from its anchor

    It reuses the shared reposition and outside-close helpers now.

Search

  • New
    SearchComponent.FILTER_KEYS replaces three hardcoded four-item lists

    opened: and added: parsed and filtered correctly but were absent from getFilterHintItems, unoffered as a prefix, and unrecognised by _isCompleteFilterQuery, so the completion list kept firing over real results. Their values are offered the way status values are, with never only under opened:.

Tag filters

  • Fix
    updateTagFilterIndicator had been reduced to a teardown that emptied #tag-filter-indicator on every call, leaving the header element and its CSS doing nothing. It carries the active tags and the match count now, and hides itself while the in-grid banner is on screen so the chips are not shown twice. renderTagFilterBanner gained withToolbar for that

Menus and popovers

  • Fix
    resolveRowBookmark fell back to the URL for rows with no page-local index and searched the current page first

    The same URL legitimately sits on more than one page, so a row belonging to another page resolved to the wrong bookmark before delete ever saw it. It matches on the row's visible label now; list order only decides when nothing distinguishes the candidates. Fixed in both copies — dashboard-bookmark-interactions-loader.js keeps its own, and that is the one that runs on the first right-click of a session.

  • Fix
    _persistBookmarkField swallowed every error and returned nothing while all three pin routes flipped pinned themselves

    It applies the change (synchronously, before its first await, so the palette label still updates), reverts on failure, surfaces an error and returns a boolean; the callers no longer flip anything.

  • Fix
    the Delete key went through AppModal while Shift+D and the context menu used the anchored popover

    All three use the popover now. The modal stays for the inline editor, whose row is a form at that moment, and for a multi-row selection.

  • Fix
    one shared _bindActionPopoverOutsideClose for Move, Delete, Tag and the multi-select tags popover

    it also closes on an outside contextmenu, and matches the anchor by containment rather than identity.

  • Fix
    _focusActionPopoverItem picks its pattern from the container's role

    aria-activedescendant with focus on the box for role="listbox", roving tabindex for menus. The tag popover's second capture-phase keydown listener is removed — document capture runs first and every branch calls stopImmediatePropagation, so it never ran.

  • New
    the check-mode submenu entry sets aria-expanded, opens with ArrowRight and closes with ArrowLeft, matching the Escape path that already existed
  • New
    the category menu shows F2 and Delete as aria-hidden chips

    "Add category" gets none: it is a held c, and a chip would promise a tap that goes to the shortcut search.

  • New
    the category sort button opens on ArrowDown, which aria-haspopup="menu" already promised
  • Fix
    _restoreActionPopoverFocus fell back to focusing a detached anchor, a no-op that left focus on <body>

    It falls through to the first row still on the grid.

Reduced motion

  • Fix
    dashboard.css overrode four selectors with `animation

    none !important, contradicting reduced-motion.css, which uses 0.01ms precisely so animationend still fires. bookmark-copy-flash and bookmark-pulse stayed on the row for the rest of the session. The 320ms wait before a cross-page move is skipped under reduced motion (ANIM.BOOKMARK_MOVE_OUT, prefersReducedMotion()`).

Only docs and tests changed in this release.

v1.0.3 One theme across most of it: openCount, lastOpened, createdAt, updatedAt and tags were written on every path, fed the built-in features, and reached almost none of the ones the user drives. +15 5 fix

One theme across most of it: openCount, lastOpened, createdAt, updatedAt and tags were written on every path, fed the built-in features, and reached almost none of the ones the user drives. Plus settings for Config → Bookmarks, which had none.

Config

  • New
    the remembered config location applies on every exit and every way back in, expiring after 15 minutes (CONFIG_LAST_TTL_MS, stamped on the way out)

    It was saved only when leaving via Shift+H or Shift+I and cleared on every other exit, and resolveConfigOpenTarget additionally required activeView to be health or inbox — so the common route, Escape out and Shift+S back in, always landed on Overview. clearLastConfigLocation has no callers left and is removed. The expiry is duplicated in dashboard-config-loader.js, which reads the same entry on a cold load before the module exists; an entry with no savedAt predates the expiry and is treated as stale.

Config → Bookmarks settings

  • New
    ten settings, all previously constants

    stored sort (configBookmarksSort), rows per load step, and the availability, pin and category a quick-added bookmark starts with; the interval a bookmark gets when switched to Monitor, including in bulk; thresholds for confirming a delete and a bulk icon refresh; the "not opened in N days" figure, which also drives the cleanup score; and the archive service template.

  • New
    clampBookmarkSettings enforces every range server-side rather than leaving it to the controls, since the API is reachable without the browser

    The archive template must contain {url} and start with http, so it can never become a javascript: URL handed to window.open.

  • Fix
    opening a bookmark from Config now respects openInNewTab

    The setting existed and the grid honoured it; this path forced a new tab regardless.

Reaching the data

  • New
    opened: and added: in the search parser, matched by matchesAgeFilter against today/week/month/year, plus never for opened:

    An unrecognised word filters nothing rather than everything, which is the safer way round for a typo.

  • New
    custom collection rules gain pinned, untagged, notOpenedDays and changedDays

    valuelessRuleFields keeps pinned and untagged without a value, so the server no longer drops them as half-filled. changedDays is the first reader updatedAt has ever had on the dashboard.

  • New
    a Recently added smart collection on createdAt, off by default, with its own limit and page scope

    The other four all key on lastOpened or openCount, so "what did I just add" was unanswerable.

  • New
    previewDesc joins the search haystack, scored below the note

    the site's words rather than the user's.

  • New
    drift reaches the dashboard header badge in the warning tier

    A drifted link still returns 200, which is exactly why it needed a human.

Grid

  • New
    tag chips on rows, off by default, capped at a configurable two with the rest collapsing into +N

    Rendered inside .bookmark-link rather than as a column: it is a subgrid whose columns align across every category, so an extra column would shift every row. Verified by measuring the shortcut column before and after — identical to the pixel, and pinned as a test.

  • New
    createSortControls rebuilt as one active button plus a ⋯ menu

    Four buttons per header, repeated per category, took more width than the bookmark names; the strip goes from ~90px to 19px, or 58px once something is sorted.

  • New
    two sort modes, added and opens
  • Fix
    the grid's recent mode sorted by lastOpened while Config used the same words for createdAt

    Renamed to opened; normalizeSortMode still accepts the old value so stored categories keep working.

Keyboard and pointer

  • New
    Shift+P pin, Shift+S share, Shift+R reveal in Health, t filter to the row's tag

    Each delegates to the existing implementation — _persistBookmarkField, shareBookmark, revealInHealth, toggleTagFilter — rather than adding a second path that could drift.

  • New
    pin gains a right-click entry

    It had Shift+P and :pin but no pointer route at all from the grid, while every other one-bit row action had one.

  • Fix
    Ctrl/Cmd+Enter opens in a new tab for that press alone

    selectCurrentElement fired a bare .click(), which constructs no MouseEvent and carries no modifier, so the keyboard had only the standing openInNewTab preference.

Inbox

  • Fix
    triage swallowed every key but Escape

    Its guard asked dash.isModalOpen(), which counts the triage overlay itself, so the overlay blocked its own keyboard. Now asks isLayeredModalOpen() — whether something sits over triage. advance() was correct all along; nothing called it. Reported earlier and not reproducible then; the repro is a seeded queue of three and two presses of j.

  • New
    a seven-step one-time tour, fetched on demand rather than with the module

    the inbox loads during bootstrap for the unread badge, so riding along would cost every session that never opens the view. Guards and structure mirror health-tutorial.js.

  • Fix
    resetOnboarding now calls clearSeenTips()

    It only cleared onboardingCompleted while its own dialog promised to replay "the welcome tour and tips" — those ids live in discoverabilityState.seenTips, which it never touched, so no tour or tip had ever come back. tipsNotBefore is cleared with them; seenSettingPromos is deliberately left alone.

Config → Help

  • New
    a fifth panel under Help → Inbox describing the one-time tour, and a matching entry in the help search index

Only docs and tests changed in this release.

v1.0.2 A repair release for the config view, from a full audit of it. +5 13 fix

A repair release for the config view, from a full audit of it. Flagged hideFromModal in index.json like v1.0.1, so it does not reopen the What's new modal.

Data integrity

  • Fix
    ensureCategoryOnPage turned a failed GET into a one-item POST that replaced every category on the page

    Proven end to end: five categories in, one out, no error shown. SaveCategoriesByPage's guard cannot catch it, since it only rejects a zero-length list. Now throws rather than degrading.

  • Fix
    loadFinders and loadCategoriesEditor set a _xLoadFailed flag instead of []

    saveFinders and saveCategories refuse to write while it is set.

  • Fix
    saveCategories returns whether it saved and takes the page id as an argument, captured by each caller at edit time

    It swallowed the error and returned undefined either way, so the delete flow acted on a 409 as if it had worked — trash entry, undo toast and all. The page picker reassigns _catPageId synchronously, so a save in flight could also land on the wrong page.

  • Fix
    SaveSettings reports dropped collections in the response instead of discarding them behind {"status":"success"}

    Surfaced when leaving the Collections tab, not per save: a half-filled row is the normal state while typing.

  • Fix
    publishConfigSync added to dashboard-config-sync.js

    The listener, the pending-marker drain and four specs all existed; nothing ever published, so a second tab stayed stale until reloaded by hand. The specs write the markers themselves, so they passed either way.

Config

  • Fix
    refreshAllFavicons posted a body-less request to /api/bookmarks/prefetch-icons, which is per-page and decodes the body first, so it answered 400 every time

    Routed through ConfigFaviconPrefetch, as search-commands.js and dashboard-quickstart.js already did.

  • Fix
    the prefetch overlay drops pointer-events on completion

    It covers the viewport at z-index: 12000 and stayed up through the 900ms completion pause and the reloads after it, so the page read "Icons updated" while every click landed on the overlay. Found via a spec that timed out clicking Save; elementFromPoint over the button returned the overlay.

  • Fix
    guardUniqueName rejects empty and over-long names

    It only ever checked duplicates and delegated emptiness to callers that never picked it up, so a cleared name saved as "" and two emptied names stopped colliding, since "" is never taken. Server clamps to the same 60 characters via clampEntityName (rune-wise, through truncateRunes), because the API is reachable without the browser.

  • New
    checkedAt, nextBackupAt and totalKept are rendered

    All three were shipped by the server and read by nothing; totalKept was silently excluded from the inbox conversion sum while the panel above showed it as its own tile.

  • Fix
    four config.* keys were missing from every locale (addBookmarkBtn, bookmarkNotFound, clearBookmarkFilters, saved)

Accessibility

  • Fix
    labelSettingsControls() names every schema-rendered control after the panel is drawn

    Labels render as <span class="config-field-label">, not <label for>, so selects and number inputs across Behavior and much of Appearance had no accessible name. Done in one pass rather than at ~30 render sites that would drift. Ranges also get aria-valuetext, since 0.85 is not what the UI shows.

  • Fix
    captureControlPanelFocus() restores focus and caret across repaintActiveControlPanels

    Controls bind on change, which fires while the control still has focus, and the repaint replaces the whole body — so the next Tab started from the top of the page. repaintTagsBody already did this, with a comment explaining the hazard.

  • Fix
    bindSubTabStrip re-focuses on the next frame rather than testing target.isConnected immediately

    Appearance activates through render(), which had not run yet, so the branch was skipped and focus landed on <body> — one ArrowRight killed every press after it.

  • Fix
    both hand-rolled confirm dialogs handle Tab through FocusTrapUtils.trapTabKey

    They declared aria-modal="true" and only handled Escape, so focus wandered into the page behind, including on Reset all data.

Import and export

  • New
    theme import (importThemeFromFile, normalizeImportedTheme), reusing Duplicate's id and naming logic so it lands as a new theme and cannot overwrite the palette on screen. A JSON file with no colour values is refused
  • New
    CSV import (importBookmarksCSV, parseBookmarksCSV)

    Hand-written parser rather than split(','): the export quotes every field so a note can hold a comma, a doubled quote or a newline. Columns are matched by header, so reordering them in a spreadsheet still imports. Rows go through /api/bookmarks/import-browser, keeping URL de-duplication server-side.

  • New
    trash search across name, URL, tag, category and origin page, plus tick boxes and a bulk restore that runs per item so one failure cannot take the batch with it

    Select-all covers what the search shows.

  • New
    SavedSearch added to Settings, normalized by normalizeSavedSearches (trimmed, incomplete entries dropped, capped at ten)

    Saved searches lived only in localStorage, so they were in no ZIP backup; anything left there is migrated on first read.

Only docs and tests changed in this release.

v1.0.1 A patch release on top of v1.0.0. +4 2 fix

A patch release on top of v1.0.0. Recorded here and versioned normally, but flagged hideFromModal in index.json so it does not reopen the What's new modal in front of users who have just read the 1.0 entry — see v2026.09.09.1 for the same treatment.

Health

  • New
    the collection trend chart moved out of .health-view-toolbar-actions, where it was a `flex

    1 1 6rem track competing with the button row for space, into a new .health-view-note-row shared with the filter note. Reserving a column beside the buttons via padding-right` was tried first and reverted: it stranded whichever button ran out of room on a line of its own.

  • New
    the chart gained a midpoint gridline, an endpoint dot, and a 100% axis label rendered outside the SVG

    The label sits outside because preserveAspectRatio="none" stretches the viewBox to the layout box and would distort any type inside it. Only the ceiling is labelled; a 50% label was added and removed as one number too many.

  • New
    per-day hover readout

    Hit zones are absolutely positioned <button> elements sized in CSS percentages rather than SVG geometry, for the same preserveAspectRatio reason: coordinates inside the viewBox drift away from where the pointer actually is. trendPointLabel() reads HealthTrendPoint.t (Unix ms), not a d/day field — an earlier draft assumed the latter and produced empty labels. A null reading renders "no reading" rather than 0%.

  • New
    showTrendExplainer() behind an ℹ beside the chart, kept separate from showHealthExplainer() so the fixed-axis and gap rationale is not buried in the view-wide text

Update check

  • Fix
    fetchGitHubLatestRelease read GitHub's /releases/latest, which resolves "latest" by published_at rather than by version

    A patch published on the calendar line after v1.0.0 would be named there and then correctly rejected by compareReleaseTags, so a genuinely newer release was never announced in the modal or in Config → Overview. Now reads the release listing and orders it with compareReleaseTags, falling back to /releases/latest when the listing cannot be read.

  • Fix
    the listing URL is derived from githubLatestReleaseURL via releaseListURL() rather than declared as a second package var

    As two independent vars, TestFetchGitHubLatestRelease stubbed one and reached the real api.github.com with the other, passing against live data.

Only docs and tests changed in this release.

v1.0.0 The first release under semantic versioning, and deliberate milestone: after a long run of bug fixing and consolidation has left the app feeling finished and stable rather than in flux. +14 32 fix

The first release under semantic versioning, and deliberate milestone: after a long run of bug fixing and consolidation has left the app feeling finished and stable rather than in flux. From here 1.x.0 carries features and 1.0.x carries fixes; see v2026.09.09.3 for the scheme change itself, which shipped the comparison logic ahead of this tag.

Data integrity

  • Fix
    _moveBookmarkToPage did a double whole-list read-modify-write

    GET both pages, splice/push in memory, POST both back. A concurrent write to either page was clobbered, and a source save landing while the target save failed lost the bookmark from both. Now uses the single-item POST /api/bookmarks/add + DELETE /api/bookmarks endpoints, each atomic under the store lock.

  • Fix
    bulkMoveTagFilterToPage had the same shape for a whole batch

    Converted to per-item add+delete via Promise.allSettled, with a partial-failure toast.

  • Fix
    deleteRemoteBookmarkInline read the whole source page, spliced, and POSTed it back, racing any concurrent write

    Now uses the single-item DELETE endpoint. saveRemoteBookmarkEdit deliberately left as-is: no single-item update endpoint exists, and emulating one as delete+add would move the bookmark to the end of its page.

  • Fix
    SaveCategoriesByPage returned nil for an empty-list save while bookmarks still referenced a category, changing nothing

    Now returns ErrCategoriesStillReferenced, mapped to 409 by respondCategoriesSaveError.

  • Fix
    category rename without originalId fell back to matching by array position, so dropping a middle category reassigned later categories' bookmarks

    Positional fallback removed.

  • Fix
    AddInboxLink trimmed at capacity after appending, discarding an item with an older AddedAt while returning success

    Now uses trimInboxItemsKeeping plus a survival check, mirroring RestoreInboxLink.

  • Fix
    DeleteBookmarkFromPage skipped read-cache invalidation
  • Fix
    concurrent page/category creation could clobber each other
  • Fix
    fetchBookmarkPreview cached error pages as valid previews

API and validation

  • Fix
    PUT /api/inbox skipped every validation POST performs

    no validateBookmarkURL, no sanitizeBookmarkIcon. It was the one route that would store a javascript: URL or a private address under allowLocalBookmarks:false, and the only path where a client could write Icon.

  • Fix
    an empty inbox URL returned 500 for a client error

    validateBookmarkURL intentionally permits empty strings (bookmarks may have none), so the check belongs in the handler.

  • Fix
    GetCategories/SaveCategories accepted a nonexistent page, materialising bookmarks-N.json as a side effect

    Both now 404 via pageExists.

  • Fix
    GetBookmarks silently returned 200 [] for a missing page/all param
  • Fix
    bookmark Name/Category/Note were never trimmed server-side, unlike Tags/Icon
  • New
    POST /api/categories?dryRun=1 reports what a category save would do — which bookmarks move, which are orphaned, which submitted categories carry no originalId — and writes nothing. Shares buildCategoryRemap with the real save so the preview cannot drift from it
  • New
    inbox text fields are bounded (clampInboxLinkFields), applied on add, patch and restore

    inbox.json is rewritten whole on every mutation, so an unbounded field is paid for by every later request.

  • Fix
    PATCH /api/inbox stored readAt verbatim, including negative and far-future values, while snoozedUntil directly above it was carefully clamped
  • New
    PATCH /api/inbox accepts tags (a pointer, so clearing is expressible)

Inbox

  • New
    tags are rendered as filter chips, editable from the row menu, matched by search, and included in both exports

    InboxLink.Tags had existed and been normalised since the field was added, with no UI at all.

  • New
    a Stats panel reads /api/inbox-stats, previously consumed only by the config view

    Promote rate is measured against triaged (promoted + deleted) rather than added.

  • New
    bulk promote, bulk open, bulk copy links, Shift+click and Shift+arrow range selection, Ctrl/Cmd+A select-all
  • New
    the right-click menu carries the inbox's own actions rather than the bookmark menu's
  • New
    R re-fetches the feed, wiring up loadAndRender({refresh}), which had no caller
  • Fix
    a failed load rendered the empty state

    now a distinct panel with a Retry button, matching the health view.

  • Fix
    the keyboard cursor is no longer dropped after a delete
  • Fix
    Escape and view-level keys ran below the empty-list guard, so clearing ticks was impossible exactly when a filter hid them
  • Fix
    a consumed ?ib_id= deep link kept clearing searchQuery/domainFilter on every later render
  • Fix
    triage's delete ignored deleteItemWithUndo's return value

    bulkSnooze discarded its results entirely; bulkDelete reported partial success as success and snapshotted survivors for undo.

  • Fix
    capacity eviction is reported to the client, and evicted items' icons are cleaned up (previously only the explicit DELETE path called removeUnusedIconFile)
  • New
    a polite live region announces the row count after each render

Health

  • New
    an orphaned-category issue type

    bookmarks whose Category id matches no category on their page. Detect-only, following the shortcut-conflict precedent. Category save and browser import now invalidate the health report cache, which they did not need to before.

  • Fix
    header badge polling moved from a fixed 60s interval to the server's cache TTL with exponential backoff, and no longer double-fetches on tab return
  • New
    header restructured to two rows matching .inbox-header

    the trend chart moved into the toolbar.

Dashboard

  • Fix
    _smartCollectionFilterNeedsCrossPageData had been collapsed into !_isSmartCollectionPageAllowed in an earlier commit

    the two answer different questions and diverge on the default empty scope, silently disabling cross-page loading. Both restored, sharing only the id normalisation.

  • Fix
    the staleness fingerprint omitted pinned, checkStatus, icon and note
  • Fix
    saveSettings swallowed its error without logging
  • Fix
    the translation-fallback pattern never fell back on a missing key
  • Fix
    multi-select Clear referenced a nonexistent keyboardNav property
  • Fix
    smart collection headers could be renamed via long-press/double-click
  • Fix
    copySelectedLinks had no execCommand fallback for plain-HTTP installs
  • Fix
    the inline-edit save hint always showed Ctrl, never Cmd on macOS
  • Fix
    multi-select Move/Tags buttons lacked aria-haspopup/aria-expanded

    the recent-bookmarks skeleton lacked aria-busy.

  • Fix
    the double /api/data-revision round-trip on tab refocus is debounced
  • New
    bulk tag-filter delete offers an undo toast
  • New
    _applyLoadedPageData's full-container view identity moved into one FULL_CONTAINER_VIEWS table instead of three hand-copied checks
  • New
    NoticeCard is the shared bottom-left card

    the analytics and side-rail notices were rewritten onto it. The push/outage notice was removed entirely.

  • Changed
    noteDataMutation(pageID) scopes read-cache invalidation to the page a write touched

Docs

  • New
    Semantic versions

    since v1.0.0 (13 August 2026), vMAJOR.MINOR.PATCH: a minor release brings new features, a patch release only fixes. A fourth number (v1.11.1.1) has been used for a hotfix.

  • New
    Calendar versions

    before that, v2026.MM.P (year, month, patch). Those releases are in the changelog archive.

  • New
    In-app token

    DASHBOARD_RELEASE in whats-new-stub.js tracks the dashboard's "seen" state separately from git tags.

Only docs and tests changed in this release.

Releases before v1.0.0, on the old calendar numbering, are in the archive on GitHub. This page is read from CHANGELOG.md, 26 minutes ago.