Haven’t read through the whole thread but wanted to chime in anyway. From my own experience I know that different groups of people think, act and communicate differently. Different in such a way that they, many times, don’t understand each other.
You can go to any regular company where they have their own IT department and you will find out that “business people” and “it people” don’t get along and don’t understand each other. Still they need each other, so if they want to create something valuable you put in a sort of translator.
Translation is key here.
If you want to serve different groups of people that can benefit from TW you should make it easy for those different groups to “find their own sound”.
- for note takers
- for information hoarders
- for developers
- for website owners
- for personal application makers
- for community builders
(I’m making those groups up for illustration purposes.)
What happens now is that you come to Tiddlywiki.com:
- have to learn that language first
- translate it to your own
- find some use for it
- start using the newly learned language
- transform that to something you can actually use
Those are steps that are pretty daunting in themselves. And here is a whole cluster of them…
So turning that around would look more like this:
- I have an idea and it looks similar to this pick an example from the TW5 website
- getting some explanation how this example was build in your own language
- start using the examples and grow from there linking each example to other possibilities (incl. examples!), isn’t that what TW is good at anyway?
- end up with something you can already actually use
It is my understanding that the intention of TiddlyWiki from the start was to give people the possibility to create their own applications.
Good stuff these discussions because it becomes clear that we need to attend to things beyond technical capabilities in order to fulfill that initial intention.