Question

Hi I am in process of evaluating Twiki to be used on our intranet as Knowledge base and as community portal. There are various groups spread across countries in our organisation who would need to start there own "Community portals" for collaboration. What I understand is that web in wiki is roughly equivalent to Portals (Media wiki as Portals!!). Is there any recommended deployment plan in terms of how webs should be created (like there can be web for each project within development community) to avoid proliferation of webs but still having some form of structure for arranging these Webs?

Environment

-- GauravSharma - 03 May 2006

Answer

This is more or less a matter of opinions, different TWiki installations are using different models.

I personally prefer one web per project because

• different projects may have different audiences
• many TWiki functions (search, WebNotify, TWikiAccessControl) work most convenient when applied to whole webs
• webs are namespaces, so every project can use the same topic name in their webs for the same thing (e.g. Project1.RoadMap, Project2.RoadMap) - and a default layout for such a project web can be defined in a web template
• yet all functions are available across webs, too.

On the other hand, many admins are rather restrictive with regard to creation of new webs. Maybe they'll add comments here, now that I dared to start

-- HaraldJoerg - 05 May 2006

A TWiki installation can be cut & sliced in a multitude of ways. No matter how you do it there will be pros and cons, so it's a good idea to document your choices as you go (so you can get smarter along the way! :-)).

-- SteffenPoulsen - 16 Jun 2006

See supplemental document on TWikiScalability.

-- PeterThoeny - 26 Mar 2008