
CORS Preflight: The Hidden 100-300ms Latency Tax
Your app is 100-300ms slower than it needs to be. CORS preflight requests add invisible round trips that double your API latency. Here's how to fix it.
We believe in the power of digital technology and co-creation. This blog is our contribution to our community of technology enthusiasts and learners. Enjoy!

Your app is 100-300ms slower than it needs to be. CORS preflight requests add invisible round trips that double your API latency. Here's how to fix it.

I spent 12 months running a multi-city event platform on both WordPress Multisite and Next.js + Directus. 400+ content items, 15 independent city sites, multi-tenant permissions.

The biggest problem with headless CMS: no visual page builder. Here's how I built a 26-block content system that supports non-technical editors.

After migrating a multi-city festival platform from WordPress Multisite to Next.js, I chose middleware-based multi-tenancy to serve 10+ city sites from one codebase. It works, but not how the docs suggest.

When working with dynamic HTML in Next.js, you might need to handle content that includes external scripts, stylesheets, and inline JavaScript. Instead of using dangerouslySetInnerHTML, which doesn't execute scripts, a more effective solution is embedding the HTML inside an iframe.
About fifteen questions, five minutes — Shyam writes it himself, free.