A year ago, a board in Tessera was a page you refreshed. Today every chart listens to the events behind it and redraws the moment they change, so the number on the wall is the number right now.
We rebuilt the query engine, the chart renderer and the way boards are shared. Most of it is invisible: queries run closer to your data, and only the bars that moved are drawn again. Read the release notes or start with the five-minute tour.
Boards now open in under a second for most teams, and the ones with a hundred charts no longer stall the tab.
Below is what changed, why we changed it and how to move your own boards across. Nothing breaks if you wait: old boards keep working until you open them in the new editor.
The live component, numbered part by part. Every measurement is read from it as it is drawn. Point at a row to outline its part, or at a part to find its row.
A marketing site with more pages than a header can list: products, resources and company pages grouped into a few sections, each with a line on what is behind it.
Sections people browse rather than search: an icon, a title and two lines help them pick the page before they open it.
Room to promote one thing per section, such as a release, an app or a video, beside the links rather than in a banner.
Headers that must also work on a phone, where the same sections fold into a sheet of accordions.
When not to use
An app’s own navigation between a handful of views. Use tabs or a sidebar; a panel that covers the page slows down frequent moves.
Commands or settings, such as Edit, Share or Delete. Use a menu button with role="menu"; these are links to pages.
Fewer than four pages per section. Use a simple dropdown list; a full-width panel for three links is mostly empty space.
Deep trees of pages. Use a sidebar or a site map; a mega menu holds one level under each section.
Under 760 px of site width the nav folds into a menu button, and a sheet lists the same items, with each section as an accordion of its links. The featured cards are left out of the sheet, so anything a card promotes should also be a link in one of the columns.
Either way it needs React 19 and a bundler that supports CSS Modules, such as Next.js or Vite. It has a dark colour scheme: it follows your page’s color-scheme, light unless the page sets one, or its colorScheme prop, with nothing to configure. Browsers without light-dark() show it light.
The header of Tessera, a made-up analytics product, over one of its blog posts. Products, Resources and Blog each drop a white panel the width of the site: columns captioned in small grey capitals, each link an outlined icon tile, a bold title and two grey lines, with a badge where there is news, and a tinted card on the right with a drawn picture, a glass play button and a full-width button. A soft band glides behind the link under the pointer and its tile lifts; the page underneath dims. Moving to another section morphs the panel’s height and slides its content the way the pointer went. The play button opens a small player. On a phone the nav folds into a menu button and a sheet of accordions. Light and dark.
The header’s items are data: plain links, and sections with columns of links and an optional featured card. Every section’s content is drawn once, as a pane in the panel, so moving between them only changes which pane is current.
The panes before the open one wait to its left and the ones after to its right. Opening another section slides the old pane out and the new one in from the side it came from, and the panel’s height follows the new pane: it is measured, and a ResizeObserver keeps it right when the text reflows.
Opening from closed fades the panel in without moving its height or its panes; only a switch between two open sections morphs, so the first open stays quick.
Hover intent: the pointer has to rest 140 ms on a trigger to open its panel, 60 ms to switch once one is open, and the panel waits 280 ms after the pointer leaves the header and panel before it closes. A click right after the pointer opened it keeps it open.
One band per panel sits behind the links. It moves to the link under the pointer or the focus with `translate`, `width` and `height` on a springy curve, and appears in place, with no flight, when it was hidden.
The featured pictures are SVG scenes drawn for each section. In the player their bars grow, their lines draw themselves and the cards drift, all CSS animations that Pause holds.
Under 760 px of site width, a container query swaps the nav for a menu button whose three bars turn into a cross; the sheet lists the same items, with the sections as accordions that open by animating `grid-template-rows`.
While on screen and untouched, a demo pointer opens Resources, glides across its links, switches to Products and then Blog, and closes; on a phone it opens the sheet and two sections. Any real input hands it over; it comes back after 8 s of quiet.
The header’s items: a link (id, label, href), or a section with columns of links (icon, title, text, optional badge) and an optional featured card (title, text, scene, cta, video).
brand
string
'Tessera'
The product’s name beside the mark, also used in the article under the header.
defaultState
MegaMenuState
—
Opens locked in a moment, with the demo off: the open section, the link under the pointer, the player, the phone’s sheet and its expanded section.
onNavigate
(target: NavTarget) => void
—
Called with the id, label and href of any link followed: in a panel, the header, the sheet or the page.
onOpenChange
(section: string | null) => void
—
Called with a section’s id when its panel opens, and with null when it closes.
onPlay
(featured: Featured) => void
—
Called when a featured card’s play button opens the player.
autoplay
boolean
true
While on screen and untouched, a demo pointer shows the main interactions. Any real input stops it.
colorScheme
'light' | 'dark' | 'system'
—
Light or dark colours, or the reader’s; without it, the page’s color-scheme.
Each section’s trigger is a button with aria-expanded and aria-controls, and its panel holds plain lists of links, each list labelled by its column’s caption, in the panel and in the phone’s sheet alike. There is no role="menu": these are links to pages, and screen readers keep their usual link commands. Panes not in view are inert.
Keyboard
Enter or Space toggles a section; ↓ opens it and moves to its first link.
← and → move along the header, Home and End to its ends.
In a panel, ↑ and ↓ walk the links, the play button and the card’s button; ↑ from the first goes back to the trigger.
Escape closes the panel and returns the focus to its trigger; tabbing out of the header and the panel closes it too.
Content on hover
Nothing needs hover: a click or a key opens every section. A panel the pointer opened stays while the pointer moves onto it and closes 280 ms after it leaves, so it can be read without chasing it. Escape anywhere on the page closes it without moving the pointer, and the focus stays where it was unless it was in the panel (WCAG 1.4.13, Content on hover or focus).
Announcements and motion
A polite live region says which section opened or closed, and which link was followed.
The player is a modal dialog: the focus moves into it, Tab stays inside, and closing it puts the focus back on the play button.
Under reduced motion nothing slides, glides or animates, and the demo pointer never plays.
Triggers are 36 px tall and links far taller, above the 24 × 24 px minimum (WCAG 2.5.8, AA).
Contrast
In both schemes, words reach 4.5:1 on the surface they sit on (WCAG 1.4.3), and the chevrons, the card button’s among them, reach 3:1 (WCAG 1.4.11). The painted pictures keep their own colours.
In this build
The sections follow the disclosure pattern for navigation: each trigger is a button with aria-expanded and aria-controls pointing at its pane, and the panes are lists of ordinary links labelled by their column’s caption. Panes not in view are inert.
Enter or Space toggles a section; ↓ opens it and moves to its first link; ← and → move along the header, Home and End to its ends. Inside a panel, ↑ and ↓ walk the links, the play button and the card’s button, and ↑ from the first goes back to the trigger.
Escape closes the panel and returns the focus to its trigger; tabbing out of the header and its panel, or pressing outside them, closes it too. A polite live region says which section opened or closed, and which link was followed.
The player is a modal dialog labelled by its title: the focus moves to its close button, Tab stays inside, and Escape or a press outside closes it and puts the focus back on the play button.
On a phone the menu button and each section’s row are disclosure buttons with aria-expanded; Escape closes the sheet. Every control shows a focus ring; under reduced motion nothing slides, glides or animates and the demo never plays. The demo pointer is decorative.
/* Mega menu (mega-menu.tsx): a marketing site's header in a browser window on a hatched stage. A section of the header drops a full-width panel of captioned columns and a featured card; the page under it dims. Under 760 px of site the nav folds into a menu button and a sheet. Colours are the tokens below, light-dark(light, dark) where the two differ: the component takes the color-scheme it inherits from the page, or the one its colorScheme prop sets (data-color-scheme). The featured pictures are painted scenes and keep their colours. Words reach 4.5:1 on their surface and the chevrons (--ink-4) 3:1, in both schemes. */.root {--stage: #f4f4f5;--hatch: #e6e6e9;--window: #fcfcfc;--window-edge: #e4e4e7;--surface: #ffffff;--surface-2: #f7f7f8;--band: #f4f4f5;--ink: #181d27;--ink-2: #535862;--ink-3: #717680;--ink-4: #8b8f98;--line: #e9eaeb;--edge: #d5d7da;--tile: #ffffff;
data.ts
// Copyright (c) 2026 Bruno Delorence. MIT License.importtype { IconName, SceneName } from'./glyphs';/* * What the header shows: plain links, and sections that open a panel of columns with a featured * card. The defaults are a made-up analytics product's site, Tessera. *//** One entry in a panel: an icon tile, a title, two lines on it and an optional badge. */exporttypeMenuLink = { id: string; title: string; text: string; icon: IconName; badge?: string; href?: string;};/** A captioned column of links. */exporttypeMenuColumn = { id: string; caption: string; links: MenuLink[] };/** The tinted card at the right of a panel; `video` puts a play button on its picture. */exporttypeFeatured = {
glyphs.tsx
// Copyright (c) 2026 Bruno Delorence. MIT License.'use client';import styles from'./mega-menu.module.css';/* * The drawings: line icons for the tiles, the header's small glyphs, the brand's pixel mark, and * the featured cards' pictures. The pictures are painted scenes, so they keep their colours in * both schemes; in the player their bars and lines move (classes in mega-menu.module.css). */exporttypeIconName = | 'book' | 'smile' | 'play' | 'code' | 'flag' | 'briefcase' | 'chat' | 'scale' | 'chart' | 'layout' | 'bolt'
demo-pointer.tsx
// Copyright (c) 2026 Bruno Delorence. MIT License.'use client';importtype { CSSProperties, Ref } from'react';/* * The demo's pointer, and the steps that move it. A demo is a script of awaited steps: wait, or * glide the pointer somewhere. Stopping the demo (the reader takes over, or it scrolls away) ends * the step in progress at once: its promise rejects, which ends the script right there, and the * pointer fades out. * * Each glide is a curved flight played by the Web Animations API, so nothing runs frame by frame. * The points of the flight are handed to whoever wants to move along with it. The arrow and the * hand are HTML boxes * that swap by their visibility: a change of style inside an SVG would lay the SVG out again. */exporttypePoint = { x: number; y: number };/** A glide's path and timing, for an animation that plays along with it. */exporttypeFlight = { points: Point[]; timing: KeyframeAnimationOptions };exporttypeDemo = {
use-autoplay.ts
// Copyright (c) 2026 Bruno Delorence. MIT License.'use client';import { useCallback, useEffect, useRef, useState } from'react';/* * When a demo may play on its own: while part of it is on screen and the tab is visible, never * under reduced motion, and not while the reader is using it. `take()` hands it to the reader; it * takes back over `idle` ms after their last input. */exportfunction useAutoplay<TextendsHTMLElement>(idle = 6000) {const ref = useRef<T>(null);const [visible, setVisible] = useState(false);const [reduced, setReduced] = useState(true);const [taken, setTaken] = useState(false);const timer = useRef(0);useEffect(() => {const element = ref.current;if (!element) return;let onScreen = false;const update = () => setVisible(onScreen && !document.hidden);const observer = newIntersectionObserver(