Skip to main content

Build note

ISR for low-friction publishing

How cached public routes and targeted revalidation keep build notes shippable without full redeploys.

June 5, 2026 · 1 min readAbout the author

Static marketing sites are simple until content changes daily.

Lebear ships with ISR on public routes so publish flows feel instant without rebuilding the entire app for one note edit.

The pattern

  • Public pages declare revalidate = 60.
  • Admin mutations call revalidatePath for affected routes.
  • Shell/header stays dynamic where session state matters.

Why it matters for builders

Honest build notes only work if publishing is low-friction. ISR keeps that friction low while preserving performance budgets from the homepage spec.

This note documents the rollout choice — not a benchmark chart — so future upgrades can trace which paths are cached and which revalidate hooks must stay in sync.

Related tools

← All notes