It outdoes most every CMS, so what am I missing?

[Michael Heckman, modificado hace 15 años.]

I am new to Liferay, and am beginning to wonder if I am just plain missing an obvious down side:

To me, Liferay seems far easier to configure and customize than most of the "classic" open source CMS (Nuke, Joomla, Drupal etc.). I am not running an "enterprise," just a small nonprofit that needs a way for members to communicate, opine, and collaborate.

Forgetting the document management portlets for the moment, I'm wondering why Liferay isn't an obvious choice for anybody running a site that includes blogging, membership, and forums?

Is there a lack of design flexibility? Does it handle traffic poorly? Does it have some other shortcoming that makes it unsuitable for member-driven web site use?

It seems to me that when combined with a decent hosting plan, Liferay is noticeably faster to deploy and easier to manage than the "classic" CMS applications mentioned above-- albeit more expensive to host. So what's the catch?

[Brian Kim, modificado hace 15 años.]

No catch. It's just great software. But then again, I am biased. =)

Thanks for the compliments.

[Shepherd Ching, modificado hace 15 años.]

I was a newbie of Liferay long long time ago, and I has used postnuke for years.

To me, Postnuke seems to be far away from strict coding than most of the "classic" open source portal (Sun OpenPortal, Apache Jetspeed and Liferay). The freedom of spaghetti codes in php nuke programming makes me hard to debug. I am not runnning a personal toy, but as the viewpoint of an enterprise, I need a way for other colleagues to work, opine and collaborate together


So what am I missing? I am missing the patience to study the basic knowledges, Java, Spring, Hibernate, Jackrabbit, Quartz, Struts, JQuery, ICEFaces, blah, blah blah.

Is there a lack of design flexibility? It depends on the favours of designers.

Does it handle traffic poorly? It depends on the knowledges of network administrators.

Does it have some other shortcoming that makes it unsuitable for member-driven web site use? It depends on decision and design of your bosses.

So what's the catch? The catch is that I need an enterprise tool for different specialists working together.


It takes all types of products to make up the world, some users need "quick and dirty" tools to get the job done and to get the job paid,
another users require systematic division of labour for their continual businesses.


It takes all kinds of people to make up the world, I don't raise any argument. Every users must have their biases.