The topic of this article may not meet Wikipedia's notability guidelines for products and services. (October 2015) (Learn how and when to remove this template message)
|Original author(s)||Boris Kraft & Pascal Mangold|
|Developer(s)||Magnolia International Ltd|
|Initial release||15 November 2003|
5.6 / 15 November 2017
|Type||Content management system|
|License||Community Edition: GPLv3
Enterprise Edition: EULA
|5.6||2017-11-15||Content tags, new REST API delivery endpoint, software BOM for 3rd-party dependencies, OAuth 2.0, Vaadin 8, Log4j 2.|
|5.5||2016-11-15||Definitions app, navigation functions, Magnolia CLI, themes in YAML, many UX improvements; CORE 5.5 uses H2 as the default db.|
|5.4||2015-07-03||Magnolia Templating Essentials, light development, configuration by YAML files, unified resource loading.|
|5.3||2014-06-24||Personalization (p13n), workflow tasks, improved DAM API, content connector, marketing tags manager app.|
|5.2||2013-11-22||REST module, more apps using new Vaadin UI, improved migration process.|
|5.1||2013-10-09||Internationalization (i18n), bulk actions, publishing workflow, customizable apps.|
|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 a 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 the H2 database by default. A light-weight embedded H2 database contains the Magnolia software, configuration, and two demonstration websites in a single download for trying out the system. For production environments other databases such as MySQL, PostgreSQL or Oracle can be used.
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 that a file-system based development approach makes the product less demanding of Java skills.
Magnolia Conference is an annual event for CMS developers and digital marketing users. The conference is a place to meet other users, share best practices, and learn about product updates. A technical presentation track targets software developers, focusing on integrations and CMS implementation cases. In 2015, Magnolia added a digital business presentation track where talks focus on content challenges that businesses are facing and how they are using the product build their brands on the Web.
The conference also includes a community unconference where attendees themselves are responsible for proposing, voting for and presenting talks which everyone is free to choose to attend.
Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.