so you think that datasets in the module db-table, lets say the db-tabe of a guestbook is not only associated with a mid (module Id) but also with an uid (user Id) ? ...mmh, thereupon you could use one mid on one tab to let the user create his own content. (datasets associate with his own uid)

But how you gone display this content to others?

...loading a module for diplaying purposes would not only need the mid but also the userId. The mid is always supplied by DNN to all modules placed on a special tab.

At the end the main requirement for such an "template tab" feature would be an extra variable in the url that this template tab would use to supply unique mid resp. tabid to the modules.

...but since I don't wanne change the core, I think it would be best to use a normal tab/ page and placing somewhat of a container module on it. This container module would use the extra url variable to decide which modules it needs to host.

...keep on brainstorming

what do you mean by GUI ...a skin package, containers, modules displaying content or the general way dnn puts them all together after a users requests a page the way you already outlined:

"a tabid has a skin, a skin contains content panes, contentpanes contain modules and modules contain data"

...cause this is for me the dnn framework, I don't wanne change. I want to code a module on top of this.

a module managing my tabs & modules? ...can you name one? For my understanding a module is a bunch of controls that can be placed on a dnn tab providing certain functionality like a guestbook, a forum, or wrapper/ aggregator.

I think that's exactly what I intend to do ...a wrapper module that can host standard modules, limiting the the admin possibilities for my users and having the possibilities to display various pages for all of my users on one dnn framework tab/ page.

DNN Framework would load just this single tab placing the wrapper module on it. That's "all" DNN would provide. You would have to give some identifier in url query to this wrapper module so it knows what "template instace" it should load. Virtually this wrapper module would simulate the way dnn handles tabs, just using its own way to inject the modules and handle admin functionality. Hence giving me a better way to support 1000s of tabs and giving my user admin wright on these "simulated tabs" or "template instances" however you wanne call it.