gary.moncrieff:
Not sure I am using this correctly.
I discovered it's quite easy to add a panel area to any existing template, however doing this means the menu doesn't stay highlighted when active even with the new version.
I envision that supplying templates with panel area will be the best way to provide additional skins based on this.
The Menu module and the Panel module are not connected, they just work well together.
Sure you can add a panel to an existing location. I would expect that it would increase your support requests when users ask to be able to alter that area.
---
There is no 'correctly' there is only 'currently', how do you want it to work.
Here's what I envisioned and my thoughts going forward.
What I expected skin developers would want to do would be to create a layout by using the system. They would build their site the way they wanted it by creating custom templates and putting them in the /skin/( jrSlate renamed )/* folder and linking to them from the "template" section of the widget.
Once the system was as they wanted it, they would EXPORT the panel structure via:
SITE BUILDER -> PANELS -> TOOLS -> EXPORT
and package that with the skin. When the skin was activated that structure would be IMPORTed to give what the skin designer imagined to the next person.
So a skin designer in the case of the SITE BUILDER system would be creating the extra template options for the widgets.
updated by @michael: 12/22/16 11:55:59AM