||This article contains content that is written like an advertisement. (August 2014)|
|Original author(s)||Boris Kraft & Pascal Mangold|
|Developer(s)||Magnolia International Ltd|
|Initial release||15 November 2003|
|Stable release||5.3.7 / 2 February 2015|
|Type||Content management system|
|License||Enterprise Edition: proprietary EULA,
Community Edition: GPL
|5.0||2013-06-20||New UI based on HTML5 and Vaadin. Framework for creating task-oriented apps.|
|4.5.1||2012-03-13||New templating API, multichannel publishing, JCR 2.0 |
|4.1||2009-06-12||Digital asset management, image generation, commenting.|
|4.0.1||2009-03-06||Standard templating kit.|
|3.0||2006-11-15||Enterprise edition with features such as LDAP authentication.|
Magnolia CMS is Java-based content management system that uses a JCR repository to store, retrieve and search data. In this respect Magnolia is similar to Adobe Experience Manager, Hippo CMS and Jahia which also use JCR. Magnolia uses Apache Jackrabbit, the JCR reference implementation by default. It is possible to use another JSR-170 certified repository implementation such as Modeshape.
In Magnolia, Jackrabbit persists data to a Derby database by default. A light-weight embedded Derby database contains the Magnolia software, configuration, and two demonstration websites in a single download for trying out the system. Production environments commonly replace Derby with an enterprise-scale database such as MySQL, PostgreSQL or Oracle.
Magnolia CMS is distributed as two web applications: an author instance and a public instance. Editors work on the author instance which typically resides in a secure location behind a firewall, inaccessible from the Internet. Editors publish content to a public instance which serves the content to visitors on the Web. The public instance resides in a location that can be reached from the Internet or an intranet. A typical Magnolia CMS production setup consists of at least two public instances. More instances can be created to meet site load and availability needs.
Magnolia CMS has a modular architecture. The system core and features such as the page editor, digital asset management and cache are packaged into separate modules. The module mechanism is also used to package and deploy websites built with Magnolia CMS. The templates, themes and functionality used on a website are split into separate modules.
Modularity allows site administrators to install and uninstall functionality according to a project's requirements. Encapsulating functionality into discrete modules also promotes separation of concerns: one team can work on website templates while another team develops apps, for example.
Magnolia International Ltd. provides commonly used feature modules such as Commenting and Personalization. The user community has developed further modules for specific tasks such as for checking broken links.
Magnolia clients come primarily from financial services, government and media. The system is best suited for organizations that have complex integration requirements and sufficient IT resources to customize the product to their needs. Significant Java expertise is needed to take advantage of Magnolia's open-source architecture and to integrate the CMS with existing systems. The company has indicated on its roadmap to make the product less demanding of Java skills in the future.
The inaugural Magnolia Conference was held in Basel, Switzerland on September 10 & 11 2009. The event attracted more than 80 attendees. The list of speakers included the Magnolia founders Pascal Mangold & Boris Kraft as well as David Nüscheler, JSR-170 specification lead (JSR-170 is Magnolia's underlying technology standard). Impressions of the event have been blogged about, photos have been published on Flickr and talks have been streamed live over the internet
The fourth Magnolia conference was held in Basel, Switzerland in September 2013. It had approximately 200 attendees and took place at the Pathé Cinema.
- Hietala, Antti (2013-06-20). "Release notes for Magnolia 5.0". Magnolia Documentation. Magnolia International Ltd. Retrieved 5 November 2014.
- Hietala, Antti (2012-03-13). "Release notes for Magnolia 4.5.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
- Joseph, Grégory (2009-06-12). "Release notes for Magnolia 4.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
- Joseph, Grégory (2009-03-06). "Release notes for Magnolia 4.0.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
- Natividad, Angela (2006-11-15). "Magnolia Turns 3, Updates Web CMS". CMSWire (Simpler Media Group). Retrieved 2009-01-25.
- Dunwoodie, Brice (2004-11-16). "Magnolia 2.0 Released, J2EE Open-Source CMS". CMSWire (Simpler Media Group). Retrieved 2009-01-25.
- "Obinary Releases Free Java-based Enterprise CMS". CMSWire (Simpler Media Group). 2003-11-20. Retrieved 2009-01-25.
- Hietala, Antti. "Instances". Magnolia Documentation. Magnolia International Ltd. Retrieved 7 November 2014.
- Meier, Christoph. "Modules". Magnolia Documentation. Magnolia International Ltd. Retrieved 6 November 2014.
- Kerkhoff, Marvin. "Deadlink App". Magnolia Community Wiki. Retrieved 6 November 2014.
- "References". Magnolia International Ltd. Retrieved 2 December 2014.
- "Magnolia 5.4 stories". Magnolia International Ltd. Retrieved 2 December 2014.
- Nakano, Chelsi (2009-06-29). "Magnolia Conference Program Finalized". CMSWire. Retrieved 2009-09-14.
- Haderka, Jan (2009-09-10). "Magnolia Conference". java.net blog. Retrieved 2009-09-14.
- "Magnolia Conference Photos". Flickr. 2009-09-10. Retrieved 2009-09-14.
- "Technology track of Magnolia Conference to be streamed live". HeiseMedia UK Ltd. 2009-09-07. Retrieved 2009-09-14.
- Christian, Walter (2012-09-04). "Magnolia will auf Tablets und Smartphones". Inside-IT.ch. Retrieved 2013-02-01.
- Adrian, Bridgewater (2012-09-05). "Magnolia Decouples the CMS for Developers". Dr. Dobb's. Retrieved 2013-02-01.
- Budde, Lars (2013-09-26). "Magnolia Conference zeigt die Potenziale von Magnolia 5". T3n.de. Retrieved 2013-10-18.