We have a bunch of pages which are utilizing the Magnolia Maven archetypes.

For quite some time it was necessary, that the command included an explicit version for the maven-archetype-plugin. According to rsiska that's not necessary anymore.

Please note that the usage of Maven archetype generally has changed a bit.

Let's us create a howTo page, to which we can link from all other docu (or wiki) pages where we use the archetypes.

It should be possible to decrease the amount of Maven related content on the pages which link to the new content should 

Acceptance criteria

Create a howTo page explaining the general usage of the Magnolia Maven archetypes.

If "latest" usage requires updates of the Maven settings or of the file ~/.m2/archetype-catalog.xml these changes must be explained on the howTo page too.

The page explains how people can utilize the Magnolia "sub-archetypes".
(Formerly known as: 
- "An archetype to create STK Theme modules"
- "An archetype to create a Magnolia project (a parent pom and a webapp)"
- "An archetype to create basic Magnolia modules"
- "An archetype to create a Magnolia module to be hosted on the Magnolia Forge"
- "An archetype to create Magnolia modules using Blossom"
)

Page does not contain complete shell log traces - but only key informations, which are important in the context.