This article describes how to create a complete Magnolia environment that contains an Author environment and two Public environments which are served via a HAProxy load balancer.
In this blog article we have a look at some of the options available for applying translations in Magnolia.
Website redevelopment and cloud infrastructure delivery for Generali Insurance, using Magnolia CMS and Amazon Web Services.
This article provides a high-level overview of the personalisation capabilities available in Magnolia CMS and explains some related concepts.
Global insurance firm, Assicurazioni Generali, have re-launched www.generali.co.uk with support from Priocept.
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.
We often get asked whether Magnolia's Standard Templating Kit is the best way to go when planning out a new Magnolia project. In this article we discuss some of the pros and cons associated with the STK to help you decide whether it fits the requirements of your Magnolia project.
In this article, we look at the difference between a CMS and a content repository, and how and why you might decide that a content repository is the right technology for your expanding content requirements.
This example follows a site editor making minor changes to a page in a Magnolia CMS website and a site publisher reviewing that change before publishing it for public viewing. It uses the Magnolia CMS Demo Area, hosted by Magnolia International to provide an area for exploring and practising.