Longer term there will be a more flexible way to include plugins.
Use tav (https://github.com/akaspin/tav) as the args processor. If there are no remote tiddlers than we just have an empty store.
This separtes the main code into it's own script, which requires the twikifer code as a module. This will make it easier for some other code to require twikifier for its own purposes.
…g into two files.
That is: at the start of the process, load up the tiddlers from a given URI, process them to put them in the TiddlyWiki store. Then run the wikifier. This allows things like the timeline and list macros to actually list some information.
Needing to bring in TiddlerFields.js Dates.js Lingo.js
add a jstest make target that runs test/*js files which contain assertions (these ought to be migrated to some kind of test harness)
This makes it a bit easier to test and play with.
While knowing such things is not critical to the twikifier experience, the knowledge was hard won and worth recording.