Yeah I do get that my use-case deviates from the original intention. But there is a very lively global community emerging right now around note taking and productivity. This is being driven by the likes of Tiago Forte's Building a Second Brain, the note taking app Roam Research, the book How to Take Smart Notes, Andy's super impressive notes page https://notes.andymatuschak.org/, and also Anne-Laure who is active on this group.
By sheer chance it looks like TW maps quite beautifully to the needs of this community for two different reasons. 1 - TW looks like it can be an open source version of Roam Research 2 - TW looks like it can allow people to replicate Andy's notes page (my use case) So fate has presented the TW with what I think is a big opportunity to ride the wave of the above mentioned movement/community. I think if you cater to their needs then TW could explode! Just look at the amount of activity and cult status that Roam Research is getting while still in beta. I don't doubt that the above things are possible in TW, but they are fringe cases and as a user trying to do these things it feels like I'm going outside the bounds of what TW is meant for. The experience is cumbersome. I'm just putting forward the idea that maybe these use cases should be considered more central and that they should be made easier, the experience should be streamlined and documented better. But I'm biased because I'm not originally from TW, I come from the above mentioned note-taking / productivity world. Its obviously a strategic decision for the TW community as to whether these use case are important and central enough in terms of the TW values. On Tuesday, 21 April 2020 12:38:21 UTC+2, Sylvain Naudin wrote: > > > > 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ca910951-fbc7-4ab3-abee-8c074d31b489%40googlegroups.com.
