Beautiful. I had begun to suspect that tiddlyweb was awesome. This clearly shows that it is. Well done!
jayfresh
· 6 months ago
This is cool. I have a couple of reactions, neither of which are meant to suggest better ways of doing things, rather point out alternatives that I've seen used:
1) serializer vs. mounting URL paths to template content
For the ILGA project, which has been my primary use of TiddlyWeb, we have used a lot of templating to render tiddler content as HTML pages. To do this, we have added URL paths such as '/article' or '/index.html' that trigger the templating process. There is more about our experiences here: http://jaybyjayfresh.com/2009/06/13/using-tiddlyweb-as-a-content-management-system-for-ilga-org/
2) serializer vs. static plugin to get js/css files
In an embryonic project called "WikiCSS" (the only thing I have written about this is here: http://jnthnlstr.tiddlyspot.com/#WikiCSS), I wanted to allow tiddlers to be retrieved and interpreted as .css files. To do this, I was hoping to write a Serializer to do the job; in fact, I think this did happen but I can't find it now.
All Comments
1) serializer vs. mounting URL paths to template content
For the ILGA project, which has been my primary use of TiddlyWeb, we have used a lot of templating to render tiddler content as HTML pages. To do this, we have added URL paths such as '/article' or '/index.html' that trigger the templating process. There is more about our experiences here: http://jaybyjayfresh.com/2009/06/13/using-tiddlyweb-as-a-content-management-system-for-ilga-org/
2) serializer vs. static plugin to get js/css files
In an embryonic project called "WikiCSS" (the only thing I have written about this is here: http://jnthnlstr.tiddlyspot.com/#WikiCSS), I wanted to allow tiddlers to be retrieved and interpreted as .css files. To do this, I was hoping to write a Serializer to do the job; in fact, I think this did happen but I can't find it now.
J.