To maintain a proper application project structure and align it with the code structure (which is always beneficial), I have divided the artboards into separate Pages, similar to what is seen in VisualCode, to keep the project organized.
I must admit that this way of organizing the project is much more efficient than laying out 10-30 artboards on one canvas to cover the entire functionality of a particular application area.
Instead of scrolling through a large zoomed-out canvas in search of a specific screen, I prefer to select the area from the Pages list and immediately see all three artboards I was looking for.
It also makes onboarding proces for new designers/developers much easier, as you can first scan whole project by structure, and then click through it. Right now we have super flat structure in Sketch (andFi9ma), which is strange. Even super old AxureRP covered it a decade ago.
This solution scales much better in large projects such as back offices, e-commerce platforms, etc., where there are numerous screens and variations of individual functionalities.
Currently, I manage using a “visual tree” approach without the ability to collapse branches. While it is not a perfect solution, it is definitely better than canvases grouping multiple artboards.
I hope this inspires you to consider implementing such an approach.