Make TiddlyWiki your own - discussion

Further on a Make this your own process.

Often the only way to make simple things, especially when based on technology, we need very good technical solutions to do the hard work for us, appear invisible, yet deliver the results.

My key example of this I am developing is part of The essential editions of TiddlyWiki and a sharable make-tiddlywiki-your-own facility.

I have started here with this alpha [Edited to link to Edition Topic] Essential Editions: Personal Notebook edition - development and feedback once downloaded it can see it is no longer at the published address and can a “run once” guide to do various setup things.

Possible Setup things
Once a user has downloaded a Wiki the are making their own we could facilitate the following;

  • Get them to close the source Wiki so they dont make changes there, and use their new local wiki.
  • Open the wiki with a link with a named target eg wikiname, so use of the same link opens it in the same tab, rather than multiple tabs, where one can save over the other.
  • Provide a tool to create a bookmark even a smart bookmarklet to the same target (details later)
  • Possibly use a cookie on the source wiki to store information about their own localised wiki
    • A “You have installed this wiki locally” message perhaps even with a link.

Then we need to guide/address the save/autosave issues and mechanisms from the default method through to others.

  • Remember we want the first, and subsequent experience to be simple and smooth
    • What do we use here? Default saver, File Backups add on, direct to Timimi?
  • Once they are getting value from one or more tiddlywikis we can point them to other smarter options like TiddlyDesktop, bob, TiddlyServer, WebDav implementations that give them the freedom to create and share wikis at least on the Local network or between devices.
    • Ideally the various editions will guide users on how to get their edition into any one of these solutions.

You can see from the potential complexity here I think we need to collaborate and build a shared path to enable this. Especially once we include methods for mobile devices.