Hi,
I've learnt much from simply being a lurker in this forum. I've have a little web design skills, being a generalist in nature. I probably can't contribute anything in terms of know how and experience in getting a medical product through to market, but maybe one thing I can do here is perhaps make a comment on how you can sway the thinking back towards a wiki. And that is:
1. eliminate or reduce the learning slope
2. provide useful benefit immediately
Being still a learner, sometimes I am lost when some of you experts here use acronymns, sometimes the acronyms don't even match the paragraph being discussed... in this case I have to make assumptions... sometimes kind folks actually put the acronymns in brackets which then helps. Now going through threads can be quite tedious for learning and collecting information, to find one piece of information, I could be searching many threads, some leading to other issues etc. A well constructed wiki can help here. Using collective skills you could even build a Template generic Technical Document using a wiki
Anyway, I have never contributed in a wiki and before today I didn't know how it works, but having a quick look at some of the syntax and examples available on the net it looked fairly simple. So to address the above two points strategy I have started an Acronymn page. Lacking much info.... but the basic syntax is there and folks with information should find it easy to add to it. There could be folks in the forum more skilled with it than me, perhaps a few of us could form a team to handle the inputting of information into the wiki. Anyone wants to add something can send it to some central person and who ever has some free time could begin putting it in.
Structure of the Wiki is another matter to consider, I hope to illustrate how it could be done only.
Meanwhile congratulations for a very informative forum.
