Progressive updates

Keep pages server-rendered by default, then enhance small repeated actions with scoped fetch requests when the result can be reflected locally.

Use it for

Good candidates are row toggles, mark-read actions, inline text saves, and other single-state changes where a full reload would interrupt review work.

Requirements

Preserve the canonical URL, keep links and pagination server-rendered, validate CSRF on the endpoint, and update nearby counts, badges, focus state, loading state, and live-region feedback in the same interaction.

Avoid it for

Leave multi-step forms, filterable list URLs, checkout, destructive flows, and complex cross-record changes as normal SSR pages unless the no-reload version has a clear accessibility and state-management plan.