I'm not 100% sure, what Stephan wants to do but I was also thinking about a "pure html" publishing workflow. ... So everytime a tiddler is saved, it should trigger an event, that creates a static version. ... but since tiddlers can be transcluded, you basically have to recreate the whole stuff. ...
Then I thought a little bit about it. ... What I actually want is something like this. - Edit a tiddler and save it. - Create a "private" static version of this tiddler for review. - If the review is ok. Publish the static tiddler. - Publishing a tiddler causes the recreation of all static tiddlers. May be only those, that are effected (in a second step). - Define a publishing date for static tiddlers. So you can create several eg: "blog posts" at once and the system publishes them, with a defined date / per tiddler. .... So for me this would be a serverside app. socket.io could be used for the realtime stuff. eg: static preview. A "cron job" like mechanism could be used for the "delayed" publishing. ... ... TiddlyWeb has all the bits and pieces, to make this happen. They exist and are tested in TiddlySpace. So for me it's a reuse and not a "new feature" problem. The problem is, how can we make the setup a "one click install" experience. just some ideas mario -- 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.
