TiddlyWiki5</a>, a reboot of <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='TiddlyWiki'>
TiddlyWiki</a>, the reusable non-linear personal web notebook <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='History'>
first released in 2004</a>. It is a complete interactive wiki in <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='JavaScript'>
JavaScript</a> that can be run from a single HTML file in the browser or as a powerful <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='node.js'>
TiddlyWiki</a> is designed to fit around your brain, giving you a better way of managing information than traditional documents and emails. The fundamental idea is that information is more useful and reusable if we cut it up into the smallest semantically meaningful chunks –<aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='Tiddlers'>
tiddlers</a>– and give them titles so that they can be structured with links, tags and macros. <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='TiddlyWiki'>
TiddlyWiki</a> aims to provide a fluid interface for working with tiddlers, allowing them to be aggregated and composed into longer narratives.</p><p>
TiddlyWiki5</a> has many <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='Improvements'>
improvements</a> over the original. It is currently labelled alpha, meaning it is working but incomplete. It is the best possible time to get involved and support its future development. You can:</p><ul>
TiddlyWiki</a> can be seen as an extensible representation transformation engine. Given the text of a tiddler and its associated <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='ContentType'>
ContentType</a>, the engine can produce a rendering of the tiddler in a new <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='ContentType'>
ContentType</a>. Furthermore, it can efficiently selectively update the rendering to track any changes in the tiddler or its dependents.</p><p>
text/plain</code> representation for display. The transclusion and templating features of <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='WikiText'>
WikiText</a> allow the engine to also be used to generate <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='TiddlyWiki'>
TiddlyWiki</a> HTML files from raw tiddlers.</p><p>
HelloThere</code> is visible then you'll see it instantly change to reflect the new content. If you create a tiddler that doesn't currently exist (like <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='IntentionallyMissingTiddler'>
IntentionallyMissingTiddler</a>) then you'll see any displayed links to it instantly change from italicised to normal:</p><pre>
$tw.wiki.addTiddler({title: "IntentionallyMissingTiddler", text: "This tiddler now exists"});</pre><p>
If you're interested in understanding more about the internal operation of <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='TiddlyWiki'>
TiddlyWiki</a>, it is recommended that you review the <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='Docs'>
Docs</a> and read the code – start with the boot kernel <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='%24%3A%2Fcore%2Fboot.js'>
TiddlyWiki5</a> is based on a 1,000 line boot kernel that runs on node.js or in the browser, with all other functionality added via dynamically loaded modules.</p><p>
TiddlyWiki</a> environment to allow it to load tiddlers and execute <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='JavaScript'>
JavaScript</a> modules. Plugin modules are written like <code>
different types of module</a>: parsers, serializers, deserializers, macros etc. It goes much further than you might expect. For example, individual tiddler fields are modules, too: there's a module that knows how to handle the <code>
tags</code> field, and another that knows how to handle the special behaviour of the <code>
modified</code> and <code>
created</code> fields.</p><p>
Some plugin modules have further sub-plugins: the wikitext parser, for instance, accepts rules as individual plugin modules.</p><h1class=''>
Plugins</a> are bundles of tiddlers that are distributed and managed as one; <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='Modules'>
Modules</a> are <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-missing'href='JavaScript'>
JavaScript</a> tiddlers with a module type identifying when and how they should be executed.</p><p>
$:/core/boot.js</a> is a barebones <aclass='tw-tiddlylink tw-tiddlylink-internal tw-tiddlylink-resolves'href='TiddlyWiki'>
TiddlyWiki</a> kernel that is just sufficient to load the core plugin modules and trigger a startup module to load up the rest of the application.</p><p>
core/boot.js</code> is executed directly. It uses the <code>
node.js</code> local file API to load plugins directly from the file system in the <code>
core/modules</code> directory. The code loading is performed synchronously for brevity (and because the system is in any case inherently blocked until plugins are loaded).</p><p>