Keyboard-first dashboards

Analytics dashboards are a tool you visit dozens of times a day in small bursts: check a number, compare a page, close the tab. At that cadence, every trip through the sidebar is a tax. This note is about three small things I've built into the Tracely app shell to make those bursts fast — a command palette, go-to key sequences, and print support that doesn't need a PDF engine.

The command palette

Press ⌘K on macOS (or Ctrl+K on Windows and Linux) anywhere in the app and a palette opens: type to filter destinations, arrow keys to move, Enter to go, Esc to close. Navigation uses Livewire's client-side navigation when it's available, so jumping between dashboards doesn't pay for a full page load.

There's nothing novel about a command palette in 2026 — that's rather the point. It's become the way people who live in software expect to move around, and an analytics tool is exactly the kind of software people live in. What matters is that it's in the app shell, so it works from every authenticated screen, not just the ones I remembered to wire it into.

Go-to sequences

For the places you visit constantly, even the palette is one step too many. So the shell also supports two-key go-to sequences, Gmail-style: press g, then a destination key.

• g s — All sites
• g a — Account

And with a site selected:

• g o — Overview
• g l — Live
• g r — Reports
• g e — Events

The sequences only fire when focus is not in an input, textarea, select, or contenteditable region — typing "gs" into a filter field navigates you nowhere. That guard sounds obvious, but it's the difference between a shortcut system people trust and one they disable: the first time a key chord eats your half-typed search query, you stop believing the keyboard is safe.

The mnemonics are deliberately boring. Overview is o, Live is l, Reports is r, Events is e. If you can name the screen, you can guess the key, and a shortcut you can guess is a shortcut you'll actually use.

Print and save as PDF

The third piece looks unrelated but comes from the same instinct: respect the workflows people already have. Sooner or later, someone needs a dashboard out of the browser — a snapshot for a Monday meeting, a PDF for a client, a page for someone who wants paper.

The common answer is a server-side PDF engine: run headless Chrome or wkhtmltopdf somewhere, render the page, stream a file back. That's a heavy dependency and a whole category of operational failure — font issues, timeouts, one more process to babysit — for something browsers already do well. So Tracely has no server-side PDF engine at all. Instead, the dashboards are styled to print properly, and "Save as PDF" in the browser's print dialog does the rest.

Concretely:

• The authenticated app shell has a Print button in the sticky header (which hides itself in the printed output — a print button on paper being the classic tell of an afterthought).
• A print-only header appears above the content when printing: app name, the page title when the dashboard provides one, and the print date. That last one matters more than it looks — an undated analytics snapshot is a trivia card, not a document.
• Screen chrome disappears: sidebar, quota banner, impersonation banner, command palette, toasts.
• @media print rules in the app's CSS set @page margins, keep page breaks from landing inside rounded stat cards, and let tables break across pages sensibly.

The result is that any dashboard is also a decent document, for the cost of a stylesheet instead of a rendering service.

Why these three together

A palette, some key chords, and print CSS don't share an implementation, but they share a philosophy: the interface should meet the muscle memory people already have. Keyboard users get ⌘K and g o because that's how their other tools work; the person who needs a PDF gets the browser's own print dialog instead of a bespoke export flow. None of it is a headline feature, and none of it will ever be — but tools you use thirty times a day are made or broken by exactly this kind of thing.

More of what's in the dashboards themselves is on /features. Next up, back to the data side of the house — there's plenty still cooking there.