I keep a number of wikis. One to document customization on my PC system (Linux), one to document customization of my wikis, one to hold shared libraries (stylesheets, macros etc.), one for personal notes, one for my journal and recently one for trips planning. Do you follow any practice similar to this or do you have a single all-encompassing wiki?
I run the Node.js edition of TiddlyWiki and all my plugins are in a common folder, shared by my other wikis.
multiple wikis, because generally I prefer to organize my tiddlers in hierarchies, and with many tiddlers I end with overloaded namespaces in tiddler names. I have a main knowledge base wiki (static data) and a main TODO wiki driven by Projectify (I call it dynamic data). Once a topic grows big enough, it gets its own wiki and relevant tiddlers get moved.
Currently it’s only one wiki (second brain, task mgmt, shopping lists, journal, etc.). I also run the node.js version with some integration via node-red (send tiddler as mail, telegram bot as quick input channel and to retreive from tiddly when remote). Even after a few years of using it the single wiki works fine. Am thinking about an archive wiki though
I’m thinking that with separate wikis inter-wiki linking may be not straightforward, but if they’re loaded at startup for example, using a tiddlywiki.info entry, then linking is easier. I do not have any experience about this and I’m just guessing.
Several wikis.
-m
All of my wikis are maintained separately for non-professional purposes catered to specific hobbies. Most are public on TiddlyHost. Of the ones I actively (try to) maintain, I have a personal website, a searchable archive of old web graphics, and a wiki for hosting one of my creative projects. Of the private ones, I’ve put the most work into a searchable archive of artwork I and others have created for that creative project with thousands of images tagged and transcribed. Before I started using TiddlyHost, I used TiddlyDesktop, tw5cloud for Dropbox, and some other solutions for managing older projects.
I’ve pondered the idea of a centralized wiki to interconnect at least some of my projects, but the need hasn’t really risen yet to motivate making one. At some point I would like to create an offline wiki to organize my computer files, though. When optimized and maintained well, TiddlyWiki is incredibly fast at finding very specific things out of large collections compared to Windows 10’s native file search.
Yes, a number!
Of course, there is one “catch-all” for non-work stuff that’s not otherwise structured (miscellaneous notes to self, info I need not to lose, notes while sifting though some purchase or travel decision, etc.), but anytime there’s a kind of ongoing activity or hobby or project that has its own “there there” in my life, I tend to make a separate wiki. I enjoy customizing each one with palettes and other stylistic differences that helps me recognize instantly which wiki is loaded up. Often a purpose-specific wiki will want some plugins rather than others, and this way I (try to) avoid having one wiki with too many plugins.
Perhaps some would find this reminder helpful: if your potential wikis overlap around some shared batch of tiddlers, where you don’t want proliferation of these (with potential emerging edit-variants to track down) across multiple files, you can load external tiddlers (on startup, or as needed).
That’s what I do with bibliographic tiddlers; I have one master bibliographic database wiki, and lots of other wikis that pull a subset of tiddlers over, based on filter conditions specific to the downstream wiki.
I prefer one Wiki for both personal professional. But I’m a simple guy.
If I need a new “empty” for a specific occasion (a presentation and so on) but has my custom settings, I’ll dump all of the tiddlers using Advanced Search.
I save tiddlers as a JSON based on categories. One way to do that is to name it using the Query filter and using “-” in place of the “[]” etc. Might be something like: [search:tags[]prefix[202601-]] which becomes: search-tags--prefix-202601-.json.
If you need security, you can 7zip those tiddlers and put passwords on them. Another great use of TiddlyWiki is to have lists of the files that are hidden in your zip archives. A card catalogue of sorts: select the files in the folder and copy the path for all of them in one go. Paste them into a tiddler and away you go.
I’ve tried multiple Wikis, but lost track of where everything was. Maybe you have a way around this problem. But for me, TiddlyWiki is at the core of my whole life and has been for 10 years.
All of this may not be new to you. If it was not helpful, I apologize. My posts are targeted to like-minded simple uses for TiddlyWiki.
Have a nice day. Don’t fight and try not to get kicked.
I am a big single file mulitple wiki user although my primary organiser wiki is the key. truth is I have a dozen relating to tiddlywiki itself.
A professional career including knowledge and information management no doubt made this easier to seperate content but I have also experimented with a lot of interwiki tools including bookmarklets and a searchable library of json files with a custom $browser, a package management config and more make it easier.
they tend to be project or function based with a set of resources wikis that I know where to go when needed.
quite a few of my wikis a proof of concepts that test the extremes of what can be done with tiddlywiki and it is wise to seperate them from wikis I depend on.