Java-based Open-Source CMS System Selection

CMS Overview

For the website CMS system, PHP-based mainstream, such as Drupal/joomla, which is also widely used in mainstream Virtual Machine providers.

However, if you have a Java team or the project's goal is to build a content management system for enterprise networks, it is appropriate to choose a Java-based CMS system.

There is a significant difference between the PHP-based CMS system and Java CMS,

Java-based CMS usually applies the content architecture to JCR specifications, such as jackrabbit, modeshape,

The CMS architecture of PHP is based on RDBMS specifications, mainly MySQL. In general, Java is more object-oriented in content management.

1. Walrus

Http://sourceforge.net/projects/walruscms? Source = DLP

A cms Based on the Spring framework does not have a separate background. After logging on to the console, the administrator can directly edit the foreground page. What you see is what you get, there is a release package that binds jetty.

2. Magnolia

Http://www.magnolia-cms.com/

Mature CMS system, detailed documentation, release packages bundled with tomcat, responsive design, support for both PC and mobile terminals, content architecture on jackrabbit.

The installation package includes public instance and authoring instance, that is, website front-end and background content management. One authoring instance supports multiple public instances.

Provides multi-type page templates, hierarchical content management, and powerful visual editing functions, complete access control (ACL) implementation.

Magnolia is good in terms of website content management, but its architecture is somewhat outdated.

Edit the background page:

Background Article editing page:

3. jahia

Http://www.jahia.com

Complete functions, support multiple display channels such as PCs and mobile terminals, and responsive design. Here is a comparison article with Drupal.

Http://people.cis.ksu.edu /~ Mrudula/talloju_690.pdf

However, online document access is quite slow (access time)

4. Hippo

Http://www.onehippo.org

Provides online demo at the front-end of the website. demo at the back-end management requires an open-source project of enterprise-level application quality, and supports both PC and mobile terminals.

By separating the presentation layer and content and Content Context, the architecture is designed to achieve multi-channel content publishing.

5. dotcms

Http://dotcms.com/products/demo/

Provides a complete front-end and back-end online demonstration, based on the SSH architecture, powerful background management functions, flexible

Conclusion

If you prefer the Spring framework, dotcms/walrus is preferred. If you consider the features, availability, and ease of installation, Magnolia is preferred.

By iefreer