Long lists and fast pages, without writing JavaScript

cms.render.loadMore() is a single call that paginates a collection. It renders the first page of items on the server, then appends an HTMX trigger that fetches the next page — when the visitor scrolls it into view, or when they click a button, depending on the trigger option. You supply a Twig template that renders one item and receives it as {{ object }}, and that same template renders the server-side page and every HTMX-loaded page after it.

Rendering the first page server-side matters for search engines, so load: true does it for you rather than making you write the for-loop. The rest of the options are the ones a listing needs: limit, sort, include and exclude filters, search, buttonLabel, and empty — HTML to show when the filters match nothing, decided by a lightweight count query rather than by rendering and finding out.

There are two placements. The default drops a self-replacing sentinel inside the content container. cms.render.loadMoreButton() emits a button you can put anywhere instead — a sidebar, a sticky footer — pointed at a container by CSS selector: items append into the target, an out-of-band swap rewrites the button's URL with the next offset, and the button removes itself from the DOM when the data runs out. Both have Data View equivalents.

The other half of this page is the cache tag, which stores the rendered HTML of a block so its body is skipped entirely on the next request. Give it a key, an optional TTL, and a list of collection ids as tags; when any object in a tagged collection is created, updated or deleted, every fragment carrying that tag is invalidated on its own, with no clear function to call. Caching is bypassed for logged-in visitors unless a fragment is explicitly marked shared, skipped in devmode so you always see fresh output while editing, and falls back to a live render if a cache backend errors.

Together they handle the two ways a listing page gets slow: too many items in the HTML, and too much work per request. A 900-post archive ships twelve posts and a cached sidebar, then streams the rest as the reader scrolls.