Thank you Tony for extended reply.
I got one idea to try. I am thinking about implementing a custom syncadapter. The build script would generate index.json which would be static and served by http server and used by `getSkinnyTiddlers(callback)`. The syncadapter would know how to retrieve index.json and tiddlers html from http server. Best regards, ILYA On 28 November 2019 19:18:25 GMT-08:00, TonyM <[email protected]> wrote: >ILYA, > >Perhaps you could layout what you want to achieve with this. >I do not think there is an exact solution waiting but depending on your > >objective it may be easy. > >Some notes that may or may not help > > - There is a method to externalise javascript ><https://tiddlywiki.com/#Using%20the%20external%20JavaScript%20template> > > - If you could host on node there are automatically generated static > HTML tiddlers ><https://tiddlywiki.com/#Using%20the%20integrated%20static%20file%20server> > this has being done for tiddlywiki.com > - There are instructions for Generating Static Sites with TiddlyWiki ><https://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki>From > > a folder based wiki (which is what you are doing) > - If you look at the instructions there in you will see the use of > tiddler templates $:/core/templates/static.tiddler.html > - In fact you can alter this template to output whatever you want the > exported pages to look like. > - Perhaps WidgetMessage: tm-open-external-window ><https://tiddlywiki.com/#WidgetMessage%3A%20tm-open-external-window> >could > also prove useful. > >Personally I want to simply publish both static (Seperate HTML files) >and >dynamic tiddlers (in the index.html) to increase search visibility and >allow low overhead views of tiddlers, >is that what you want? > > - I would like to generate a full single file wiki (index.html with a >splash screen) from a tiddlywiki with a separate static version of >every > content (non system) Tiddler, >- however any links there in would point to the actual tiddler(s) in >the > index.html. > - Thus searches will see the content of each rendered tiddler in a > static version and link to the real tiddlers, > - but on the first interaction the full wiki loads and thus all the > javascript interaction can take place. >- In addition in the interactive wiki provide each tiddler with a >button >that on clicking opens the static version of that tiddler in a new tab, > >I believe the above is achievable with a minor alteration to the >appropriate template, and the provision of a view template button to >open >the static tiddlers separately if desired. > >However a full interactive wiki is always the best for users, the >splash >screen keeps them waiting while it loads and adding a CDN like >cloudflare >on the front improves performance. > >If the reason is your regular tiddlers are images or videos and your >wiki >is thus too big, perhaps you need to investigate; > > - External Attachments Plugin > <https://tiddlywiki.com/#External%20Attachments%20Plugin> > - ExternalImages <https://tiddlywiki.com/#ExternalImages> > >Or even using other html >methods https://www.w3schools.com/tags/tag_object.asp > >Regards >Tony > >On Friday, November 29, 2019 at 1:36:12 AM UTC+11, ILYA Khlopotov >wrote: >> >> Hello, >> >> I am trying to make an edition which would include a set of plugins >and >> few custom tiddlers. This edition need to be exported as a web site. >> The website should act as read-only tiddlywiki. I.e. search and all >> included Javascript should continue to work. The exported site should >have >> index.html (which would contain all system tiddlers) and a set of >separate >> html files for non system tiddlers. All tiddlers from separate files >need >> to be accessible from index.html. >> Ideally I want to achieve that via tiddlywiki.info file without extra > >> scripts. >> I know it should be possible but I cannot understand how to make it >work. >> I found few examples but they don't do what I need: >> - "--rendertiddler","$:/core/save/all","index.html","text/plain"] --- > >> renders everything into a single file >-"--rendertiddler","$:/core/templates/static.template.html","static.html","text/plain" > >> --- produces noJS version of wiki I would like to avoid modifying all >my >> tiddlers. I tried exporting using $:/core/save/empty but I don't know >how >> to refer to other tiddlers (exported in html format) in output/static > >> directory. I included the content of tiddlywiki.info in the >attachment. >> >> Any hints or examples of doing something like this? >> >> Best regards, >> ILYA >> >> > >-- >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 view this discussion on the web visit >https://groups.google.com/d/msgid/tiddlywikidev/6e78c944-aa7e-4cbb-b651-d16e360e508e%40googlegroups.com. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/A3E7D9BC-095C-428D-9DA7-7346BB6AED3D%40gmail.com.
