Try Magnolia Extensions
are experimental Magnolia modules originating as side projects from our demos, support, our clients' requests, and last but not least interest from the Magnolia Team.
The extensions such as the Search Engine Optimization (SEO) module or the Single Sign On (SSO) module provide very useful functionalities to the existing official Magnolia modules.
While getting limited support, usually directly from an extension's developer, the extensions are described in their own separate EX Documentation Space and are covered by our standard Magnolia License Agreement, which is friendly and includes access to the source code.
4 Comments
Niels Hardeman
The Stories app seems to be missing in this overview.
Martin Drápela
Dear Niels,
the Stories app is in fact a submodule of the Content editor module, see here Content Editor module: Module structure, so that's why we do not list it here separately.
Best,
Martin
Frank Messie
Perhaps a question with an obvious answer about the version numbering of modules.
When I select Magnolia branch 5. 6 the contacts module shows version 1.6.
Does this mean that this Contacts Version 1.6 is compatible (and tested) with Magnolia 5.6 ?
Christoph Meier
Frank Messie
Basically yes.
All modules that are bundled are tested together with the modules with which they are bundled. (öhm ... I hope that was understandable).
Also note that for every major branch - 5.4, 5.5, 5.6 and soon 5.7 - we also release minor versions.
In a minor release - also named maintenance release - typically the Magnolia bundle versions are raised - and typically for some but usually not all bundled modules the versions are raised too.
If you want to know the vesions precisely - check the BOM file of the bundle in the exact version you are interested in.
Examples:
Note that the EE BOM inherits from the CE BOM of the same version. And for the EE BOM you may lack the permission.
BOM files of all versions are on our GIT repository. Every release is "tagged" with a GIT tag.
I hope this helps,
cheers,
Christoph