Hi Rick, On Wednesday, October 22, 2014 11:35:14 PM UTC+2, Rick Williams wrote: > > > There is still the option, to create a completely static version of all >> tiddlers, no javascript involved. >> This could be served entirely by the nginx server. >> So every tiddler is a single page. .... There would be the need for a >> different layout, because at the moment the static version uses the same >> layout as the js version. >> > > Can you point me instructions for deployment of a static environment built > from a standard TW5 wiki? >
If you have a look at the tw5.com tiddlywiki.info file [1], you can see the static build section. The first step/line: .. creates a static.html file, that is like a "startpage". So imo it's important to have a TOC there :) second line: .. creates an alltiddlers.html. ... As the name says the whole TW in one tiddler (no js) So imo its nice to use the browser search third line: .. creates all tiddlers as single tiddlers into a static/ directory forth line: .. creates the needed CSS file. I'm using the exact same settings [2], to create a static version of the german translation. So you should be able to just copy paste the stuff into your tiddlywiki.info to test it. build static command: node tiddlywiki.js yourEdition --build static build all command: node tiddlywiki.js yourEdition --build ---------- To build your own static layout you have to have a look at the $:/core/templates/xxxx tiddlers [3]. So it would be possible to create your own branding :) Template handling can be a bit tricky. .. But its all html5 + tw5 wikitext syntax. Used elements are html, macro definitions, filters and transclusions. Docs can be found at tiddlywiki.com But imo this will be the second step. ------------ I also talked with Jeremy at the last hangout #65 [4] about the difference between image tiddler lazy loading and images using _canonical_uri The link starts at the position and the discussion is about 10 minutes. There will be some background info, if you want to see it. Tiddler lazy loading would have been a solution for your too but I simply forgot about it. After our last discussion I think this mechanism fits better to your workflow, and would eliminate the conversion from "fat" image tiddlers to "skinny" tiddlers using the _canonical_uri. images can be "fat" but would be loaded in a second step. ... see the video have fun! mario PS: any success on loading speed? Please keep us updated. [1] https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/tw5.com/tiddlywiki.info#L54 [2] https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/de-AT/tiddlywiki.info#L25 [3] https://github.com/Jermolene/TiddlyWiki5/tree/master/core/templates [4] https://www.youtube.com/watch?v=hJ4feiD6iuY&feature=player_detailpage#t=4144 -- 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. For more options, visit https://groups.google.com/d/optout.
