I did not go for other products since the tool's open-source version was available. If I want to learn new features, I can easily try my luck using it to see if it offers enhanced security while getting to see how things work in the tool.

We evaluated Oracle Portal, WordPress, and Drupal.

Before choosing this product, we also evaluated Adobe AEM, Alfresco, etc.

We evaluated Alfresco (open source software) and Adobe Experience Manager, as alternatives. However, we have used the latter as well, for some other project.

We evaluated SharePoint.

For most of my proposals, I provided a separate sheet that includes other recommended tools. These recommendations were sometimes from the client based on their previous implementations.

For most of the client’s requirements, Liferay was a clear win because of its out-of-the-box features, portlets, and the depth and type of customization it can do.

Before choosing this product, I did not evaluate other options.

We did not evaluate alternative solutions.

We knew of applications like Drupal, but we did some research through Google. We settled on Liferay because of it's open-source functionality and our end-user was keen on getting an open-source platform. It was exactly what Liferay offered.

We didn't have extensive comparison tests with other platforms or applications.

We looked at JBoss Portal and Pluto.

We evaluated Adobe Experience Manager and WebSphere Portal v6.

We evaluated both WordPress and Drupal before deciding on Liferay.

Before selecting Liferay in 2014, I evaluated the Oracle WebLogic Portal, the JBoss Portal, and the IBM WebSphere Portal.

Before choosing, we also evaluated Drupal (open source) and Adobe AEM (proprietary).

We evaluated IBM WebSphere portal, but found WebSphere to be overkill for our project.

We tried Drupal, but it doesn't have as many built-in features as Liferay.

We evaluated WebSphere before choosing Liferay.

Several content management platforms are available in the market, such as Adobe and, in simpler scenarios, WordPress.

However, being open source is a great advantage if you are looking for extending the existing solution and customizing it for specific scenarios.

Furthermore, the solid stack of frameworks and modern UI technologies is something unique in Liferay.

Being based on OSGi and supporting extension through OSGi is almost too good to be true. With OSGi, we are even able to make hot deployable modules and patches without any significant effort while controlling the dependencies with Gradle in a way that only OSGi can support.

I evaluated JBoss Portal in 2008, but I then went ahead with Liferay

We had experience with Drupal, Joomla and other PHP platforms and we evaluated Sharepoint also.

We also evaluated Alfresco, but we decided that Alfresco and Liferay are not competitors. Instead, they both play very well together, for complex situations involving ECM, BPM and Web apps.

For content management, we have used Mura which is a ColdFusion based CMS, Drupal, and SharePoint.

We did not really evaluate other options.

A number of alternative products were evaluated, including staying with the original IBM platform. We selected Liferay due to its flexibility and scalability.

Yes, we also looked at SharePoint and WebSphere.

Before choosing this product, I also evaluated BackBase.

As mentioned earlier, we used WebLogic.

We looked at Joomla!, Drupal, and Adobe CQ5. We felt that they covered more in the content management area, instead of in the enterprise solutions.

I chose between Liferay, Drupal and Microsoft products.