• Java content management solutions in the 2000-2010 era tended toward heavy-weight, hard-to-use, hard-to-develop "enterprise" systems.

• Over the last few years a new generation of content management systems (CMS) have entered the market based on better-faster-lighter principles.

• To put it another way - what does a modern CMS built for a world of Continuous Delivery look like?

• In this session we'll talk about requirements for a modern CMS solution, including support for mobile, responsive design, and targeted content for specific application needs. We'll also talk about requirements for ongoing maintenance, including operational and development complexity.

• We'll pay particular attention to the issues and strategies for migrating off legacy enterprise (or custom internal!) CMS systems to these modern CMS solutions.

• This will be an interactive session - bring your war stories and your aspirations!

Java CMS in

2015

Will Iverson

CTO, Dev9

• CTO, Dev9– Previously Apple,

Symantec, SolutionsIQ

• Java since 1995

• Four Books, Numerous Articles

• Numerous CMS Evals, Implementations

• Custom software development firm – Based just outside Seattle, Washington

• We build custom software solutions based on Continuous Delivery– Processes & tools based on combination of Lean & heavy use of

automation

• Typical projects– CMS implementation!

– Java & .NET-based web services at scale

– SQL, NoSQL

– Variety of client-side technologies • AngularJS, Android, and iOS.

– DevOps implementations, including Docker

• CMS Fundamentals– Types of CMS

• CMS Architecture– Modernization & Upgrades

• Picking A CMS– Platform

– Evaluation Process

– Contenders

• Demo[s]

• Q & A

FUNDAMENTALS

• Core Ideas– Publishing content is a process

– Structure allows for reuse

• Next Steps– Internationalization & Localization

– Multiplatform (Print, Online)

– eCommerce

– Collaboration

– More…!

• Vivamus sodales

• "Neque porro quisquam est qui dolorem ipsumquia dolor sit amet, consectetur, adipisci velit..."

• Lorem ipsum dolor sit amet, consecteturadipiscing elit. Proin tincidunt eleifend purus, eumaximus lacus placerat eu. Suspendisse velvolutpat dui. Maecenas porttitor ut diam quisullamcorper. Curabitur suscipit libero sit ametipsum bibendum, id varius felis tempus. Morbiturpis nibh, convallis pretium elementum eu, pretium nec nulla. Quisque quis ornare ante, euscelerisque magna. Sed laoreet ullamcorpernibh, vitae dapibus neque viverra ut.

• Proin Malesuada

• Maecenas Gravida

• Title: Vivamus sodales

• Intro Pull Quote: "Neque porro quisquam estqui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..."

• Body: Lorem ipsum dolor sit amet, consecteturadipiscing elit. Proin tincidunt eleifend purus, eumaximus lacus placerat eu. Suspendisse velvolutpat dui. Maecenas porttitor ut diam quisullamcorper. Curabitur suscipit libero sit ametipsum bibendum, id varius felis tempus. Morbiturpis nibh, convallis pretium elementum eu, pretium nec nulla. Quisque quis ornare ante, euscelerisque magna. Sed laoreet ullamcorpernibh, vitae dapibus neque viverra ut.

• Author: Proin Malesuada

• Editor: Maecenas Gravida

1. We built a custom website

2. We have basic content publishing

technology

– Now what?

3. Differentiate!

• Repository

• Structured Editing

• Specialized CMS

• Full Collaboration

– Repository only

– Only interesting if you

want to build your own

– Examples: Apache

Jackrabbit + Apache

Sling

– ~10-20MB

– Repository + editor +

publishing

– Codename: WCM

– I think what most

people mean by CMS

– ~10-50MB

• Variety of targeted needs– Arguably includes

most popular blogging suites

• “You’ll know it when you see it”

• ~10MB-500MB+

– E.g. Wikis, Discussion

Boards, Document

Libraries, more…

– Codename: ECM

– E.g. SharePoint, Alfresco

– ~1-2+GB

HOW A CMS

WORKS

CMS Server

UI Code (JSP)

BrowserIntegration Code (Java)

Repository

HTTP/HTML

CMS Server

UI Code (JavaScript, AngularJS)

Browser

Integration

Code (Java Microservice)Repository

Mobile

?

REST/JSON

• Build your own!– Really easy to make a text box

