Hi Tobias > > 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). >
First, TW5 wikitext syntax is necessarily complex because it allows complete user interfaces to be built up from primitive parts. But, it's intentionally not necessary to delve into widgets and macro definitions to use TiddlyWiki; those things only crop up when customising it. Complex things will always be complex, but we should over time be able to capture more of the important idioms and capture them as high level wikitext syntax, or core macros, so that the key. We can also extend the control panel and other parts of the UI to make customisation easier to discover and explore. > 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. > I don't think that's right anymore. Installing Node.js is no more complex than installing a browser, and the commands to run TiddlyWiki are pretty trivial. Because it keeps all it's data in files its also very straightforward to manage backups. > 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. > I'm more inclined to move beginner material into a separate wiki - I'm planning to grow http://tiddlywiki.com/prerelease/editions/introduction into an interactive step-by-step tutorial. > Theoretically, there could be more segmentation, like... > I think that each segment makes it harder for people to find the content that they are looking for. I don't think we should split the primary docs into more than two parts, and those two parts need to have a clear distinction. The current distinction of being for developers is pretty clearcut, and we can refine the edge cases. Best wishes Jeremy > > - 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. > -- Jeremy Ruston mailto:[email protected] -- 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.
