That's an excellent question which, unfortunately, likely has answers that 
start with "It depends ..."

Sometimes, it makes sense for a wiki to handle a bunch of things that have 
a lot of commonality/reuse-opportunity.  For example, I have one TiddlyWiki 
that has content that is shared in various contexts/purposes/personalities:

   - Product Reviews 
   
<https://intertwingularityslicendice.neocities.org/CJ_ProductReviews.html?context=ProductReviews>
   - Urban Off Gridding for Laypersons 
   
<https://intertwingularityslicendice.neocities.org/CJ_ProductReviews.html?context=OffGridding>
   - Hydro Bill Cutting for Laypersons 
   
<https://intertwingularityslicendice.neocities.org/CJ_ProductReviews.html?context=HydroCutting>
   - Chromebook: Beyond Web Browsing 
   
<https://intertwingularityslicendice.neocities.org/CJ_ProductReviews.html?context=Chromebook>
   
What originally started with a "how would I create a Product Reviews 
TiddlyWiki" opened up reuse of info about those products into info about 
using those products for various hobby projects.  All kinds of transclusion 
delight going on there.


Other times, the subject is so focused, so unrelated to other 
writings/content with no commonality/reuse-opportunity, that it just seems 
to make more sense to have a narrow-focused/independent TiddlyWiki.  For 
example:

   - ADHD Slice'n Dice 
   <https://intertwingularityslicendice.neocities.org/CJ_AdhdSliceAndDice.html>
   
To me, wedging ADHD-related content/writing doesn't make any sense thrown 
into my "Product Reviews (etc.)" TiddlyWiki.  In a somewhat 
"distraction-free" writing spirit, I wanted that ADHD stuff neatly isolated.


Cheers !

On Thursday, October 22, 2020 at 11:54:41 AM UTC-3, Lin Onetwo wrote:
>
>
>
> Hi, Tony and Tones,
>
> Why multiple wikis? I haven't reached that point, so I wonder the reason.
>
> Wouldn't that make transclusion and linking harder?
>
> I'm now putting different content in different Github repo, and clone 
> then, symlink them into a "main" wiki, and only main wiki have plugins, 
> other "sub-wiki" just have tiddlers.
>
> Sincerely
> LinOnetwo
>
>
> 在2020年10月22日星期四 UTC+8 下午5:42:03<TW Tones> 写道:
>
>> Tony,
>>
>> With only 4 wikis (I have over 100), I would just do any change you wish 
>> to make to one, and manually apply to others. There are neat and easy ways 
>> to do this.
>>
>>    - If in your master wiki you create a tiddler that lists (with links 
>>    of all the things that changed you flag for the other wikis) you can just 
>>    drag and drop them on your other wikis.
>>    - You could export all the changes as a json file and drop that file 
>>    (or import it) to your other three wikis. You can then collect a set of 
>>    changes to drop on a new wiki if you get a 5th.
>>    - One trick I like is to use an iframe in the child wikis, that opens 
>>    the master wikis updates tiddler in an iframe,  you can actually drag 
>> items 
>>    from in the iframe window and drop them on the wiki that the iframe is in.
>>    - Mario has a bundler plugin you may like, one option allows you to 
>>    select if you which to overwrite on import or not. This helps avoiding 
>>    overwitting config tiddlers.
>>    - I have created dragable packages installed in a master wiki that I 
>>    can drag an drop as needed, and another collects all the plugins I come 
>>    across, and I make sure I record the source. I often "disable" the plugin 
>>    in this plugin repository to keep it clean. After dragging a disable 
>> plugin 
>>    to a new wiki it becomes enabled in the new wiki.
>>
>> With a more complex situation like mine I have established workflow 
>> practices. I try and make sure my changes are comparable where ever I 
>> install them and have a quick and easy way to install as I need them. If I 
>> am in wiki 2 and I want to use my smart-code view I install it. I have some 
>> nice easy ways to find such tiddler packages on windows I can share. 
>>
>> The most sophisticated processes would be to bundle changes into a plugin 
>> and add them to a library not unlike the plugins add new plugins. The 
>> library facility allows you to trigger reinstalls. But this is still a 
>> little painful to achieve, and you need to serve the library via a server.
>>
>> I do not know who skins cats but there are many ways to do anything in 
>> tiddlywiki, and a vast majority need only wiki text, widget and macros. I 
>> suggest developing your own solution that you can evolve over time.
>>
>> Tones
>>
>> On Thursday, 22 October 2020 at 19:52:21 UTC+11 [email protected] wrote:
>>
>>>
>>> Hi all, much respect and adoration etc
>>>
>>> My use of TiddlyWiki is via TiddlyDesktop for personal (non-shared) 
>>> information only. I used to have only one wiki which I sectioned off into 
>>> different topics, but I have found reasons over time to split these wikis 
>>> up, so I now have 4 separate wikis (They aren't all located in a common 
>>> folder, but all 4 are accessible at the same time from a single machine)
>>>
>>> Every so often, I take a look at new plugins or tweak my settings in one 
>>> of these wikis, and I find amazing and helpful things that become part of 
>>> the wiki
>>>
>>> You can see where this is going...right: the new plugins and features I 
>>> use are meant to be globally-evolutionary across all of my 4 wikis, two 
>>> examples are: that I started using the codemirror Vim keymap, or that I 
>>> tweaked my theme sizes to be all % based rather than absolute.
>>>
>>> My 4 wikis should all be essentially the 'same' in terms of settings, 
>>> the only things that aren't 'data' ie: content tiddlers, that should be 
>>> different between them is things like the wiki name, or the  favicon logo 
>>> i've set for the wiki that I can see in tiddly desktop
>>>
>>> So....can anyone see a process I could use to keep my settings and 
>>> plugins 'synced' between these 4 near-identically-configured wikis? I 
>>> guess, as with any sync operation, there may be instances where both sides 
>>> have changed (or at least it isn't clear whether a change on one side is 
>>> evolutionary), so some crude visual 'diff' to see what i'm going to update 
>>> would be beneficial (although that isn't crucial I guess, the process could 
>>> just overwrite - its usually just one of these 4 that get's upgraded and I 
>>> want to make the other 3 mirror its settings, but because I haven't had a 
>>> good way to 'sync' settings i'm sure i've ended up in a mess where some 
>>> newer settings/plugins now exist across all 4 wikis)
>>>
>>> thanks enourmously for everything in advance
>>>
>>

-- 
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/901a3d63-0cca-43fb-9af6-dd2f22471981o%40googlegroups.com.

Reply via email to