This is fire! Keep up the amazing work 😍 👍

For a template library where people scan to decide, Load More feels closer to the real flow - the cost of a long page shows up most in mobile scroll fatigue and the time before the 9→18 fetch, so I'd track time-to-decision and the scroll depth at which people stop voting rather than just click share.

The whole work looking good

Load more

For a large library, I would lean to Load More for casual browsing, but keep pagination when people need to return to a specific page or share a set of results.

Load more for a template library. People want to compare with what they already scrolled past, and pagination makes them lose that. Pagination makes more sense once they're searching for something specific.

I think load more or may be you could use the lazy loading, the records will load automatically once you are on the last record.

Pagination for me. With a template library people want to jump back to that one they saw earlier, and Load More makes that painful.

I’d go with Load more. It keeps everything in one flow without making users jump between pages.

Load More

I really love the feel the headline font adds to the catalogue. Is the name of the font Comfortaa?

Really insightful breakdown, Serge! Love seeing the step-by-step thinking behind the final result. Thanks for sharing this with the community!

For a template library I’d pick Load More, since people browse and compare. A small counter like “Showing 18 of 60” helps them keep track of where they are.