Jump to content

Magnolia (CMS): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
added section "Industry Analysis"; cited RSG vendor analysis for Magnolia
Line 75: Line 75:


==Industry Analysis==
==Industry Analysis==
In its Summer 2015 CMS vendor analysis report, the Real Story Group assessed Magnolia concluding that the platform is something of an anomaly: very developer centric, but not very complex or functionally rich, asserting that developers will like it better than editors or marketers.<ref>{{cite web|last1=Real Story Group|title=Magnolia Vendor Analysis|website=The Real Story Group|accessdate=10 July 2015}}</ref>
In its Summer 2015 CMS vendor analysis report, the [[Real Story Group]] assessed Magnolia concluding that the platform is something of an anomaly: very developer centric, but not very complex or functionally rich, asserting that developers will like it better than editors or marketers.<ref>{{cite web|last1=Real Story Group|title=Magnolia Vendor Analysis|website=The Real Story Group|accessdate=10 July 2015}}</ref>



==Magnolia Conference==
==Magnolia Conference==

Revision as of 12:37, 10 July 2015

Original author(s)Boris Kraft & Pascal Mangold
Developer(s)Magnolia International Ltd
Initial release15 November 2003 (2003-11-15)
Stable release
5.3.9 / 9 June 2015; 9 years ago (2015-06-09)
Repository
Written inJava
Operating systemCross-platform
TypeContent management system
LicenseEnterprise Edition: proprietary EULA,
Community Edition: GPL
Websitewww.magnolia-cms.com

Magnolia is an open-source content management system (CMS) developed by Magnolia International Ltd., based in Basel, Switzerland. It is based on Content repository API for Java (JSR-283).

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 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.

Independent technology analysis firm, the Real Story Group, has compared Hippo, Magnolia and OpenCMS,--another Java-based content management system-- focusing on where these projects substantially diverge in repository architecture, component model, user experience and other functionality.[8]

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.[9] 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.[10]

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.[11]

Users

Magnolia clients[12] 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[13] to make the product less demanding of Java skills in the future.


Industry Analysis

In its Summer 2015 CMS vendor analysis report, the Real Story Group assessed Magnolia concluding that the platform is something of an anomaly: very developer centric, but not very complex or functionally rich, asserting that developers will like it better than editors or marketers.[14]

Magnolia Conference

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).[15] Impressions of the event have been blogged about,[16] photos have been published on Flickr[17] and talks have been streamed live over the internet[18]

The third Magnolia Conference was held in Basel, Switzerland on September 4 & 5 2012.[19][20]

The fourth Magnolia conference was held in Basel, Switzerland in September 2013. It had approximately 200 attendees and took place at the Pathé Cinema.[21]

References

  1. ^ Hietala, Antti (2013-06-20). "Release notes for Magnolia 5.0". Magnolia Documentation. Magnolia International Ltd. Retrieved 5 November 2014.
  2. ^ Hietala, Antti (2012-03-13). "Release notes for Magnolia 4.5.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
  3. ^ Joseph, Grégory (2009-06-12). "Release notes for Magnolia 4.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
  4. ^ Joseph, Grégory (2009-03-06). "Release notes for Magnolia 4.0.1". Magnolia Documentation. Magnolia International Ltd. Retrieved 2014-11-05.
  5. ^ Natividad, Angela (2006-11-15). "Magnolia Turns 3, Updates Web CMS". CMSWire. Simpler Media Group. Retrieved 2009-01-25. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  6. ^ Dunwoodie, Brice (2004-11-16). "Magnolia 2.0 Released, J2EE Open-Source CMS". CMSWire. Simpler Media Group. Retrieved 2009-01-25. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  7. ^ "Obinary Releases Free Java-based Enterprise CMS". CMSWire. Simpler Media Group. 2003-11-20. Retrieved 2009-01-25. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  8. ^ Byrne, Tony (2 October 2014). "Open Source Java CMS: Hippo, Magnolia, and OpenCms". Real Story Group. Retrieved 10 July 2015.
  9. ^ Hietala, Antti. "Instances". Magnolia Documentation. Magnolia International Ltd. Retrieved 7 November 2014.
  10. ^ Meier, Christoph. "Modules". Magnolia Documentation. Magnolia International Ltd. Retrieved 6 November 2014.
  11. ^ Kerkhoff, Marvin. "Deadlink App". Magnolia Community Wiki. Retrieved 6 November 2014.
  12. ^ "References". Magnolia International Ltd. Retrieved 2 December 2014.
  13. ^ "Magnolia 5.4 stories". Magnolia International Ltd. Retrieved 2 December 2014.
  14. ^ Real Story Group. "Magnolia Vendor Analysis". The Real Story Group. {{cite web}}: |access-date= requires |url= (help); Missing or empty |url= (help)
  15. ^ Nakano, Chelsi (2009-06-29). "Magnolia Conference Program Finalized". CMSWire. Retrieved 2009-09-14. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  16. ^ Haderka, Jan (2009-09-10). "Magnolia Conference". java.net blog. Retrieved 2009-09-14. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  17. ^ "Magnolia Conference Photos". Flickr. 2009-09-10. Retrieved 2009-09-14.
  18. ^ "Technology track of Magnolia Conference to be streamed live". HeiseMedia UK Ltd. 2009-09-07. Retrieved 2009-09-14. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  19. ^ Christian, Walter (2012-09-04). "Magnolia will auf Tablets und Smartphones". Inside-IT.ch. Retrieved 2013-02-01. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  20. ^ Adrian, Bridgewater (2012-09-05). "Magnolia Decouples the CMS for Developers". Dr. Dobb's. Retrieved 2013-02-01. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
  21. ^ Budde, Lars (2013-09-26). "Magnolia Conference zeigt die Potenziale von Magnolia 5". T3n.de. Retrieved 2013-10-18. {{cite news}}: Cite has empty unknown parameter: |coauthors= (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Magnolia_(CMS)&oldid=670820923"