What shipped recently

Every release, in plain language.

Dashboard blocks
v2.4.0Jul 14, 2026
- addedTwelve dashboard and data-table sections
- addedKeyboard navigation across every table block
- changedSidebar collapses below 1024px instead of 768px
Accessibility pass
v2.3.1Jun 2, 2026
- fixedFocus ring clipped inside overflow containers
- fixedMarquee ignored prefers-reduced-motion
Theming
v2.3.0May 19, 2026
- addedToken generator with contrast validation
- changedAll blocks now read semantic colour tokens

Release Timeline

A dated changelog on a vertical rail with added/changed/fixed tags and machine-readable <time> values.

Content & Blog145 linesNo deps13 Sept

Roadmap

What is done, what is being built, and what is next.

Shipped

2

Marketing sections
Heroes, pricing, FAQ, footers.
Dark mode tokens
Every block reads semantic colours.

In progress

2

Dashboard blocksQ3 2026
Shells, tables, settings.
CLI installQ3 2026
Add a block straight to your repo.

Planned

3

Full page layoutsQ4 2026
Composed screens, not sections.
Starter templatesQ4 2026
Multi-page projects, ready to deploy.
Vue and Svelte ports2027

Public Roadmap Columns

Shipped / in progress / planned in three columns, with status carried by icon as well as colour.

Content & Blog122 lines1 dep2 Sept

From the blog

Engineering

How we run incident reviews nobody dreads

Blameless is easy to say and hard to schedule. The template, the timebox, and the one question we ask before anyone opens a dashboard.

Priya RamanJul 8, 20269 min read

Blog Index Grid

A featured post at full width above a card grid, with drawn covers built from tokens — a blog index with no image pipeline and no broken-thumbnail state.

Content & Blog188 lines1 dep

What changed for them

Three teams, three different problems, one number each that a colleague can check.

A grid of case-study cards that lead with the metric rather than the company name, each one linking out to the full write-up — the block a customer-stories section or a home page needed and only had a full case-study page for.

Content & Blog136 lines1 dep

Engineering

The day we deleted 40,000 lines of feature flags

Flags are borrowed complexity — this is what it cost to pay ours back, and the two rules that keep the debt from growing again.

Priya Raman

Staff Engineer · July 21, 2026 · 12 min read

The pull request was titled “remove stale flags, part 1 of 8” and it deleted more code than the previous quarter had added. Our flag service listed 312 active flags; production telemetry showed 41 of them had evaluated to the same value for every user since at least January. The rest were split roughly evenly between experiments nobody remembered starting and kill switches for services we had already decommissioned.

“A feature flag is a loan. The interest is every engineer who has to reason about both branches forever.”

Article Header & Byline

Kicker, headline, standfirst, byline and share row, with the opening prose and a pull quote included — the type scale of a post, decided once instead of per-article.

Content & Blog171 lines1 dep2 Sept

The people building it

A small team spread across four time zones, shipping every week since 2023.

Priya Raghavan
Co-founder & CEO
Previously led platform at a payments unicorn; still reviews PRs.
Marcus Okafor
Co-founder & CTO
Wrote the first commit in March 2023 and the incident runbook the week after.
Elena Sokolova
Head of Design
Believes every empty state deserves as much care as the dashboard.
Tom Whitfield
Staff Engineer
Owns the sync engine; measures success in p99s, not features.
Aisha Diallo
Product Manager
Turns forty support tickets a week into a roadmap the team believes in.
Daniel Kim
Developer Advocate
If you found us through a conference talk in 2026, it was probably his.

Team Grid

An about-page team section on initials avatars rather than photos, so shipping it never waits on headshots and there is no broken-image state to design.

Content & Blog166 lines1 dep

Open roles

We’re hiring across three teams. Every role lists the real salary range — no “competitive”.

Engineering3 openings

Design2 openings

Go-to-market2 openings

Nothing that fits? We read every speculative application — jobs@hoverlab.dev.

Careers Openings Board

Openings grouped by department with location, type and salary on every row — candidates self-select by craft first, and a flat list makes them scan for it.

Content & Blog186 lines1 dep10 Sept

Docs navigation

Authentication

Every request to the Acme API is authenticated with a bearer token. This page covers creating a key, storing it safely, and rotating it without downtime.

Acme issues two kinds of keys. Secret keys (prefixed sk_live_) can read and write everything in your project and must only ever live on a server. Publishable keys (prefixed pk_live_) are safe to ship in a browser bundle and can only create client sessions.

Keys are scoped to a project, not to your account. Deleting a project revokes its keys immediately; removing a teammate does not, so treat offboarding as a reason to rotate.

Creating an API key

