Hi Alex, interesting to see you asking similar question to those I was about to. ;-)
I just started to port tb5 <http://tobibeer.github.io/tb5> to a *node.js* managed version with neatly assorted folders only to be pushed some day onto GitHub ...and there is *a host of questions* bubbling up. For example, there are more wikis than just *tb5* and I will eventually do the same process with all of them. This introduces interesting problems. I have separate content bits but then some of the underlying framework of custom components I'd like to share amongst those wikis. So, I will eventually setup a folder structure like so... - common - config ...gobal config for all wikis - templates ...global templates for all wikis - macros ...global macros for all wikis - plugins ...selectively added to any of the wikis below - KaTex - Tinka - MyPlugin - wikis ...maybe these correspond to the editions folder in the TiddlyWiki repo? - tb5 - system ...anything beyond the common components - content ...the actual content of tb5 - filters - system - content - style - system - content - MyPlugin - system - content ...showcasing the plugin and demos for it - etc... For example, for the *MyPlugin* wiki there will be some repo on github where I maintain the code for MyPlugin, that I want to then utilize and demonstrate in the MyPlugin wiki. Preferably, building that wiki will somehow point to my local copy of that repo so as to include the latest built, me assuring that I haven't just switched to some bugfix-branch. Also, for some or all wikis I will eventually want to render static files, too. So I am wondering not only how to render those, as I've not done any of that yet, but also where to sensibly render them to. I have a similar problem for the actually built wikis, that I haven't yet figured out how to built, as their location will be outside of the above folder structure, since I don't want the output to be part of the same content-repository, as that would possibly blow that out of proportion. Currently, I have one big repo with all the standalone wikis in it that at some point were on TiddlySpot, so as to manage them more close-by... and I am a bit concerned that GitHub will at some point remind me of some quota I am about to reach. So, I started to, again, create individual TiddlySpot wikis for demonstrating things like modifications associated with a pull request. That way I don't add ever more wikis for that to a GitHub repo. On top of all things, I will also want to be able to quickly built a pre-release version with the modifications of a given branch for whichever pull requests I make to the TiddlyWiki repository. So far I have always been editing the affected components in the browser, which is possibly not ideal. Not yet done that prerelease built process, and so it needs more studying to run it under node... with respect to my forked folder. I guess Jeremy's instructions <https://groups.google.com/d/msg/tiddlywiki/___q7IP3FW8/cr8RA7kdBAAJ> above deliver the basic how2 to doing that. But then the demo-tiddlers to showcase the changes will have to be somewhere else, however not part of any pull requests. Ah, the complexity. :D I guess I'll have to constantly link and unlink different versions from where to compile my output as I probably wouldn't want to construct my main wikis from a pre-release built... as you do... although I can understand why you would. ;-) Much doing ahead. Best wishes, — tb -- 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/19318d29-0471-4329-81fa-42214084cb89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
