12 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.
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.