Magnolia (CMS)
 |
|
| Original author(s) | Boris Kraft & Pascal Mangold |
|---|---|
| Developer(s) | Magnolia International Ltd |
| Initial release | 15 November 2003 |
| Stable release |
5.5 / 15 November 2016
|
| Repository | git |
| Written in | Java |
| Operating system | Cross-platform |
| Type | Content management system |
| License | Community Edition: GPLv3 Enterprise Edition: EULA |
| 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).
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.
...
Wikipedia