
What I value most about Liferay is its ability to go beyond building a website or portal and become a foundation for solving broader enterprise digital challenges. In real projects, content, customer journeys, business processes, integrations, and user permissions are rarely isolated concerns. Liferay gives us the flexibility to bring these pieces together without forcing the entire solution into a rigid product model.
I also like the direction the platform is taking. The evolution toward a more structured, headless CMS through the CMS 2.0 initiative is particularly interesting because content should not be tied to a single website or presentation layer. The ability to create reusable content and deliver it across different channels gives enterprises more architectural freedom and helps separate content management decisions from front-end technology choices.
What makes the broader product direction even more interesting is the development of capabilities around content marketing, data, sales, and commerce. The Content Marketing Platform can help connect content planning and campaign execution, while Liferay Data Platform brings account intelligence and customer engagement signals closer to the digital experience layer. Digital Sales Room capabilities and B2B commerce also open up opportunities to connect digital engagement with actual buying journeys.
For me, the important point is how these capabilities can work together. An enterprise should be able to connect content, customer or account data, self-service experiences, and commerce rather than manage each as a completely disconnected initiative. Liferay's existing integration capabilities and extensible architecture provide a useful foundation for this approach.
Liferay is not necessarily the simplest option for every use case, but I appreciate that it gives organizations room to build around their real business requirements. Its combination of enterprise portal capabilities, customization, integration, and expanding digital experience offerings makes it a platform worth considering for long-term enterprise needs. Review collected by and hosted on G2.com.
My biggest concern with Liferay is the amount of platform knowledge needed to make the right decisions early in a project. The platform offers many possibilities, but that also means teams need to understand its architecture and conventions before they can use those possibilities effectively. Without that experience, even relatively straightforward requirements can turn into more customization than expected.
I would like to see a clearer path from a standard business requirement to a recommended implementation. Experienced teams can work through the available options, but newer developers could benefit from more practical, end-to-end examples that explain not only how something works, but also which approach is appropriate and why.
Another area for improvement is the overall cost of change. Custom solutions can serve a business very well, but they also create responsibilities around upgrades, regression testing, compatibility, and ongoing maintenance. Making these transitions more predictable would help organizations get more value from their original investment.
I would also like to see more capabilities available out of the box for common business scenarios, reducing the need to build and maintain custom functionality for requirements that many enterprises share.
I see these as opportunities to make a capable platform easier to adopt and maintain, rather than fundamental weaknesses in the product. Liferay already provides considerable control; making that control easier to use consistently would make the overall experience even better. Review collected by and hosted on G2.com.