Document structuring tags
In order to structure a tree of nodes you can insert single-character (strings with the lenght 1) tagged edges into your tree. Freemind itself doesn't provide edge annotations explicitly, for the edges between parent and child nodes are not editable first class objects. However, this is not a shortcoming. We easily can add annotable "edges" by simply inserting a node between a parent and a child node (thus in fact making the children grand children) and interpreting this intermediary node being an edge.
The map above generates the following example list:
-
Example:
- Title of list item 1. Note that a tree without docment structuring tags will will be serialized as a list of html span elements.
-
list item 2
(title of) first par in list item item 2
second par of item 2
- list item 3
In order to define a node being an edge it has to show one of those characteristics:
- it has a lenghts of exactly one character
- it contains a reserverd keyword like "and", "und", "or", "oder"
- it is tagged with a reserverd icon which allows for arbitrary edge labels
Non-trivial features
Similar to the edge tag "S", which produces subsections recursively to docbook, the edge tag "D" produces self containing sub-documents. The result tree of sub-documents is reflected in the left hand navigation of the resulting html web pages. In it's most simple use pattern semAuth allows to maintain a multi-page web site from one single freemind map.
There is an edge tag "include URI" available, which works not only for other freemind maps, but also for html documents on the web. If you combine a tree of "S" tagged headings with "include" targets you can collect a set of html web resources into one document. In an earlier version of semAuth we have used this feature to collaboratively edit a large EU FP7 proposal with a wiki and arrange the various pages under a sound and deeply nested heading structure (2b refactured).
