If someone could also extend the dev docs,  that would be wonderful too. As it 
is now,  it gives a broad outline of practices in TW. Beyond that we are 
expected to understand the use cases and best practices by looking at the core 
tiddlers. I think if we manage a couple of more stepping stones,  the 
relatively new ones to programming might build something useful to themselves 
and community. 

Oh,  also a suggestion to add a separate tab in the community tiddlers edition 
for plugins alone,  preferably in a table format giving link,  author, and a 
one line description. 

One other thing I strongly feel should be done is re-ordering the topics on the 
tiddlywiki.com sidebar. I guess some logic has gone into organising it like 
that, however I fail to grasp it. Under the topic "Learning",  we have topics 
like "Creating substories" coming before far more basic things like "How to add 
a new tab to the sidebar". You would think that "editing with emacs" and 
"editing with vim" will be close to each other, but nope. And to cap it all,  
the first step - "Creating and editing tiddlers" comes way down -somewhere in 
the middle. 

I understand the possible counter-argument to this is that TW5 is a hypertext 
based wiki and table of contents is not the main method of organization. 
However, to someone new to wiki,  it is a confusing quagmire. It was to me 
while I started, and my learning process has been extremely inefficient and 
time consuming. I have a feeling that I am not alone in such a situation. 

Last but not least,  little less dull colors,  please. 

-- 
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/bc578ade-cb15-46c8-be45-85e3185a1c33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to