Caching Page Designer pages and refreshing type definitions
Key Takeaway
A Page Designer page, with every component on it, is cached for the shortest cache time that its component types set in their render functions, even if the page type sets none. If neither the page type nor any component type sets a cache time, the page isn't cached.
Page Designer pages use the same storefront page cache as other storefront pages. The developer's scripts decide how long a page stays cached. The platform renders each page inside two nested remote includes, so it can cache each visible version of a page separately. The page types, component types, and custom attribute editors that developers build are also cached in memory. On production they refresh only after a code version switch.
Page Designer uses the storefront page cache
Page Designer has no cache time of its own. Page Designer pages use the same page cache that other storefront pages use. A page stays cached only as long as the developer's scripts say.
Two cache lifecycles run side by side. The controller that calls PageMgr.renderPage(), for example Page-Show, has its own page cache. The page content has a separate cache. Because of this split, cache settings in page types and component types apply to the whole page but not to the controller that started the rendering.