I would like to start a discussion here about providing a smooth and simple as possible workflow to New and Naïve users to “Make TiddlyWiki your/their own”, or a solution we develop for them.
TiddlyWiki.com suggests you download empty.html but I believe this is really an edition for experienced users to obtain the minimal build, from which to construct a solution. Although essential it is not the best introduction to tiddlywiki, perhaps we need a separate “Learn through Play” option.
But I would like this thread to focus on
The quickest and easiest ways to obtain TiddlyWiki so you can experiment or build.
- I believe The most critical and potentially confusing is how to guarantee you can save your changes back to the same file / tiddlywiki you loaded.
- Whilst this can be somewhat complicated by all the browsers and Operating systems we can go a long way to detecting the users current browser and going from there. Use the KISS principal “Keep it Simple Sweetheart”.
- Sure, near at hand is the sophisticated and comprehensive multi-browser, OS and server options but they need come later, when someone is committed.
It seems to me there are three key needs to Make TiddlyWiki your own;
- First time users and visitors to TiddlyWiki.com and other “community sites” - this is the gateway to the “TiddlyWiki Platform”. This approach can include play, learning, building and documenting.
- First time users and visitors to our custom wikis, who may only care about our published site;
2.1 Perhaps you encourage them that they make your edition their own - so they save their own content or data. The solution in #1 should be transferable to other these TiddlyWikis. - Other TiddlyWiki’s will be server based, interactive, use in browser memory, local storage or databases. These need their own processes and procedure’s, however it would be helpful if we built a set of resources to support such solutions, like standard user “login” processes, using across multiple devices . This will make what “one learns on one tiddlywiki, transferable to others” and also reduce the implementation time for designers.
What if every wiki that wanted to, had the same “Make this my own” button ?
TiddlyWiki is full of potential to detect browsers, store information, display conditionally, undertake Q&A, provide links eg; Directly to an Edition, browser Add On, instructions etc… I have always felt TiddlyWiki can be a superior workflow tool with options and feedback, perhaps even better than confluence and other solutions. Why not put tiddlywiki to work for its own good?
So I will post a reply shortly, with some tricks and features we can make use of to this end. I hope you can contribute your ideas so we can progress this and make TiddlyWiki easy to make your own, for everyone.