10 articles tagged frontend.
A security questionnaire asks for a CSP, you copy the nonce recipe everyone publishes, and your statically generated site quietly becomes a dynamically rendered one. Which directives cost nothing, why the nonce is the expensive part, and how we split a policy so the security lands where it actually matters.
Sessions fell 41% the month after the relaunch and the leads went up, because the old site counted everybody and the new one only counts the people who said yes. What the consent rule actually covers, why cookieless is not automatically banner-free, the server-side denominator that makes the numbers honest again, and why the count that pays lives in the ERP.
Making a human prove humanity is a UX tax, and the bots pay it more reliably than your customers do. The invisible gate on every form on this site: a honeypot field, a minimum fill time, and a fake success that teaches the bot nothing — three server-side checks, no third-party script.
Thirteen services across four groups need more than a hover dropdown. The roles a navigation menu must not use, what a portalled panel does to your tab order, and why the mobile menu is a different component rather than a smaller one.
Prefetch-everything wastes bandwidth, prefetch-on-hover fires too late, and neither exists on a phone. Cursor trajectory, tab distance and scroll direction are better signals — and this site already runs them.
CSS-first config turns Tailwind into a token pipeline: OKLCH variables in, consistent components out. The two-layer setup, the one keyword that makes dark mode work, and the four files where the cascade stops.
When your primitive library changes direction, you migrate deliberately. Mapping Radix patterns onto Base UI, the accessibility differences that surprised us, and the codemod that did the boring three quarters.
LCP, INP and CLS are graded on real visitors at the 75th percentile, not on your MacBook with a Lighthouse tab open. What actually moves each metric on content and commerce sites, ranked by effort.
Language in the URL, slugs in a translation map, detection demoted to a suggestion — plus the tooling question: when we reach for next-intl vs Paraglide JS, and why Tolgee runs the translations from our own clusters.
HSL lies about lightness. OKLCH doesn't. What changed when we rebuilt a brand palette on a perceptually uniform color space.