A Quick Tip;

For those using dropbox and drive remember you can synchronise these or 
part of such as a file or folder locally. If your workflow keeps and saves 
the output to the local drive it can be automatically synchronised. 
The only caveat is to make sure the sync finishes before turning off your 
computer. 

In this thread there are a couple of tools mentioned for publishing drive 
or dropbox files on the internet such as fast.io

A lot of web hosting services also allow you to configure WedDav or online 
Web drive equivalents for your own folders, and automated ftp is also 
possible. These synchronisation methods are particularly use full for read 
only or static sites, but as long as you retain the "source of truth" the 
wiki copy you edit things in, it should all go smoothly.

I think all this static file activity has inspired a larger number of 
internet publishing, Please continue to acknowledge tiddlywiki where 
practical and do share back how you did it, as well as publicising your own 
published content.

Regards
Tony

On Sunday, 3 May 2020 06:36:01 UTC+10, Jeremy Ruston wrote:
>
> A disadvantage for some users of TiddlyWiki’s static site generation 
> capabilities is the requirement to use Node.js. I’m therefore pleased to 
> announce an update to the JSZip plugin that makes it practical to render 
> medium sized static sites in the browser, without needing to use Node.js.
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/6a0ff7db1807f45b73061ced82f5a85f1a529bbf
>
> The updated plugin adds a handful of messages that can be used in the 
> browser to:
>
> * create a blank ZIP file as a tiddler of type "application/zip”
> * add text files to a ZIP tiddler
> * download a ZIP tiddler as a .zip file
>
> To try it out, visit the prerelease and review the docs:
>
> https://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fjszip 
> <https://tiddlywiki.com/prerelease/#$:/plugins/tiddlywiki/jszip>
>
> The complete code to save a static site looks like this:
>
> \define actions-render-static-site()
> <$action-sendmessage $message="tm-zip-create" 
> $param="$:/temp/_ZipTiddler"/>
> <$list filter="[all[tiddlers]!is[system]limit[100]]">
> <$action-sendmessage $message="tm-zip-render-file" 
> $param="$:/temp/_ZipTiddler" filename={{{ 
> [<currentTiddler>encodeuricomponent[]addsuffix[.html]] }}} 
> tiddler=<<currentTiddler>> 
> template="$:/core/templates/static.tiddler.html"/>
> </$list>
> <$action-sendmessage $message="tm-zip-render-file" 
> $param="$:/temp/_ZipTiddler" filename="static.css" 
> template="$:/core/templates/static.template.css"/>
> <$action-sendmessage $message="tm-zip-download" 
> $param="$:/temp/_ZipTiddler" filename="myzip.zip"/>
> \end
>
> <$button actions=<<actions-render-static-site>>>
> Render site
> </$button>
>
>
> Performance is a bit sluggish with large zip files (>2MB on my desktop 
> machine) but otherwise it seems to work well. I’ve got an idea for 
> improving performance that I’ll work on if I have time.
>
> Questions and comments welcome.
>
> Best wishes
>
> Jeremy
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c09f9479-1d6b-438f-959e-f86bd715368f%40googlegroups.com.

Reply via email to