Liferay Digital Experience Platform (DXP) vs. Magnolia

Liferay Portal is a framework which comes with a fine grained security/permission model, (Web) Content Management, Authentication and Authorization, outbox portlets with different features to manage content or users. So if any business application has below questions then I can recommend not to use Liferay as a platform.

• Application is big but not content or user driven.
• Application with few static contents.
• Application with batch transactions(DB) i.e. insert , update db records in batch.
• Application with ERP capabilities.
• Application with Big Data support.

Magnolia is very well suited to scenarios where there are multiple end points for content eg. apps, remote devices, websites etc. and with multiple users. Magnolia is very good at working with different "shapes" of content so it's not necessarily all about HTML content for the web which tends to be the default for a number of other products of this nature. This means that it's more logical for people to work with structured data and easier for the applications to sort and manage that content when they receive it.

This works really well when you have multiple team members (often in multiple locations). We've had clients who've had people in twelve European locations with sixteen languages and they can share skills and resources between them but still manage their own content.

Magnolia is less appropriate for SMEs who have fewer digital assets and content. It's not to say that it can't be done but it's more that the budget would not necessarily fit.

Incentivized

• Personalization
• Business to client relationship
• Customer management is better.

Incentivized

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

Incentivized

• Harder to get started
• Enterprise level of options can cause confusion
• Development documentation could be better

Incentivized

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

We are currently using Liferay Portal and plan to keep using it.

We have invested a lot of time and energy into tailoring a solution that works for the company.

We think the new features in v6.2 will help us get to the next level

We also don't have the resources to rebuild a website platform from scratch even if we wanted to

Incentivized

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

Incentivized

Prior to using Magnolia as an enterprise CMS solution, different teams leveraged different website platforms including WordPress, Weebly, and others. While these other platforms may be slightly more user friendly to the content editor, they don't offer nearly the same amount of customization and digital best practices out of the box that are customizable by web development teams like Magnolia does. The other solutions may work better for a quicker/simpler web implementation without technical resources but don't have the depth and breadth of capability and functionality that Magnolia has and fall flat.

Incentivized

• Create a good environment
• Resolution is not so much better.
• Have a long things to do.
• Content management is better off.

Incentivized

• Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
• The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
• The templates makes the whole process easy

Incentivized