How to: workflow for node.js tiddlywiki served via github.io

36 views
Skip to first unread message

Steven Schneider

unread,
Jun 18, 2018, 2:14:44 PM6/18/18
to TiddlyWiki
Hi folks,

There's got to be a better way to do what I'm doing, which is basically trying to run a production version of TW for designwritestudio.com, which is a tiddlywiki that serves as a textbook, course hub, and studio home. I'd like to version it (perhaps by semester), retaining much info and wiping other info.

I want two or more people to be able to edit, ultimately, so I"m using github and will explore pull requests as edit requests.

I anticipate building several versions of the same wiki over time (perhaps for each semester, for example), so I'm using node.js.

Currently, designwritestudio.com is served by designwritestudio.github.io. More specifically, designwritestudio.github.io returns index.html at the main branch of my github repo.

Do most node.js users edit the wiki on the http://127.0.0.1:8080/ version?

Or am I better off generating two files -- maybe index.html and index-to-edit.html --- from the node.js command "build --index" , and using  tiddlydesktop  to edit index-to-edit.html, and (somehow) render the tiddlers into the node.js version, and then rebuild the index in the node.js commands? (that's a lot of steps...).

Any thoughts of sharing of workflows would be helpful!

//steve.





 
Reply all
Reply to author
Forward
0 new messages