Web Design and Engineering

Next.js, React, modern CSS, performance, immersive web, frontend architecture.

Page 3 of 3

Three layers pulled apart in a stack; on the front one the same card appears wide in one container and stacked in a narrow lit one

Web

Modern CSS 2026: cascade layers, container queries, :has()

Cascade layers end specificity wars, container queries replace component media queries, and :has() ships in every major browser. What to adopt in 2026.

A balance on an open-A fulcrum, tipped: the lower pan holds a dense block of lit tiles, the raised pan a quiet page with two small lit islands

Web

Why we still pick Next.js over Astro for most SaaS in 2026

We have shipped both Next.js and Astro this year. For SaaS specifically, Next.js stays our default. Here is the honest tradeoff in 2026.

On a white ground, a grid of tiles swept by a black vertical line: black tiles with a white dot behind it, two dashed empty ones, one ringed, and grey tiles ahead

Web

React Compiler 1.0 directives: use memo and use no memo

React Compiler 1.0 memoizes most components at build time. Where the two directives apply, and where useMemo and useCallback still earn their place.

Five diamond shapes in a row joined by a line to a large dark tile, each with a branch down to a small tile; a white path runs through three diamonds and drops at the fourth to a lit tile

Web

Server Components vs Client Components: the decision tree we follow

The five-step decision tree we apply on every Next.js 16 project to decide when a component stays server-side and when it needs "use client".

A full wall of dark tiles split by three glowing white fault lines that step down through the gaps, the pieces between them slightly shifted

Web

Next.js 16 + React 19: the 3 changes that break old SaaS code

Turbopack is the default bundler, request APIs like params and cookies are now async, and React Compiler 1.0 is stable. What breaks moving a SaaS off Next 15.

Back to Field notes