Pages Sections limit

I would like to make a suggestion regarding the Page Sections in the Kirby panel. When using the limit option to restrict the number of child pages displayed (e.g., limit: 7), the thumbnails currently wrap onto a new line when there are more items than can fit in a single row.

I believe it would be more coherent and user-friendly to implement a carousel-style display for these sections, ensuring that all thumbnails remain in a single row with horizontal scrolling, rather than breaking into multiple rows. This approach would preserve the panel’s design consistency and improve responsiveness, especially on smaller screens.

This small improvement would significantly enhance the panel’s usability and maintain a cleaner layout for users working with sections that have a limited display of child pages.

Thank you for considering this suggestion, and thank you for your continued work on Kirby!

@Contact Your suggestion wouldn’t allow then anymore to limit the number of pages (say 20) but still wanting to have them layed out as a grid with multiple rows. That would be a regression for many users. But maybe you have ideas hwo to support both.

Of course, it would still be possible to keep the page limit! A carousel would simply act as a dynamic pagination, where the total number of carousel cells represents the limit we want to apply. The key would be for the cells to be flexible. Just this morning, a client asked me to remove the “limit” option because he didn’t like the line break, without realizing he’ll likely have over 50 entries… and this happens consistently in my projects. I really hope this feature gets implemented soon.

@Olivier Jonvaux My point was that many developers would not want their section to turn into a carousel just becuase they limit the number of pages shown. They want to limit it to e.g. 10 pages, but still show all of them in multiple rows. If just by applyig a limit the section would render as a carousel, those developers wouldn’t be happy. That’s why I asked for an idea to support both preferences.

If the goal is to keep both options, perhaps the best approach is to add a new parameter, like “carousel: true,” for instance?