Jed - while admirable, I think it is the wrong approach to statically document anything for TW, and one we've used just so many times for other documentation projects - with failure after failure. The most successful example using this documentation approach is tiddlywiki.com - but even this *exceptional* case suffers problems that stem from a static approach! The docs on tiddlywiki.com ARE very good (of course) but it is problematic to revise material and keep it up to date due to the process content has to go through (effectively putting most of the burden on one individual) and the documentation must keep a rigid structure that is good is some cases but unfortunate in others (for example, a user curious on how to use tags so he types in the natural term "tags" in the search field on tiddlywiki.com... will not be happy)
The superior way for a project like this is what you've already laid the foundation for, namely TWederation. (Ah, of course ;-) IMO the following is what is required for a successful TW documentation project: 1. get twederation working 2. set up a documentation TW that fetches peoples documentation 3. ...which for a particular "doc-topic" filters the relevant tiddlers to make an aggregated topic-display 4. include a "quality system" such as some voting mechanism to have tiddlers qualify for that topic-display The key is to not rely too much on any one individual. The high activity on the boards is a definite indication that there is no end to questions so documentation has to be flexible and allow for accumulation rather than the typical static documents we've had so far. Just my thoughts. <:-) -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b30fbf8b-f0a9-48a0-86eb-b5b6bd6bfe1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
