@Edgaras A few ways to go about this. I favour a more unix inspired modular approach, small pieces of the overall workflow that do one thing and do it reliably.
My personal approach would be something like this: 1) use config/FileSystemPaths based on a tag to save the tiddlers that should be exported to a separate sub directory. See https://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming 2) a cron job (a scheduled task, both windows and osx have something equivalent too) set to run how every frequently suits you? Every 5 minutes? Every 15 minutes or an hour? 3) have the cron job run a script that runs the node js tiddlywiki commands to export your static site 4) I would probably also use a Makefile to handle the static build process, so that the export static commands only run when dependencies (tiddlers) have changed. 5) You could also add a step that pushes the exported files to your hosting service. Alternatively, I believe the tiddlywiki.com build process uses Travis for continuous integration: https://travis-ci.org/ Hope this helps, Saq On Wednesday, May 13, 2020 at 2:27:18 PM UTC+2, Edgaras wrote: > > I am trying to optimise the workflow of building static sites, now I am > trying to use Node.js TW version. > > Is there a way to continuously or periodically build/export static site > respecting defined filters (I only want to export tagged tiddlers). > > I am planning to share my optimised website building process when I am > done! 😊 > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/65b9df07-60ea-49ab-b5af-dcb7b0492142%40googlegroups.com.