render…

– Really easy to build a custom app that

duplicates existing CMS…

• Special snowflake!– All modern CMS systems highly

customizable

– Special snowflake Focus on dev

experience

• Save on licensing!– Really good open source options

• The only person who loves a

custom CMS is the person who

built it.– …And they probably quit.

• Responsive design

• Mobile apps– Native

– Hybrid

• Personalization initiative[s]

• Custom integration is hard– Bad edit/debug cycle, poor repository, undocumented…

• Testability

• Ability to find/retain staff

• Long term TCO– Expensive licensing for legacy system

• Lend themselves to dual systems

• Usually easier than you would expect

– Like cleaning out your garage

• We have done many, happy to discuss!

– Careful attention to risk management

YOU HAVE TO

CHOOSE!

• Platform

• Evaluation Process

• Contenders

PLATFORM

SELECTION

• You have to pick something you can

deploy.

• No, really.

• Structured

• Refactoring

• Integration

• Well known

• Broad professional skill set

– Dev, IT know it

• SquareSpace

• Wix

• Many, many more…

• WordPress– JSON/REST API

– http://wp-api.org/

• Drupal– https://www.drupal.org/documentation/modules/rest

– https://www.drupal.org/project/restapi

• Joomla

• Magento

• bolt.cm

• octobercms.com

• Already Strong Microsoft Shop

• SharePoint

– REST API http://bit.ly/1zaKm7U

• SiteCore

– Sample at http://bit.ly/1DlDQKI

• Too many to count.

• New one every week.

EVALUATION

PROCESS

• Starting Point– Existing CMS or greenfield?

• Broad Type– Structured Editing, Specialized(?), Full Collaboration

• Specific Requirements– Circular problem!

• Expected Customization– Be Honest

• Test Strategy– Automation?

• Total Cost– Dev, Test, Deploy, Patch…

– Assume new patch every week!

CONTENDERS

• CMSMatrix– http://www.cmsmatrix.org/

– Reviewed [at least briefly] ~240 links

• Java-Source.net– http://java-source.net/open-source/content-managment-

systems

• Wikipedia– http://en.wikipedia.org/wiki/List_of_content_management_

systems

– Much shorter, cleaner list

• Can a dev build with it fast?

• Can you test it easily?

• How hard is it to upgrade?

• Does it do what you need?

• How much does it cost?

• Deployment

• Configuration Management

• Development

• Edit/Compile/Debug Cycle

• Modern JS Framework support (e.g. AngularJS, Ember)

• Native mobile support (iOS, Android)

• JSON/REST-friendly

• WebDAV support?

• Lean & Fast– BrightSpot CMS

• HippoCMS

• MidMarket– Magnolia

• Enterprise/Collaboration– Alfresco

– Nuxeo

• Ones that I like– Highly subjective

• Always need to conduct eval for YOUR needs!

• http://dotcms.com/– Quasi-open source

• http://www.ekinocms.com/– But their home site is running on PHP

• http://www.jahia.com/

• http://www.liferay.com/

• http://www.opencms.org/en/– Docker image!

– Prior successes

• http://www.infoglue.org/

• http://entermediasoftware.com/

• https://enonic.com/en/Home

• Hotels– http://www.mediaconcepts.com/solutions/content-management-system.html

• Schools– http://omniupdate.com/

– http://www.terminalfour.com/

• Newsroom– http://www.atex.com/

• Governments– http://www.revize.com/

• Globalization: i18n & l13n – http://www.sdl.com/products/tridion/

• http://www.brightspotcms.com/

• Small, light-weight, good looking

• Describe content types via Java

– Dynamic reload FTW!

• Lean, dev friendly

• Modern design

• http://www.onehippo.org/

– https://blogs.oracle.com/geertjan/entry/hippo_

development_in_netbeans_ide

• http://www.magnolia-cms.com/

• Based on Spring, REST, WebDAV

• http://www.alfresco.com/

– http://docs.alfresco.com/5.0/tasks/alfresco-sdk-install-quick-start.html

• Now Maven based

• In use by some big names

• Has REST API

• Pretty darn big

• http://www.nuxeo.com/

• Lots of Continuous Delivery, Agile Focus

– Massive installer

– Really an ECM package

DEMOS

Q&A