x28de It helped me to view all the initial stuff at one glance. If you don't like it (or don't like it here) throw it out.

But why don't these three maps "Deepamehta Architecture", "Users and Groups", and "Directory Services" have any "What's related?" relations?

• do you ask, why those maps don`t have some related stuff which is explanatory for the user if he wants to explore what these maps do? per default those maps maybe don`t have any associated topics cause they haven`t been opened up yet (cause then they become a derivation association to your private copy) or because they don`t have published yet (then they get a publishing association to the resp. workspace they have been published to).
  • x28de 08-Jun-2008 00:18 CEST I thought all objects should be somehow "hung up" somewhere in the structure, and this would be seen from the associations. But I have learned that the "Publishing" association does not work like I expected but just the other way around. And I experimented a lot with the permissions (only on my own installation, since on the central server my DeepaMehta membership is broken), and I was very much astonished about how open it is. So please check my "collaboration" sections in the User Guide if I am still completely wrong.

Malte i like the idea to have an overview visualized as a map. thanks for that. imo: informations visualized parallel as a map and a chapter layout make sense for further wiki pages too. additionally i wanted to show my intentions with this page. i didn`t want to build a type definition page, more a type description page. my first draft showed this not so clearly (cause of showing properties of the resp. types.) in this page i just want to talk about the description not about e.g. custom implementaton giving the help command some sense.