One feature that is missing on DNN core is a panel splitter or a module grid where it would allow you to split a pane into two or more panes.   For example, let us say you have a two-column template (left and right) and you have a large HTML/Text module spanning the right column.  Now under that HTML/Text module in the right column, you want to add four smaller HTML/Text modules (image module or any other modules).    What if you want to add another module the spans the entire right column under those?  In today’s DNN, there is not method to handle this situation without modifying the skin.

What would be great is panel splitter or module grid modules that could be added to a pane and split it up into new panes, which then would be added to the pane list where you can add modules to those new panes or even more nested pane splitters or module grids.

This would provide extreme flexibility and cut down the number of skins a skin developer has to put out as you would not have to make different versions to allow of more columns or rows, just layout the big pane blocks and the user can adjust per page to fit their needs.

At first glance, it does not seem like it would take a lot of work.  I was looking into this a while back and found the place where DNN builds the pane list.  In here, it would seem like you could hit the DB for a list of all pane splitter or module grid controls and add their pane names to the list.  The other part I did not look into yet is the editing of the panes (where you drag/drop/move) modules around, those would probably have to have some modification.

As it is, if you do not use 3rd party modules for this, it can cripple your layout of sites.  It would be a great feature to have in the core!

Any thoughts?

Yes, it would be for panes, but not a splitter.  Much more "like" the ModuleWrapper, but integrated so that the when you split a pane into multiple parts, the new panes show in your DNN interface as if they were originally on the skin.  This allows for multiple modules in a new pain along with all the normal controls for placing, moving and editing modules.

When DNN is building the pane list on a page, it could enumerate any of this pane splitters (or what ever they would be called) and add the panes specified in them to the list.  Possibly it could dynamically add a div or table structure for the new panes allowing them to work the same as the predefined panes on a page.