Comparison of CMS - Alfresco, Magnolia, Drupal and Joomla

I am comparing Alfresco, Magnolia and Joomla specifically for the following functions:

a. Ease of Integration of user created templates. b. JCR (JSR-170?) or CMIS compliance. c. Scalability in architecture. d. Mobile site deployment. 

I used cmsmatrix.org to compare features, but I was not able to get specific information related to the above points.

Any information based on your experience with one or more of the above CMS products will be helpful.

Thanks,
Krish.

+4
source share
4 answers

Although these four products are branded as CMS, I do not think they are truly comparable. Drupal and, as far as I know, Joomla is a CMS web publication (or WCMS ), they are designed to create websites and manage their content. They are not designed as general CMS, DMS or ECM . Alfresco, and possibly Magnolia, are ECM / DMS for enterprise content management.

For example, being managed in Drupal (given sufficient effort and custom PHP code), a complex multi-agent workflow for multilingual documents (PDF, Office, etc.) is probably easier to manage with Alfresco. And Alfresco is probably not suitable for managing web content with an easy publishing workflow and user-generated content.

Having managed content published on a website does not mean that it should be controlled by the same tools that the website managed. For example, using the Drupal CMIS module, you can link it to Alfresco (or any CMIS ECM compatible) to manage your corporate content in suitable tools, but publish parts of it on the Drupal website.

+12
source

To summarize what I got here along with what I have found in my search from various discussions so far (thanks @ mongolito404 and bkraft).

For web content management features - Drupal / Joomla recommended.

For corporate content management / document management features with minimal web publishing capabilities, Alfresco / Magnolia is recommended.

For specific requirements, you can use the best of various tools - Drupal for publishing web content using CMIS. Alfresco as a solution for workflow and document management.

Alfresco already supports and continues to have CMIS in the product roadmap (contributes to the CMIS community).

Drupal is compatible with CMIS (OOTB) with powerful web content.

Using the best of them (Alfresco and Drupal) can also be one of the options depending on the requirement. See http://www.optaros.com/blogs/drupal-alfresco-integration#

Another interesting option, apparently, is Liferay (v6 + specifically) with their CMIS integration: http://www.liferay.com/web/jonas.yuan/blog/-/blogs/integrating-alfresco-through-cmis- in-liferay

Thank you Krish.

+6
source

One cannot speak for others, but from the point of view of Magnolia, ease of integration is, of course, the main feature. It runs on the Java platform, so integration is done from the platform. In addition, Magnolia rated the most flexible CMS on the market today by independent analyst Tony White of Ars Logica to download his free report (always worth reading, as well as other reports).

JCR: Magnolia is based on JCR, and it was like that since the first line of CMIS code: not yet implemented, but it is planned that Magnolia 5 will be shipped later this year Scalability: Magnolia has embraced it. See Our Case Studies Mobile Site Deployment: Again, naturally, it comes to Magnolia due to its architecture and rich functionality.

Relationships - Boris

+3
source

Update: CMIS is available as a community module with Magnolia v4.5

+1
source

Source: https://habr.com/ru/post/1339007/


All Articles