TW Plugins

Last edited 25th August 2020


Knowledge Base Workflow

Highlight JS Styles


TW has a micro-kernel architecture where everything is stored as a tiddler. The idea is that the micro kernel can treat everything from core to plugins the same and expose the utilities needed for achieving the desired functionality.

Wiki text goes through a parsing stack, this stack in turn triggers events which bubble up from the parse tree to the DOM, to the store. Most of the code for dispatch is found here. The DOM should be treated as write only, this is comparable to a desktop application with a function like paint(canvas) where it only renders the data that has changed. Reads should come from the internal data store.


Custom components are denoted by the $ prefix. Attaching meta-data such as message allows you to dispatch actions to the parsing stack.