...

This rule seems pretty solid to me.

2) Relevant

Make things become 'obvious' through clarification: not just repeat the obvious. Keep the concept map relevant. Just because a topic is worth mentioning on a map doesn't mean that it deserves a map for itself. A good rule of thumb regarding the specificity of a possible map is 'take a step back'. Go up a level. Does a component merit a concept map? Or should component simply be a concept on a concept map called Template? Obviously everything is relevant, but we don't want to include everything! Instead of 'relevant' we could say 'appropriate'.

Again, this rule seems pretty solid.

3) Relational

Make things become 'obvious' through clarification: not just repeat the obvious. Second level concepts on a Magnolia CMS Concept Map should be no more than one step removed from the central-concept. There's nothing wrong with having sub-levels of conceptually related topics, but a concept is in Magnolia CMS, then that concept is in some way related to everything else in Magnolia, so there's no need to expand the conceptual circle too far.

...

• Colour-coded nodes indicating that a page or component exists in our documentation.
• Coloured lines, firectional arrows for dependencies or to indicate hierarchy. So Template > Component, Page, Area > Web page
• Hover over augmentation. (User hovers over a node and suddenly it explodes to life.)
• Click nodes. Click to open and close a node. Move from one node to another, so....

To achieve these would probably require a phased approach.

Phased Approach

Phase 1 - Static Concept Maps

...

Mind maps become interactive and link to Magnolia CMS documentation, wiki pages, other mind maps etc. through basic hyperlinks.

Use case

Sitting on the U-bahn on her way to work, the young CTO of a company that deals in car components for distribution in the European market is checking out the Magnolia-CMS Webpage to learn more. The company is growing and more and more detailers are using the web to make orders.  The company website (solid, dull, stad but funictional) is accessed by numerous dealerships and they don't all require the same kinds of products. There have been complaints about time being wasted having to look through product lists of irrelevant. Worse, although the distribution has a central office, there are distribution points distributed throughout the markets - and in each dealership there are users that need acces to the CAR PARTS R US website and associated sites to update the site to indicate if products are available etc.. She needs a solution that can handle what is decoming an increasingly messy situation...

Time is short, the meeting is half an hour. She is tired, a bit grumpy and the U-bahn unusually busy.  Text looks like ants crawling across a page. She needs something very visual, immediate - something that gives a good highlight, but that can lead to further information is she needs it. As her perfectly manicured fingers lighty tickle the shiny tablet screen, she smiles as with the ease of an high-end app, she check out the neat interactive concept map provided in the documentation section of the potential supplier.... For example on the CAS module page the first thing a viewer sees is a concept map with the salient points/ideas related to CAS, they can then use the map to navigate to the LDAP page or to a page about ACLS.

User clicks CAS on the LDAP Concept Map...

... is taken to a CAS Concept Map

From here the user can navigate to the LDAP page or to a page about ACLS.

Phase 3 - Fully Interactive Magnolia CMS Concept Map

...