Liferay as a CMS
Anyone have experience with Liferay as an enterprise CMS? Is it a 'real' CMS or does it just call itself one like Drupal does?
We're in the market for an enterprise CMS, and with LP5 on the horizon, there might be some connection points if we were to implement Liferay as a CMS also.
Thanks, Bob.
liferay cms
Seems fairly full featured.
http://www.liferay.com/products/liferay-portal/features/cms
I'm not sure how much Sungard's modifications will alter the baseline liferay abilities though.
This question is much easier
This question is much easier to answer when you have a list of features you need, and you can directly compare what Liferay/Luminis can provide.
I'm not an expert, but I've played with Liferay and Luminis 5 a good deal at this point. The portal platform provides things like approval of content before posting, versioning of documents, some limited saving of details and tracking of who uploaded and who contributed what. Things like de-duplication (not really necessary for us, I think) and a powerful included reporting engine (kind of important, I think to any institution) are missing. Reporting and Admin type stuff seems real, surprisingly weak to me. It doesn't look like Liferay/Lum provides reports for the last time a user logged in, how often a document or portlet has been accessed, etc... "Use Google Analytics" is completely unacceptable. I'm sure a lot of this data is available in the database, but that is pretty lame as well, IMO. (Sorry, I drifted away from CMS some.)
What specific features are you looking for? What is Drupal missing that you would need? (I ask the latter having limited Drupal experience, so I'd like to know.)
Liferay separate from Luminis
I probably didn't make this clear, but this would be a completely separate instance of Liferay to be used as an engine for an institutional CMS. Luminis 5 on Liferay would be separate. However, I do feel there would be some overlap between the two instances, especially in expertise, that may be worthwhile to exploit.
From my limited involvement in CMSes, there seem to be two classes of applications that call themselves a CMS:
1) traditional CMS: like RedDot, Cascade, Sitecore, MOSS, LCMS (yikes!)
2) blogs/wikis with feature bloat: Drupal, WordPressMU, Joomla.
As much as I appreciate Drupal(it's perfect for lumdev), I can't imagine building a medium-size college institutional website with Drupal, probably using plugins for workflow, versioning, and reporting.
My question is: does Liferay CMS fall into 1) or 2) above?
Thanks, Bob