Hi Tobias Looking at tiddlywiki.com I am finding plenty developer related > information, especially concerning node.js, but also message > specifications, etc.... which really are not basic user material, imho. > Example: no user will be able to take something practical from > FieldManglerWidget <http://tiddlywiki.com/#FieldManglerWidget>. and all > the messages. >
The /dev site is for material for JavaScript developers, and to a lesser extent HTML and CSS. Material for end users running under Node.js is intentionally on tiddlywiki.com. In the case of the FieldManglerWidget, I think the problem is just that the docs are out of date and confusing, but they still belong on tiddlywiki.com. Is it planned to have all that migrated to http://tiddlywiki.com/dev/? > There is some material about message structures that should be moved but otherwise the split is roughly as intended. > I think it makes plenty sense to output all content of tw.com > <http://tiddlywiki.com> (or perhaps only that with a dev field) stuffed > into http://tiddlywiki.com/dev as shadow tiddlers. > Is that even possible using some kind of cross-wiki inclusion when > generating the lot using node.js? > I've thought about that too. We could include the docs from tiddlywiki.com directly in /dev, but I think it may be more helpful to make the basic docs available as a plugin so that other wikis can include them where needed. > Also, I think it were good if - rather than prose titles - > http://tiddlywiki.com/dev would be much more structured around a > meaningful tag hierarchy, things like... > > - Contribute > - Core > - node.js > - Github > - Plugins > - Widgets > - etc... > > 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. > Last but not least, could perhaps a dev space be set up for tw5 on > tiddlyspace such that working on that content does not require all that git? > 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. The trouble with baking a shared space on tiddlyspace.com into tiddlywiki.com is that then I have to take great care to check all the contributions. In the case of the space used for the content for classic.tiddlywiki.com, we had to make the space restricted to just a few authors. The end result was much the same: there was a big hurdle for casual contributors. Furthermore, I think a shared space can actually discourage experimentation because of the way that every change is instantly visible to other users, and may be propagated to tiddlywiki.com. Many contributors would rather experiment with their changes in private before submitting them for review. > Or is and will it be remain the strategy to have all that content managed > via the github repo? > I'm not at all happy with the barriers to contribution that github represents. Over the last few weeks I've put a lot of effort into engineering a way for translators to submit translations without using github, and I plan to do the same for tiddlywiki.com content. Best wishes Jeremy > > 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. > -- 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.
