Le mardi 21 avril 2020 08:17:14 UTC+2, Yoni Balkind a écrit : > > Thanks for the outline. I'm finding that readonly plugin (step 5 of your > outline) a bit confusing. For example it references a ReadOnly ay > tiddlywiki.com but I cannot find the theme. Though it might only be > mentioning it as an alternate option. Nevertheless the process is a bit > unclear and from what I can tell it does not hide all of the controls so as > to make the wiki look like a blog. > I think I'll go the static route so I will wait for Anne-Laure tutorial. > > I think that making a site readonly and looking like a blog is an > important use-case, should be easier to do and well documented >
Hi, I think that until now this has not been the primary use of TiddlyWiki users. For the most part I think our favorite notetool is personal and therefore not public. Static site generators are indeed fashionable, and there are many ways to do this with TW (as there often are). BJ had proposed something, we can find Ton Gerner's http://tw5readonly.tiddlyspot.com/ Otherwise more recently Jed proposed this: https://ooktech-tw.gitlab.io/plugins/readonlycore/ (see here https://groups.google.com/forum/#!msg/tiddlywiki/EHSH7ll6jcg/Z8BQQiq-CAAJ) Mohammad also proposed something interesting with modal window. Personally I use a button to do the work and customize the elements I want, but as it's still a standolone TW, you can always access the engine to take over if you know it's a TW. A true read-only, static, JS-code-free TiddlyWiki loses the meaning of TiddlyWiki on searching, tag browsing, etc. (and because I'm still not comfortable with Node.js) Cheers, Sylvain -- 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/17d399e4-7cc8-45e5-b436-6bbf490974f7%40googlegroups.com.
