@riverbankcms/sdk 0.75.0 → 0.77.0

package/README.md

@@ -3286,6 +3286,8 @@ Keep the `import()` inside the lazy factory. Wrapping a component that was impor
 
 `createCatchAllPage()` filters and resolves lazy overrides per rendered page, so unused factories are not invoked. Next.js still builds the client-reference manifest from the static catch-all route graph, though, so a static `import('./HeavyClientBlock')` inside the route graph can still appear in internal build manifests even when that block is not on the current page. For client-heavy blocks, keep the server override wrapper small and put ALTCHA/forms/booking widgets behind block-local client boundaries, then verify the production build artifacts for the specific site.
 
+For a fuller public-performance checklist covering broad client imports, bundle measurement, and decorative image/LCP pitfalls, see [`docs/usage-patterns.md#performance-optimization`](./docs/usage-patterns.md#performance-optimization).
+
 This single call replaces ~160 lines of typical boilerplate that handles:
 - Path resolution from URL slugs
 - Content loading (pages and entries)