Magnolia (CMS)
Lua error in package.lua at line 80: module 'strict' not found.
| 300px | |
| Original author(s) | Boris Kraft & Pascal Mangold |
|---|---|
| Developer(s) | Magnolia International Ltd |
| Initial release | 15 November 2003 |
| Stable release | 5.4.4 / 19 January 2016 |
| Written in | Java |
| Operating system | Cross-platform |
| Type | Content management system |
| License | Enterprise Edition: proprietary EULA, Community Edition: GPL |
| Website | www |
Magnolia is an open-source digital business platform with a content management system (CMS) at its core. It is developed by Magnolia International Ltd., based in Basel, Switzerland. It is based on Content repository API for Java (JSR-283).
Contents
Major releases
| Version | Date | Features |
|---|---|---|
| 5.0 | 2013-06-20 | New UI based on HTML5 and Vaadin. Framework for creating task-oriented apps.[1] |
| 4.5.1 | 2012-03-13 | New templating API, multichannel publishing, JCR 2.0 [2] |
| 4.1 | 2009-06-12 | Digital asset management, image generation, commenting.[3] |
| 4.0.1 | 2009-03-06 | Standard templating kit.[4] |
| 3.0 | 2006-11-15 | Enterprise edition with features such as LDAP authentication.[5] |
| 2.0 | 2004-11-15 | Usability improvements.[6] |
| 1.0 | 2003-11-20 | Initial release.[7] |
Architecture
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.
Persistent storage
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.
Instances
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.[8] 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.
Modules
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.[9]
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.
At the file system level a Magnolia module is a JAR, a Java file format used to package Java class files and resources (images, CSS, JavaScript) into one file. Deploying a Magnolia module involves copying the JAR file into the Java application server and restarting the Magnolia instance. Magnolia CMS recognizes the JAR file during the startup process and installs the module.
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.[10]
Users
Magnolia clients[11] 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[12] makes the product less demanding of Java skills.
Conference
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.
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
External links
- No URL found. Please specify a URL here or add one to Wikidata.
- Magnolia Community Wiki
