Multiple linked single wikis

#1

Hi All,

I am thinking about the final architecture of my guns wiki (30,000 tiddlers or there abouts). Now the information is split into two set: the landing page and the rest of the information (history, technical, etc).

In most cases, I expect the user will want to see tha landing page and then the local history description, maybe with access to a live map of the area. The rest of the information is really research/academic information.

So I am thinking, is there a way of splitting the wiki into two and have active links between them so that when on a landing page for a gun, if the user wants some of the additional information, we show him the tiddlers from the second wiki (maybe in a new window)?

I assume this will speed up load time for the landing page wiki as we don’t need to load all that academic stuff up front.

I know I can use a full URL to open a particular tiddler in the second wiki but what could we do with wikilinks? I am thinking something along the lines of canonical_uri but in this case loading the tiddler from the second wiki.

I don’t want to use node.js wiki’s as my user is technically naive.

Am I crazy of what?

bobj

#2

You could generate a list of all tiddlers you link to in the sidewiki, then use a modified version of the link widget, which is what happens to simple links, and redirect those in the list by constructing a html a record, use a target of a fixed name so they open in the same window/tab unless r-click open in new tab is used.

  • Other wise just change them all to point to their new home.

Although it would be nice if you could pull them in one at a time.

#3

This thread is focused only on loading at startup, but might have ideas you could use to fetch them dynamically: New Features in TiddlyWiki 5.3.0: HTTP request and deserialize operator.

#4

We are able to create single file wikis, that use “lazy loading” without a Node.js server backend. But it needs a special build configuration. You can create your wiki using a local client server configuration or a single file wiki.

Before publishing, a build step will be needed, that extracts the “research” content from the wiki and saves .tid files to an eg. text directory. The build process will also set the _canonical_uri field and removes the text field from the research tiddler.

The disadvantage is, that full text search will not work anymore. So you may need more search terms in tiddler fields, so users can find something.

Just some thoughts. At tiddlywiki.com we use that mechanism for the “Alice in Wonderland” tiddler.
If you open the dev console F12 and select the Network tab. Then open the tiddler “Alice in Wonderland” you will see, that the text will be dynamically loaded.

#5

Thank you people for your thoughts. Much to think about yet but start early I always say.

bobj

#6

I have been thinking about things further and have come from al alternate direction.

Maybe we still have two wikis, one the full bore, all tiddlers, etc and the second just the landing pages only. Then allow the user to click a button when on a landing page to navigate to the second wiki to the identical place. So the casual user gets quick access to the landing page info for their gun of interest but if they want to explore, follow links, etc, they have to go to the second full bore wiki.

In front of a gun, the user is directed to the landing page wiki unless they are a researchers and have previously accessed the full bore version.

Bobj

#7

Would the innerwiki plugin do the job?