
Next.js cache on Vercel: what I change first
On Vercel I do not start with a CDN checkbox. I name the fetch cache, the tag, and what busts it after a write.
Hi, I'm Aris Setiawan. Cursor Ambassador in Indonesia. I build Next.js, WordPress, and AI products for teams worldwide — and coach developers on practical Cursor workflows. 13+ years.
Experience
13+ Years
Projects
50+ Delivered
Location
Indonesia

Next.js, WordPress, AI features, and performance work — shipped to production, remote-friendly.
Build blazing-fast React applications with server-side rendering, static generation, and modern web architecture.
Custom themes, plugins, and headless WordPress solutions for scalable content management systems.
Enterprise-grade PHP applications with Laravel, custom APIs, and database architecture.
Audit, analyze, and optimize your web applications for Core Web Vitals and user experience.
Mentoring, Cursor workflows, and community learning for teams and builders who want to ship faster with AI.
13+ years building scalable web products for startups, agencies, and enterprises.
Named collaborators include Hongkiat, SAB Digital, Raja Kreatif, and Ta-Wan.
Cursor Ambassador Indonesia and MiniMax Dev Community Expert.
Remote-first workflow with clear communication and timely delivery.
Previously worked with
Technical articles, tutorials, and thoughts on web development.

On Vercel I do not start with a CDN checkbox. I name the fetch cache, the tag, and what busts it after a write.

I use WordPress as the CMS and Next.js as the front. Here is how I fetch, draft, and revalidate without treating WP as the site.

I migrate Pages to App Router one URL at a time. Copy the data rules, keep a rollback, and leave the next route until this one is boring.