Hi Jeremy,

Thanks for the the indepth reply.

Being able to easily track and manage changes is essential, indeed. As you 
know, I haven't even tried to commit much, but I'll do some more warm-up 
exercises and I hope that will get things started.

I'm afraid the /dev site is not at all finished. It just aggregates two 
> different piles of docs, and I haven't had a chance to do any further 
> updates. Help welcome.


I hope I'll do some of that. 

For making it easy for people to make content updates I actually favour 
> individuals editing a standalone version of the wiki, and then submitting 
> the wiki when they're happy with it. We can automate producing a pull 
> request from a submitted wiki.


That sounds great.

I have a mild worry that some features of tw5 require power-user, if not 
developer-level knowledge. This shifts the focus away from providing 
solutions towards solution design, which of course is an honorable exercise 
but might be quite over the top for an everyday wiki user who is all the 
more interested in solutions (how to use features) and designing content and 
less in any under-the-hood widget-voodoo or macro-magic (how to design 
functionality).

I am not sure what makes node.js a user-centric topic, it's at best an 
admin / pro topic for a server environment which, again, requires some 
tech-know-how and somewhat of a power user to be willing to run it and 
understand what's going on.

Not sure if that's sensible, but perhaps there's room to extract some 
chunks into a "pro" wiki, so that the spectrum from using solutions towards 
developing them is split meaningfully, not only in terms of what is being 
documented but especially how.

Theoretically, there could be more segmentation, like...

   - tw5
      - *focus: the solution(s) and how to use them*
      - getting started, features, editions, apps, download, plugins, 
      resources, history, compact feature release notes
   - pro
      - *focus: developing solutions with wiki components, **server, OS*
      - coding macros, filters, messages, mechanisms, variables, detailed 
release 
      notes, 
      - node.js, commands
   - dev
      - widget- /plugin- /core-dev-guides, core documentation, 
      code-practices, github, contributing, languages
   
Best wishes, Tobias.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to