Springer, A most important consideration - who is the audience?. For many wikis it is them-self, and the prior issues are important, but anything planed for the bigger world the scope is often easy to define.
Thanks for making this important point. This aspect could possible be broken down further. Such as read only publications vs those with serial editors need different support tools. Regards Tony On Friday, June 12, 2020 at 5:06:14 AM UTC+10, springer wrote: > > Just one more variable here, in terms of whether and when to individuate > TW instances: AUDIENCE > > Many of my TW projects are already -- or may eventually be -- shared with > a particular kind of audience (often students in a course, but not always). > I have one catch-all wiki for all the personal project content that doesn't > fit any of those baskets, and another for TW-related experimentation > (plugins under evaluation, useful tidbits and how-tos, plus resources and > links squirreled away for future exploration). > > For any audience other than myself, when the point is the content rather > than the tool itself, I like to share a wiki that doesn't include too many > unrelated tiddlers. (And often even the interface style wants to be > different, and I do enjoy having different interface flavors as I shift > from one domain to another on a given day.) > > Of course, one might prefer to keep everything together, knowing it's > possible to export a filtered set of tiddlers down the road. But when I > already suspect that a body of ideas may be prime for sharing later, I > start by setting up a tiddlyspot site for it (with an encryption password > if need be). Then I can share a link to the site in a totally spontaneous > way when I run into someone who would appreciate it. > > -Springer > > On Thursday, June 11, 2020 at 7:36:15 AM UTC-4, TiddlyTweeter wrote: >> >> I support multi wikis! In my opinion like a word processor you should >>> have different docs for different purposes! >> >> >> I agree that one way to conceive a wiki is as a "document" in the same >> way a word processor does. But many other mental models work too! For >> instance your very own Tiddler Commander can be best thought of as "utility >> software". Its a serious application. That is the richness of TW, its >> architecture supports many models of function and purpose. >> >> Regarding the OP there seem two dimensions ... >> >> 1 - SCOPE - meaning what the wiki is for: mixed purpose (e.g. don't need >> several wikis), single purpose (e.g. bookmark collection), single document >> (e.g. e-pub), mixed content (e.g. a media hub), dev-environment (e.g. for >> prototyping) etc... etc ... etc... >> >> >> 2 - PERFORMANCE - Though TW scales well, at size there are known limiting >> factors, depending on a wiki's construction (dynamic tag use being a major >> one, I think.) BUT we do have special plugins like Dynaview that might >> address this issue on large wikis; though they are only just beginning to >> be used so examples to follow are limited. >> >> >> Best wishes >> TT >> > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f2adee31-9d87-4eec-9068-b128dff2c575o%40googlegroups.com.
