Item: Magnolia
Rating: 9
Author: Clara Armengol Ramírez

Use Cases and Deployment Scope

We use Magnolia in a project developed for an airline. Specifically, it is used to host the website and all its related content (images, files, and other contents in content apps developed specifically for this) and to host content that we serve headless that is consumed by other source platforms.

Pros and Cons

Api Rest
Page translation
Multisite management

Management of informative messages to the user
Improve performance on heavily loaded content apps
Information and control of the livecopy actions carried out

Return on Investment

Is positive planning through content publishing scheduling
Positive impact on the management of translations of web pages
Positive impact to manage multisites through livecopy

Usability

I think that Magnolia has a very positive character and is that it is quite intuitive when used by users. For example, dividing content apps into groups makes it easier to use and the possibility of enabling or disabling actions based on the roles of the users generates a better handling of the application and a lower possibility of errors.

Performance

When sharing content through api rest if the content app
that shares content has many elements hanging from the same node, this makes performance a bit slow.
However, the rendering of pages is very fluid and when it is a little slower it is due to the loading of large images, and an imaging module is created to manage this.

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, Bitbucket, Jira Software, Eclipse, Postman

Likelihood to Recommend

I think that Magnolia is especially well trained to generate and manage multisite web pages and all their content. Regarding the scenario in which magnolia is less appropriate, I think it is directly related to the management of large volumes of content in the same content apps. Especially when sharing these contents via api rest.

Magnolia is cool

Overall Satisfaction with Magnolia