You want a fast initial page load, but you also have dynamic, personalized product requirements. What if you could have both, within the same page, with no new APIs? Learn more about experimental Partial Prerendering in Next.js.

@nextjs This fulfills the promise in the old tagline dynamic at the speed of static

@nextjs Thanks for making the video! It's so much clearer when showing it visually!

@nextjs If you're using `cookies()` in the root layout for stuff like personalization does that prevent all PPR?

@ianduvall_ @nextjs

@nextjs What I really want is to be able to completely detach static pages from the Next.js server, have it on a CDN for example, but still be able to re-render them and push the new versions to the CDN. I love Next.js, but want to ensure key pages are in a CDN, not reliant on a server.

@nextjs Since this is built with ISR does this mean every time we load the page it would incur ISR costs?

@nextjs there’s a new lee rob tutorial every month

@nextjs That's the goal!

@nextjs Is it possible to use PPR at all if you need to support multiple UI languages but instead of having the locale as part of URL, it would be in session? I assume that you can have only PPR for each route?

@nextjs Can we talk about the triangle in the back in the first 5 seconds 🔺🔺