Hello, I am new to TW. It seems, I should have discovered it long ago. (I had been using an app for Windows called *ConnectedText. *But, it lacks the killer feature of TW which is single HTML distribution.*)*
I have a question about the strategy for rational and flexible access to Tiddlers. It seems to me that for Core Business interests that it may be wise to just create Tiddlers as "info Lego blocks" into a "Core Bus. TW" as Tiddler repository. Then, by using the correct coding or Tagging strategy, to be able to extract a list of Tiddlers which one may wish to include in ... say "Project A" (while the same Tiddlers may *also* be employed in "Project B". So, given the bewildering set of system, user, shadow Tiddlers, I am wondering if anyone more experienced has a system which will: (1) Enable a single Tiddler to be coded in a way that will identify it as in the family of say "Project A" and also "Project B" if it is a common info bit. (2) Hide that multi-project coding since I will want to compile the family of Tiddlers as a business presentation and leave the content "tidy" (3) And be able to order the extracted Tiddlers from the Core TW File in the desired order of presentation Of course creating an "NY Public Library" of Tiddlers may be unwise. I don't know at what point a TW file becomes too fat and thus unwieldy. But, I plan to create distinct ones where possible. There seems to be multiple solutions spread about various user URLs. And I am sure I could divine this with hours of research and trial and error. I just wonder if someone *has been where I want to go *and can kindly *share* a shortcut. Thanks for any help. ## Q ## -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6484beeb-73e4-4b9c-9529-0156b511e477%40googlegroups.com.
