0

We're evaluating a set of requirements for a customer who wants Liferay which mainly has AAA and Web CMS requirements, and allowing user to upload their own content. Also all inetgration is via web services.

However there is no need for other features such as actual "portlets", i18n, mashups, skins, themes, tagging, social presence, no collaboration etc

So we feel we can do this as a standard JEE web app and not use Liferay (or any other portal product) since these are overheads we dont need.

The customer feels the Web CMS requirements + user upload justify the "portal" product.

Can anyone help me with some points to convince the customer? Assuming our point of view is right.

Improve this question
3
  • 2
    Were you planning on writing the CMS from the ground up? That would be a barrier for me as once your task is done the customer would have a harder time extending it without coming back to you. Have you offered any industry standard CMS solutions that are a little more light weight?
    – Rig
    Nov 26, 2012 at 18:30
  • @Rig: thinking of magnolia or alfresco - or any suggestions you have? no plans to write our own CMS
    – shinynewbike
    Nov 30, 2012 at 6:18
  • Can't say that I do as I have no experience with either. Been a while so anything that lead to you a choice would be probably worth sharing ;)
    – Rig
    Mar 5, 2013 at 3:22

1 Answer 1

Reset to default
1

you should check the requirements of your costumer now and in one year, depending on that, you should then know, if a CMS or a Portal, or a Portal with CMS integration best fits the costumer needs, now and in one year.

between CMS and Portal is a big difference. where CMS is just about Content Management, means there are just special users who are able to add end edit the content displayed on the website. each user will see the same content (maybe without rights a bit less)

a portal is something where users can login and either just use available content as they want. iGoogle as example is a portal. each user decide what content so see where.

a Portal with CMS is a portal, but now the users have the option to add and edit content to the portal which can be used by other users.

and also a benefit of good portal like Liferay is, it used portlets, so if you dont need some content / features you can remove this portlets.

and if a produkt brings such features like i18n or themes skins fro free, its not bad, you dont need to use it.

also why in that case you should prefer an existing solution over own development is: the existing solution is proven that it works for what your costumer need, your own doesn't.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.