purplebox wroteYou would not want to give a user too many rights. There fore every default control panel in DNN could not be used (to expose to your users)
You would need to write custom control panel acoording to what you want to allow. Remeber DNN is a framework, not a solution. It contains all building bloks you would possibly need, the default interface actually limits your possibilities too much.
You would write a module so a user could manage his tabid, including adding modules and configuring them.
I'm not sure if I could follow you entirely.
However I can't see a way to use or extend the dnn framework without going into core to deep.
I thought about implementing some kind of template tab/page you would pass some kind of extra identification in the url (like Default.aspx/template/identification ) so it could simulate a real tab/page to the existing modules. This template would be a normal tab/page containing just one module. This module should then host all normal modules, giving them things like moduleId, tabId and so on. Maybe this "container module" could also provide limited admin functions to the user.
The idea behind is, that I create just one real tab ( template tab ), preventing DNN to create overhead creating 1000s. of tabs, causing the portal speed going down.
CAUTION: Just brainstorming
Any errors in reasoning?
maybe you can help.
thx
came