Many "collaborative" solutions to doing projects in distributed teams are being sold by
- business/social web sites - such as LinkedIn and Google+
- "dashboard" sites with post-it notes yellow stickies
- video conference hardware vendors
While it is necessary to have all of the above elements - you cannot handle all of the elements of a business or engineering project in that manner. You cannot reduce the complexity of business and engineering documents to a few style sheets in a web site. Accept it - real projects will always requires off-line complex documents and formats that cannot be preprogrammed into web objects - at least not in a cost effective manner.
They can however be stored, accessed and described on-line - which is what HRI's hri07e Infosys2 system is describing in its rough current form - and which a future infosys3 will do better; once infosys2 figures out what it's doing.
Infosys2 is more about a smallish but not trivial set of guidelines and standards for managing "knowledge" and "projects" which does not attempt to be encyclopedic (we have Wikipedia for that) but does try to do projects in a manner that is predictable and from which new non-proprietary information created by projects can be "discovered" and shared for future reuse. This is on the assumption that many projects repeat core methods and experience - but no two projects are alike in structure or content - unless they are the same project being repeated with nothing learned from the first one.