Developing with

Magnolia CMS 5
Nikola Vasilev
18.03.2015
Skopje, Macedonia
Tricode BV
De Schutterij 12 -18
3905 PL Veenendaal
The Netherlands

tel: 0318 - 559210

fax: 0318 - 650909
www.tricode.nl
info@tricode.nl
Agenda

Short Intro in Magnolia 5

Modular Approach
Author and Public Instances
The Tricode Events sample project

1
Short Intro in Magnolia CMS 5

Short Intro Into CMS

Based on Java Content Repository
JCR2: JSR-283
Editions
Magnolia CE: Open Source (GPLv3)
Magnolia EE: Enterprise license needed
Content Apps

2
The JCR Repository

2
Modular Approach

Magnolia CMS uses Maven

Magnolia CMS allows creating of a custom
modules using maven
Maven archetypes provided by Magnolia
Parent project + empty web app
Magnolia standard module
Magnolia Blossom module
Magnolia STK theme module
Magnolia Forge module (community based)

3
A Magnolia Module

Is a Maven module too. But a Maven module is

not a Magnolia module.
Is specified by its module descriptor file.
May have a dedicated module class which may
implement ModuleLifecycle
May install configuration from
src/main/resources/mgnl-
bootstrap/<module-name>.
May have a ModuleVersionHandler.
4
Magnolia Module Structure

5
 Author and Public
Instances
Author instance is where editors work
The author instance publishes the content to the
public instance
The public instance receives the content and
serves that content to the visitors on the Web

6
Author and Public
Instances - Benefits
Security
Loose coupling
Scalability
Flexibility

7
A Typical Configuration

8
The Tricode Events Project
Uses Magnolia CMS 5.3.7 Community Edition
Uses an open source templating project
Magnolia templating kit based on Foundation
framework for Sites
https://github.com/gtenham/magnolia-templating
Responsive frontend framework
Created an events app
Created an events page and events grid
component

9
The Tricode Events Project

10
Questions

11
Follow us:
tricode.nl
facebook.com/tricode
linkedin.com/company/tricode
slideshare.net/tricode
twitter.com/tricode