I used to do that too, but then I refused. This is bad practice, I think. The “Section” element is a full-fledged html tag, with all the ensuing consequences - it gets into the DOM and also into the route path to the nested elements when the binding is done.
This question was also raised quite a long time ago and an excellent proposal was formulated to add a new element to the AC side, which would allow grouping elements in the tree (as shown in the screenshot above), but at the same time, which did not create absolutely no problems for the code. The implementation is extremely simple - this element would be an ordinary comment in the code, with special marks that the Wappler would recognize and display it in the tree visually.
The idea was supported by everyone. George confirmed that this is quite simple to implement. Implementation was hindered, apparently, by more serious tasks. It would be great to revisit this idea again.
An element for grouping in a tree, which would be a regular comment in the code, would be an amazing tool for improving navigation in the tree and increasing the order in the structure of the application.