@springer : Alright. That lowers my fear of messing up my data. Got you, that's also what I saw on your teaching Wiki. You have a red outline and yellow background for definitions for example, which, as you say, tells us clearly that we're looking at a definition.
@Charlie Veniot : I'm sorry if I sound dumb, but I don't understand what could be the use of "relink". Is it related to the dynamic modification of links ? So basically, whenever you change a title, it gets updated everywhere thanks to relink ? Thanks :) On Friday, 27 November 2020 at 00:06:29 UTC+1 springer wrote: > Cl0d, > > You'll find people here at both extremes: some use one massive TW5 as a > repository for everything, figuring that this path makes maximal room for > connections even across domains that may seem separate. > > My own approach is different largely because I like to have TW5 files that > I can share with different audiences, without worrying that something > intended for one audience would be distracting or even inappropriate for > another audience. Obviously, that holds for a project devoted to a > particular university course. I also set up a TW5 for a committee I chair; > it's locked down with an encryption password and includes notes that aren't > appropriately shared except with others on the committee (though I don't > naively upload anything to an online repository like GitHub that is > super-sensitive). For another example, folks at the TWGG know that I just > set up a super-minimal TW5 for hosting the images connected with the 5.1.23 > logo contestants. Anyone who visits that wiki can poke around the "Recent" > list without being confused by a long list of irrelevant things. Many > plugins offer demo TW5 pages that are similarly stand-alone. I enjoy > developing each of my projects with a distinctive color scheme and style > set so that it feels like I'm arriving in a different "work environment" > when I shift from one project to another. > > Whichever way you go, you should be reassured that dragging tiddlers > between files, or filtering and exporting a JSON batch and dropping it onto > a different TW5, allows you to engage in fusion or fission as needed down > the road. > > -Springer > On Thursday, November 26, 2020 at 4:13:44 PM UTC-5 Cl0d wrote: > >> Thank you for your answer. >> >> It can without a doubt serve, I'd say, unlimited purposes. And the fact >> that you outlined that, made me realize something I internally knew since >> the first day I started using TiddlyWiki : the way you organize TW, greatly >> depends on what you do with it. >> >> I have flown over both plugins tutorials and I'm going to try them out on >> one of my test Wiki's, to see how I can use them. >> >> Your site is amazing. This is definetly the kind of organization I'm >> looking forward to achieve. >> >> I hope you don't mind me asking this question, but do you use TW for >> other purposes ? I'm asking because, I couldn't get my head around a >> question, which is, should I use only one Wiki for everything ? >> >> To give you an example, I read a lot of books and I take plenty of notes >> and I also write extended documentations about computer science. Now, what >> I'm doing right now, is creating one Wiki per subject. So I have a Wiki for >> programming, one for everything that's related to pentesting, one for >> system related things, one containing all my notes on books etc. >> >> I don't really know if this is going to be sustainble once I'll start >> transfering all the information to TW. >> >> Said like this, it might sound trivial, but I feel like if I mess up my >> '"entry" in TW, it's going to be hard to get everything straight later on. >> >> On Thursday, 26 November 2020 at 20:57:15 UTC+1 springer wrote: >> >>> Cl0d, exactly what I find marvelous about TiddlyWiki is how much it can >>> be molded to very different purposes. I maintain different TW5 projects for >>> different purposes, with different plugin sets and other customizations >>> suited to the purposes of each project. >>> >>> Two things that I suspect I do more than most people are: >>> >>> (1) Make a dynamic table, using the Shiraz plugin, for virtually every >>> important tag. It offers a great compact way to get the big picture on any >>> slice that interests me. I used to use TOC-style tiddlers for this purpose, >>> and that structure still has uses, but the dynamic table is more powerful. >>> I love that I can structure each such dynamic table to focus on the fields >>> that are important for that particular tag. (Of course, you can build a >>> dynamic table around criteria other than tags, but that's my main workhorse >>> use.) I also tend to populate my stylesheet with tag-specific css, so that >>> there are clear visual cues as to which kind of tiddler we're looking at. >>> (I use TW for teaching. So, a quiz question tiddler has a look and feel >>> that differs from an author-specific tiddler or a definition tiddler or a >>> tiddler focused on excerpts from the readings, etc.) >>> >>> (2) Liberally employ a "details" GUI for things that I don't want to see >>> (or don't want to show to students) unless/until it's time to dig in >>> deeper. I use telmiger's details plugin, because it's super-flexible about >>> the contents within the details area (allows any formatting or markup you >>> can think of within the hidden "pocket" area). But to put ordinary text >>> elaboration into a details "pocket," Shiraz's details function is simple >>> and great too. >>> >>> If you'd like to poke around on one of my teaching sites, feel free to >>> visit this link: >>> https://springerspandrel.github.io/tw/ethicsatwes.html#TiddlyWiki >>> >>> Enjoy the adventure of discovering the possibilities! >>> >>> -Springer >>> On Thursday, November 26, 2020 at 2:06:10 PM UTC-5 Cl0d wrote: >>> >>>> Hi there, >>>> >>>> Been using TiddlyWiki for a few weeks now. I'm still learning how to >>>> cope with the enormous potential offered by TiddlyWiki. >>>> >>>> For example, I discovered today that it was possible to create a >>>> dynamic table of content using keywords. >>>> >>>> So I was wondering, what are your best practices, or let's say, >>>> advices, for using TiddlyWiki ? How does your "basic wiki" look like ? >>>> What >>>> plugins and/or custom features do you use ? >>>> >>>> I'm still in a transitional phase, meaning that I'm writing my new >>>> notes in TiddlyWiki to get used to it and I'm at the same time trying to >>>> discover new tools to organize my future wiki's in the best way possible. >>>> >>>> Thanks in advance for every answer. >>>> >>> -- 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/c4476548-f0d4-42d4-8219-41403155a258n%40googlegroups.com.
