Item: Magnolia
Rating: 9
Author: Manuel Alejandro Lupión Jiménez

Use Cases and Deployment Scope

I am currently working on a project where we make use of magnolia for the creation of an airline website in which magnolia manages all the content of this. This content is consumed in two ways. On the one hand via headless from other front platforms, and on the other from the pages generated within the content manager.

Pros and Cons

Multisite management
Page translation module
API Rest

Message and workflow management
Improve performance on heavily loaded contentApps
Generation of contentApps with different nodetypes

Return on Investment

Planning through content release scheduling
If the data to be displayed on the page is retrieved from a content app with a lot of data load, the page load is affected
The multisite management of the web is much simpler by making use of the live copy module, it reduces the management of the content in the different sites.

Usability

The user interface is fully customizable, allowing the different content Apps to be grouped into sections, which can be given different roles for different types of users. Visually it is easy to use and easy to find the different functionalities that cms provide. The approval flow is simple and effective, allowing to validate the content that is going to be published on the web. Pages edition through components is easy to use and customize.

Performance

The pages generated with the content manager itself are rendered quickly, if these pages have many images to render, we make use of the imagin module which compresses these images with little loss of quality, loading quickly. The response time of the rest api is fast, even if the data to be returned is retrieved from an external system.

Key Insights

Do you think Magnolia delivers good value for the price?

Yes

Are you happy with Magnolia's feature set?

Yes

Did Magnolia live up to sales and marketing promises?

Yes

Did implementation of Magnolia go as expected?

Yes

Would you buy Magnolia again?

Yes

Other Software Used

Atlassian Confluence, Jira Software, Eclipse, Postman, Bitbucket

Likelihood to Recommend

I think that magnolia is prepared for the generation of webs were to show static content managed directly by the cms itself. Due to the internal management that JCR does, I think that magnolia's performance should be improved when the data that is retrieved from the Rest api is very heavy, for example, a content app in which more than 500,000 records are stored.

Magnolia, more than a cms

Overall Satisfaction with Magnolia