CMS - Alfresco、Magnolia、Drupal 和 Joomla 比较
我正在比较 Alfresco、Magnolia 和 Magnolia。 Joomla 特别针对以下功能：
a. Ease of Integration of user created templates.
b. JCR (JSR-170?) or CMIS compliance.
c. Scalability in architecture.
d. Mobile site deployment.
我使用 cmsmatrix.org 来比较功能，但我无法获得与上述几点相关的一些具体信息。
根据您使用上述一种或多种 CMS 产品的经验得出的任何见解都会有所帮助。
谢谢，
克里什。
I am comparing Alfresco, Magnolia & Joomla especially specific to following features:
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 could not get some of the specific information related to above mentioned points.
Any insights based on your experience on working with one or more of the above CMS products will be helpful.
Thanks,
Krish.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
虽然这四种产品都被称为CMS，但我认为它们并没有真正的可比性。据我所知，Drupal 和 Joomla 都是网络发布 CMS（或 WCMS），它们旨在创建网站和管理他们的内容。它们并非被设计为通用 CMS、DMS 或ECM。 Alfresco（可能还有 Magnolia）都是 ECM/DMS，旨在管理企业内容。
例如，虽然可以在 Drupal 中进行管理（只要付出足够的努力和自定义 PHP 代码），但使用 Alfresco 可能更容易管理多语言文档（PDF、Office 等）的复杂多状态多参与者工作流程。 Alfresco 可能不适合管理具有轻量级发布工作流程和用户生成内容的 Web 内容。
在网站上发布托管内容并不意味着必须使用与管理网站相同的工具来管理它。例如，使用 Drupal CMIS 模块，您可以将其与 Alfresco（或任何符合 CMIS 的 ECM）桥接，以管理您的企业内容合适的工具，但将其部分发布到 Drupal 站点上。
While these four products are branded as CMS I don't think they are really comparable. Drupal and, for what I know, Joomla are web publishing CMS (or WCMS), they are designed to create web sites and manage their content. They are not designed as generic CMS, DMS or ECM. Alfresco, and probably Magnolia, are ECM/DMS designed to manage enterprise contents.
For instance, while manageable in Drupal (given enough effort and custom PHP code), complex multi-states multi-actor workflow for multilingual documents (PDF, Office, etc.) are probably easier to manage with Alfresco. And Alfresco is probably not suitable to manage web content with lightweight publishing workflow and user generated content.
Having the managed content published on a web site does not means it has to be managed by the same tools that the one used to manage the web site. For instance, using the Drupal CMIS module, you can bridge it with Alfresco (or any CMIS compliant ECM) to manage your enterprise content in the suitable tools but publish parts of it on a Drupal site.
总结我在这里收到的输入以及我在迄今为止的各种讨论中搜索到的内容（感谢 @mongolito404 和 bkraft）。
对于 Web 内容管理功能，建议使用 Drupal / Joomla。
对于具有最少 Web 发布功能的企业内容管理/文档管理功能，建议使用 Alfresco/Magnolia。
对于特定要求，可以使用最好的不同工具 - Drupal 通过 CMIS 支持发布 Web 内容。 Alfresco 作为工作流程和解决方案的解决方案文件管理。
Alfresco 已经支持 &继续将 CMIS 纳入产品路线图中（为 CMIS 社区做出贡献）。
Drupal 符合 CMIS (OOTB) 标准，具有强大的 Web 内容功能。
根据需求，利用两者的优点（Alfresco 和 Drupal）也可能是选项之一。请参阅：http://www.optaros.com/blogs/drupal-alfresco-integration#
另一个有趣的选择似乎是 Liferay（特别是 v6+）及其 CMIS 集成功能：http://www.liferay.com/web/jonas.yuan/blog/-/blogs/integrating-alfresco-through-cmis-in-liferay< /a>
谢谢，
克里什。
Summarizing inputs I received here along with what I found in my search from various discussions so far (thanks @mongolito404 and bkraft).
For web content management features - Drupal / Joomla is recommended.
For Enterprise Content Management / Document Management features with minimal web publishing features - Alfresco / Magnolia is recommended.
For specific requirements the best of different tools can be used - Drupal to publish web content via CMIS support. Alfresco as solution for workflow & document management.
Alfresco already supports & continues to have CMIS in product roadmap (contributes to CMIS community).
Drupal is CMIS compliant (OOTB) with strong web content capability.
Leveraging best of both (Alfresco & Drupal) could also be one of the options depending on the requirement. Refer: http://www.optaros.com/blogs/drupal-alfresco-integration#
Another interesting option seems to be Liferay (v6+ specifically) with their CMIS integration capability: http://www.liferay.com/web/jonas.yuan/blog/-/blogs/integrating-alfresco-through-cmis-in-liferay
Thanks,
Krish.
不能代表其他人，但从 Magnolia 的角度来看，易于集成无疑是一个核心功能。它运行在Java平台上，因此集成是平台方面给定的。此外，Ars Logica 的独立分析师 Tony White 将 Magnolia 评为当今市场上最灵活的 CMS 下载他的免费报告（总是值得一读，并且还提供其他报告）。
JCR：Magnolia 基于 JCR，从第一行代码开始就是如此
CMIS：尚未实施，但计划 Magnolia 5 今年晚些时候发货
可扩展性：Magnolia 已经解决了这个问题。请参阅我们的案例研究
移动站点部署：同样，由于 Magnolia 的架构和丰富的开箱即用功能，这对 Magnolia 来说是很自然的事情。
问候
——鲍里斯
Can't speak for the others, but from Magnolia's perspective, ease of integration is certainly a core feature. It runs on the Java platform, so integration is a given from the platform side. In addition Magnolia has been rated the most flexible CMS on the market today by independent analyst Tony White of Ars Logica download his free report (always worth a read, and other reports are also available).
JCR: Magnolia is based on JCR, and was so since the first line of code
CMIS: not implemented yet, but planned for Magnolia 5 to be shipped late this year
Scalability: Magnolia's got it covered. See our case studies
Mobile site deployment: again, comes naturally to Magnolia thanks to its architecture and rich out of the box functionality.
Regards
- Boris
更新：自 Magnolia v4.5 起，CMIS 作为社区模块提供
Update: CMIS is available as a community module since Magnolia v4.5