At Priocept we work with a number of clients with a global presence, where various local country sites often share much of their content and structure, but are also very different in certain sections. In this article we explain how to effectively combine content reuse and content differences, using a CMS inheritence model.

Upgrading your Magnolia 5.3.x project to a newer version 5.4.x should be an easy task, but even if we are speaking about two versions which are only 18 months apart, there are tweaks that have to be done, even for this small upgrade process.

Priocept has recently been working side-by-side with two alternative cloud computing service providers: Rackspace and Amazon AWS. This gave us a great opportunity to compare the details of both providers. On both projects the software platform was based around Magnolia, a Java based CMS.