Please add native numbered pagination to CMS Collection Lists. We need numbered page buttons with a clear current-page state, previous/next controls, and direct, indexable URLs such as /blog/page/2 and /changelog/page/2. Ideally, the current page or route parameter would drive the Collection List Start Offset and Limit.

Today, native CMS lists support Load More and Infinite Scrolling. Start Offset and Limit are fixed controls; there is no documented binding from a route parameter/current-page value to Start Offset. A code component cannot access CMS collections at runtime to fetch and paginate the data. The CMS API and editor plugins are not a runtime pagination layer for a published native list.

We tried duplicating /blog into static page routes with fixed offsets. That can work for a small, fixed number of pages, but each route and offset needs manual maintenance, and our cloned responsive component instances did not reliably switch to their page-specific variants. This is impractical for a growing blog and changelog.

Please consider native numeric pagination with page numbers, previous/next, crawlable page URLs, and a supported way to bind the current route/page to the CMS list offset. Framer Support confirmed on September 29, 2026 that this is not currently available and directed us to submit the request here. Thank you!