Articles about software engineering, Odoo, cloud infrastructure and running a digital business.
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.
Visitors who use search buy at several times the rate of visitors who browse — which makes the search box a conversion feature, not a technical checkbox. When the database you already run is enough, when typo tolerance pays for itself, and the sync problem that is the real project either way.
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.
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.
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.
Tell us what you'd like to read and we'll add it to our writing queue.