Understanding TiddlyManual format

9th August 2017
The manual is written in a novel format which is very easy to use; like most things, it takes a little getting used to to get the best out of it.

What's on my screen?


Look at How to read this Manual or take a Video tour of the AMBIT manual for an explanation of all the buttons and features on your screen that will help you navigate and read material. N.B. IT IS REALLY WORTH LOOKING AT THIS, as the format behaves slightly differently from conventional websites.

Getting it to work in a big organisation


You may have to make a few calls and changes to get the best out of a TiddlyManual in a large organisation that has old I.T. (such as the NHS!) - these things will get easier over the next year or so, but are surmountable now. See Organisational support for the technology to run TiddlyManuals.

Editing a local version


Local teams can open their own version of a tiddlymanual, which includes all the content curated by a central source (such as the AMBIT project at the Anna Freud Centre) and they are encouraged to Edit their local version, to "tune" it to local needs, and local culture. There is a Video introduction to editing a tiddlymanual as well.

Technical Glossary


All the technical terms and bits of the TiddlyManual you are likely to wonder about are tagged with the title of this tiddler (Understanding TiddlyManual format), so just look at the Show references and info panel for this tiddler (above, to the right of the title) to see all the Sub-topics under this heading.

Who wrote which bits?


TiddlyManuals encourage local teams to incorporate the core content of a manual (which is curated centrally) but to add local customisations and and adaptations - a process we refer to as Manualization.

It is worth knowing how to find out Who wrote which bits?

Explain TiddlyWiki?


Have a look at TiddlyWiki to get more information on what makes it tick.

Changing the interface


There are almost limitless ways to Change the interface of a Tiddlywiki to suit tastes, and some of the simpler ways to do this are described.

Most significantly, this is a Dynamic, adaptive Manualization that is not a static document, delivered "once and for all" from distant authorities, but which functions as a collaborative "work in progress" - integrating local expertise, creativity and service-user feedback into team-based edits to the local TeamTemplate.

Understanding these things will help you get to what you want or need faster.