Magnolia CMS 5.0 - Milestone 3

The new UI architecture and framework is built! Finally we have a solid fundament and feel that we are on the right path. We urged to have a more final AdminCentral though, but decided not to rush into anything and didn't want to build upon something half-baked. As a result we can now present an extraordinary customizable and pluggable UI.

Watch our technical video featuring a short demo of the milestone 3, some architecture slides and a sample customization module:

In the next milestone we will focus on the page editing and templating. Naturally we will also catchup on the AdminCentral and dialogs to round over the impression.

Magnolia CMS 5.0 - Architecture manifests

After few weeks of Magnolia 5.0 development and again focussing on the UI architecture, I have finally assembled slides and diagrams to give insights into our doing. Some of the concepts are very drafty but most of them are already reflected in the latest codebase. When we deliver the milestone 3 end of march, we hope that the base architecture will be set in stone ;-)

Magnolia CMS 5.0 - Architecture


Magnolia CMS 5.0 - Overview
An other high level presentation describing our goals and plans can be found here:

Groovyness - the agile paragraphs

Back on track. After releasing Magnolia CMS 4.4 my mindset moves back to Magnolia 5.0. While playing around with groovy to merge the changes from the 4.4 branch back to the trunk I came up with a idea which I would like to share and get some feedback from you.

Using a groovy builder (DSL) we could make the paragraph definition very concise

• include the dialog definition in the paragraph definition
• add a closure for rendering the content

example: text and image paragraph

What we get:

• no configuration (update, ...)
• a single concise definition (all in one place)
• agile

Note: this will not replace any other ways of defining paragraphs or dialogs its just a groovy alternative. But since we allow pragmatic registration of dialogs, paragraph, ... in Magnolia 5.0 such an implementation should be rather trivial.