Hi Mat, Mario -I'm not fully qualified to give judgement - but from my limited > perspective; What an absolutely wonderful writeup!!!! I propose it is > somehow incorporated into tw.com. >
Perhaps you could work together? Mat, you might be the perfect person to expand Mario's outline into an article. Perhaps stitch it with the background stuff I wrote to create an article called "How does TiddlyWiki work?" and then publish it on Medium and on tw.com? (Actually, it should probably be called "I looked inside the TiddlyWiki core and you'll never believe what I found"). The trouble is that discussions of improving the documentation at tiddlywiki.com generally flounder into a technical discussion of the means by which those updates could be made, and no writing takes place. Perhaps it's better just to write out a handful of key background questions that can trigger an interesting essay. Collaborate on it as a stream of text on Google docs if you want. Then we can worry about incorporating the essay into tw.com afterwards; the text-slicer tool I'm working on might useful if we got to that stage. Best wishes Jeremy. > > Regarding: > > >> So if someone would sit down and describe how the content of every single >> core tiddler (1218) works, we would have the "low level doc" for the actual >> TW UI and its "may be" reusable blocks. .. BUT ... >> >> Since we, the TiddlyWiki Community, are not able to fund Erics "Inside >> TidddlyWiki" documentation, which is a "TiddlyWiki User Manual", I doubt we >> will be able to fund the low level docs, that would be needed to create: >> "TiddlyWik the App Framework" documentation. So for the time being, this >> knowledge will be beautifully hidden in some heads, but not written down in >> a consumable way. >> > > > Ironically, we're working with the very type of tool invented for exactly > this problem: A wiki. IMO it is not feasible for "some*one*" to document > what you describe but rather it is a group effort (like Wikipedia) - but we > would need the infrastructure for it. I expect this to much fall in place > when the TWederation gets going, but a simple "solution" might be the "Public" > component <http://tiddlersidebar.tiddlyspot.com/#Public:Public> of my > TiddlerSidebar addon and the associated CommunityComments. This would let > you get immediate documentation on the tiddler you're interested in. (I > happen to know some things are in the doing that you don't expect so just > maybe this will take a big step in due time. Can't say more right now.) > > <:-) > > -- > 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 http://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/c75e2b8f-f6ad-46f2-9680-76139ffa9f04%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/c75e2b8f-f6ad-46f2-9680-76139ffa9f04%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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 http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJbk4XxaWKHypcYpjXn9U6Nx4eaQ5EQ-WnDJ_DUL0s%2BUpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
