> b) While a "pure" community site would deliver a lot, I believe, it
> risks not being as prominent or "official" as would probably be good
> for it while also containing a huge amount of duplicate information
> with respect to tiddlywiki.com, tiddlywiki.org and all the rest of
> it... and of course, risking core contributors (also refering to
> people around Osmosoft) not taking part but leaving it up to "the
> enthousiasts" to, again, find this "too big to succeed" of an
> undertaking fail before even having started.

tiddlywiki.org is this no?
I would expect tiddlywiki.com to be a front door with the bare minimum
information. It should tell me how to use TiddlyWiki, it should point
to a community site (tiddlywiki.org), point to documentation of the
tiddlywiki core and point to the code. Not much else is really needed
although a blog might be useful to list known issues.

Tiddlywiki.org should go into more detail. It should clearly signpost
to me how I can get involved, how i can improve the software, how i
can get help and maybe make it easier for users to sign up to the
mailing list.

tiddlywiki.org as it stands has lots of good information but is far
too noisy with no clear sign posts. It mixes developer documentation
with end user documentation - a sorry state of affairs.

The navigation is terrible. There are links to the home tiddler and a
random button (which seems like a gimmick). Instead I'm expected to
search through the timeline or use the search to find the content I
need. I think this is because, although people are keen to look after
the content, someone who cares about this stuff should be keeping an
eye on the presentation.

My two cents would be
* someone needs to own this problem - note this doesn't mean solve the
problem, but it means be the coordinator - ie. the person who brings
up the topics of "the documentation doesn't cover X, and doesn't cover
Y" I'm happy to help with things like UI and code and getting the
relevant content in there, but I think what would be really useful
(and cool!) is if someone in the group outside Osmosoft, Jeremy and
Eric takes control of this.
*  there should be a public wiki where anyone can contribute
* there should be a deployed wiki to tiddlywiki.org which is composed
of the best bits of the public wiki and picked out by a subset of the
TiddlyWiki community (including the coordinator) to ensure content
doesn't die and is well structured.

PS. http://tiddlywiki-org2.tiddlyspace.com/ is a bit closer to how I
would like tiddlywiki.org to look like - I knocked this up to
hopefully get people thinking and experimenting.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywiki?hl=en.

Reply via email to