I visit this site occassionally. I am largely interested in providing creative inputs. I also host twiki in my organization, and have tried to make it acceptable in a larger audience.
Things that I am interested in (in order of preference):
Structured Data Management, leading to good UI integration.
While some of us are most confortable with edit-save cycles to change content, I also find it very important to have "Add new list item" button to an existing list. How should we design this?
TWiki as Integration Platform for web applications.
Twiki allows information to be collected from diverse apps, databases (and of course manually created content). And it also allows us to manipulate this information, within a standardized framework. The framework provides: Users, Groups, Naming Standards and so on. In essence, this integration platform allows every resource to have an URL, and allows information to be managed.
Alternative to Excel.
While it seems a distant dream, I feel we can do it. How? Separate Reporting from data collection. Allow UI to create reports.
Integration with Email
: Most important people move around with their laptop, and can only respond to email effectively. Email also acts as offline store for all information that you come across. I would like to get twiki replicated as folders and emails within them. Yes, all versions of all the webs and topics that I subscribe to. And then use HTML composer of email to change content of twiki topic, and email it back. So both email world and 'shared documents' world can come together.
TWiki as Publishing Server, complete with Reverse-Proxy capabilities.
Published data is polished, and not supposed to change often. And people can add external comments (say on website etc.). In the same framework, twiki can also allow us to control who gets to see what data. It can access other intranet websites, and make those pages accessible to world (changing URLs etc. in the process.) The access control itself will be managed from within twiki.