18 articles tagged nextjs.
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.
A technician stood outside a locked building at seven in the morning because a recurring visit had been expanded into absolute instants six weeks before the clocks went back. The three kinds of "when" that don't convert into each other, why a recurrence rule is not a list of timestamps, what Odoo hands you over the API, and how to test a bug that only reproduces twice a year.
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.
Raising the body-size limit is the fix that keeps working right up until it doesn't. Why buffering user files through your application is a dead end, the presigned handshake that replaces it, the checks that still have to happen after the bytes land, and why the ERP should be handed a pointer instead of a payload.
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.
The new site is faster and better looking, and three weeks later organic sessions are down a third. Nothing looks broken, because a 404 is a working page. Where the URL inventory actually comes from, why the sitemap isn't it, where redirects belong in a Next.js stack, and the rule that stops people blanket-redirecting a thousand URLs to the homepage.
Postgres can push an event to your app the moment a row commits. The trigger that catches every writer including the ERP, the listener that survives a reconnect without losing a change, the pooler that silently breaks all of it, and the bulk import that turns a live board into 40,000 notifications.
You don't have to replatform to get a fast shop. Keep WooCommerce as the order engine and wp-admin your team knows, put React in front of it, and be honest about the one hard part: checkout.
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.
Next.js will happily serve your JS bundles from a CDN with one config line. We stopped doing that. Hashed chunks belong to the build that emitted them; images outlive every deploy — and treating both as 'assets' is how a rollback turns into a cache-purge incident.
No database, no admin panel, no plugin updates. Content is MDX in the repo, frontmatter is a Zod schema that fails the build, review is a pull request — and publishing is a merge. The architecture behind this website, and the case where you shouldn't copy it.
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.
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.
This site renders once at build time and serves from memory. SSG, ISR, and the short list of things that genuinely need a request-time server — most marketing pages aren't on it.
React Server Components moved the data question out of the client bundle and into the render. For pages backed by an ERP, that's not a trend to adopt blindly — it's a boundary worth drawing precisely.
Every custom build ships two frontends — the one your customers see and the one only your client's own staff opens. The first earns Next.js. The second is usually paying a tax for machinery it never uses.
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.
Remote turbo caching turns ten-minute builds into ten-second cache replays, and a self-hosted Woodpecker pipeline deploys every PR as its own preview instance. The setup behind this very website.