Create a key from the dashboard under Settings → API keys, then pass it as a bearer token on every request:

curl https://api.acme.dev/v1/projects \
  -H "Authorization: Bearer $ACME_API_KEY"

Note: the full secret is shown once, at creation. Acme stores only a hash, so a lost key cannot be recovered — it can only be rotated.

Rotating keys

Rotation is overlap, not replacement: create the new key, deploy it everywhere, and only then revoke the old one. Both keys stay valid during the window, so a slow rollout never turns into an outage.

Three-Column Docs Frame

Sidebar, article and on-this-page rail — each column answers a different question, and they collapse on mobile in the order that keeps the article alive.

Content & Blog290 lines1 dep13 Sept

GET/v1/projects/{project_id}/deployments

List the deployments for a project, newest first.

Parameters

Name	Type	Required	Description
project_id	string	Required	The project to list deployments for. Passed in the path.
status	string	Optional	Filter by state: building, ready or failed.
limit	integer	Optional	Page size, 1–100. Defaults to 20.
cursor	string	Optional	Opaque cursor from a previous page’s next_cursor.

Request

curl "https://api.acme.dev/v1/projects/prj_8kq2/deployments?limit=2" \
  -H "Authorization: Bearer $ACME_API_KEY"

Response200 OK

{
  "data": [
    {
      "id": "dep_9f2c1a",
      "status": "ready",
      "branch": "main",
      "created_at": "2026-08-12T09:41:00Z"
    },
    {
      "id": "dep_8e1b0d",
      "status": "failed",
      "branch": "fix/session-ttl",
      "created_at": "2026-08-11T17:03:12Z"
    }
  ],
  "next_cursor": "dep_7d0a9c"
}

API Endpoint Reference

Method badge, path, parameter table and a request/response pair kept side by side — an example request whose response is a scroll away gets pasted blind.

Content & Blog237 lines1 dep2 Sept

Package Manager Code Tabs

One install command behind npm/pnpm/yarn/bun tabs with a working copy button — every reader uses exactly one package manager, so showing all four wastes three lines.

Content & Blog152 lines1 dep11 Sept

Aisling Moreau

Principal engineer — platform, performance and the unglamorous parts

Print or save as PDF

Ten years building systems that other engineers depend on, mostly by removing things. I am at my best on a team that has outgrown its first architecture and has to keep shipping while it changes. Looking for a principal or staff role where the hard problem is technical rather than political.

Experience

Principal Engineer, Platform · Northwind
Mar 2023 — Present · Remote
Series B logistics platform, 40 engineers, one Rails monolith and four Go services.
- Cut p95 checkout latency from 2.4s to 610ms by deleting a caching layer rather than adding one — the invalidation cost more than the reads saved.
- Led the migration off a managed search product onto Postgres full-text, against a hard contract-expiry date. Saved $310k a year with no change to result quality anyone could measure.
- Wrote the on-call handbook and cut pages per engineer per week from 11 to 2, mostly by deleting alerts nobody had ever acted on.
Senior Software Engineer · Contoso Health
Jun 2019 — Feb 2023 · Dublin
Patient records for 60 clinics. Regulated, audited, and slow to change by design.
- Rebuilt the appointment booking flow to meet WCAG 2.1 AA before the deadline the procurement contract set. It passed audit first time, which nothing else that year did.
- Introduced contract tests between the scheduling service and three consumers, ending a class of release that broke a downstream team every quarter.
Software Engineer · Umbra Labs
Sep 2016 — May 2019 · Dublin
- Second engineer. Built the billing integration that the company ran on unchanged for six years.

Skills

TypeScript · Go · Postgres · React · Next.js · Terraform · OpenTelemetry · WCAG 2.2 AA · Incident command

Education

BA (Mod) Computer Science — Trinity College Dublin — First Class Honours2012 — 2016

Selected writing and talks

“The cache we deleted” — SRECon EMEA, main track2025
“Accessibility as a procurement requirement” — Write the Docs2024

Résumé Document

A CV as a document rather than a timeline of cards — one column, dates on the end edge, and a print layer that puts it on paper without a separate PDF to keep in step.

Content & Blog347 lines1 dep

Episode 3

4:18 / 12:04

Profiling, end to end

Where the time actually goes

48,219 views · Episode 3 of 7 · Published 4 March

We take a page that feels slow and find out what is actually slow about it — with a profiler open the whole time, and no guessing. The fix at the end is two lines; finding it is the other eleven minutes.

Video Player Shell

The watch screen with no playback in it: a ratio-locked stage, a control bar drawn down to the buffered layer, and an up-next rail. Drop a video element in and wire your own player.

Content & Blog327 lines1 dep