Magnolia CMS 4.2: Interoperability, Standards, Integrations

Recently, the open source Magnolia CMS (news, site) saw its 4.2 version light that brings hierarchical data modeling, simpler integrations with external data sources, updated STK and a new node-builder extending the JSR-170 standard.


Content Modeling and Hierarchical Data Types

With many debates around content modeling, and the chicken-egg situation around data vs. structure, Magnolia’s move to support hierarchical data types is understandable.

The updated data module now allows users to create multifaceted, hierarchical data sets that can be managed via the front-end user interface.

The ability to build hierarchical data structures lends itself to integrations with CRM, HR and ERP systems, where (thanks to the data import tool) Magnolia can be used as a form of web-based cache for importing data into enterprise systems.

magnolia hierarch data types.png
Magnolia Content Modeling

Once imported into the CMS, external content can be indexed, cached, manipulated and then accessed via the JSR-170 standard or Magnolia APIs.

Updates for the Devs

The updated Standard Templating Kit (STK) is designed to give developers a better set of building blocks for developing websites and online applications. STK v1.2 also features improvements regarding accessibility and SEO.

magnolia stk.png
Magnoia STK View

Code highlighting and line numbering makes it easy to edit a template directly in the browser.

magnolia screenshot_code_highlighting_715px.png
Magnolia Code Highlighting

Magnolia 4.2 also integrated its Public User Registration Module (PUR) for user-generated content with the STK to allow for out-of-the-box creation of new registration forms in a website.

Open Standards and Interoperability

Magnolia 4.2 features a new node-builder as an improvement on the JSR-170 standard. With JSR-283 having recently superseded JSR-170, looks like there’s still more work on Magnolia’s plate.

This tool is designed to simplify module creation and maintenance in Magnolia. The new API can be used to bootstrap or update modules and simplifies manipulation of content through Groovy scripts.

In the new release, there is also an implementation of a WebDAV interface for the file-system-like access and management of remotely stored Magnolia CMS templates.

Check out more Magnolia 4.2 features in this screencast and let us know your thoughts about Magnolia’s newest release.