pimcore的（dis）优点是什么？ [英] What are the (dis)advantages of pimcore?

问题描述

我正在寻找一个基于Zend框架的CMS，我阅读关于pimcore。现在我有一些问题：

• 有没有人有这个CMS的经验？


• （dis）的优点？


• 学习曲线如何？

解决方案

Pimcore岩石作为一个高级企业cms，ams，pims，你有什么。我们已经在公司环境中使用它作为我们的资产管理系统从v1.2，并正在使用v1.4.1现在和爱它。

一般缺点to the run of the mill popular cms's like joomla / drupal / wordpress etc）：

1. 陡峭的开发学习曲线，需要知道zend框架extjs如果你想修改管理区域或添加插件（虽然我认为大多数较旧的cms是一个噩梦开发）。


2. 高级管理界面，不是最终用户友好标准cms任务（如添加页面）。



li>后端插件工作需要前端/ extjs / ajax知识和后端/ php / xend框架/ mysql知识。

4. 在专用计算机上运行最好，需要大量的处理和权力对于zend框架要快，并且投入共享主机需要一些调整来工作。


5. 仍然早期的产品，所以一些东西，如品牌管理和其他小东西不是那么灵活。


6. 不是一大堆主题或插件。


7. 有点难做


8. 没有前端登录/注册/成员区域模块，如果您需要前端用户身份验证，则需要自己编码。

优点：

1. 立场它是超强的和可扩展的，可以做任何事情，因为它完全基于对象/资产/文档模型与API使用这些对象和插件架构来定制管理员。


2. 使用Pimcore API和Zend Framework / ExtJS编写代码很方便，而且相当的bug免费


3. 许多企业系统需要的内置功能，例如用户/组/权限，版本，计划，缓存，cdn和i18n国际化。


4. 在管理员中使用ExtJS框架的许多哇因素用户界面，如拖放，网格，编辑对象。


5. 现代网站编辑功能/


6. 没有太多的障碍或限制因素，基本上它可以开放你想要做的任何事情，很少有你遇到的东西，是一个完整的路障，需要编辑核心文件。


7. 大多数使用案例都足够灵活，足以允许改进和自定义而不是噩梦。


8. 内置升级机制。


9. 插件架构。


10. PHP单元测试插件。


11. 内置用于创建可扩展类和对象的管理UI。 >
    
12. 管理界面，用于布置允许使用许多预配置的ui控件（如文本框，滑块，复选框等）编辑对象数据的屏幕。

即使Pimcore在早期阶段它是一个优秀的企业cms框架，并将处理任何任务，但准备潜入代码找出东西，当你去。我相信这会改变，因为它成熟，他们使人们更容易地贡献代码和开放的插件市场。目前，我不会说这是一个替代的常规网站使用wordpress或drupal与吨主题和插件和最终用户UI的狂喜正常网站cms操作。但是既然你是一个编码器，不介意使用extjs和zend编写你的插件，那么这是非常值得我的灵活性。我现在的建议是去混凝土5，如果你想现代化的Zend MVC CMS网站替换，是易于使用，但仍然愉快的发展。随着时间的推移pimcore会给所有的cms一个运行，因为它的真棒建筑。

希望有帮助！

I am looking for a CMS based on Zend Framework and I read about pimcore. Now I have some questions about it:

• Does anyone have experience with this CMS?
• What are the (dis)advantages?
• How is the learning curve? (I work a lot with ZF)
• Can you develop a new module?

解决方案

Pimcore rocks as an advanced enterprise cms, ams, pims, what have you. We have been using it in a corporate environment as our asset management system since v1.2 and are using v1.4.1 right now and loving it.

General Disadvantages (when compared to the run of the mill popular cms's like joomla/drupal/wordpress etc):

1. Steeper development learning curve, need to know zend framework and extjs if you want to modify the admin area or add plugins (although i consider most of the older cms's to be a nightmare to develop on).
2. Advanced admin UI, Not end user friendly for standard cms tasks like adding a page. Not immediately clear how to add a page, add to custom navigations, etc.
3. Coder required to get it setup and really use it to its potential.
4. Backend plugin work requires both front-end/extjs/ajax knowledge and backend/php/xend framework/mysql knowledge.
5. Runs best on a dedicated machine, needs lots of processing and power for the zend framework to be fast and putting on shared hosting requires some tweaking to get working.
6. Still early product so some things like branding the admin and other minor stuff is not that flexible yet. Not everything is completely easily modifiable without touching the core yet.
7. Not a ton of themes or add-ons yet.
8. A little tough to contribute, can't just fork it on github etc.
9. No front end login/registration/members area module, you need to code it yourself if you need front end user authentication as of present.

Advantages:

1. From an architectural standpoint it is super powerful and extensible and can do anything with it since it is completely based on an object/asset/document model with an API to use those objects and a plugin architecture to customize the admin. This is a great model for a catalog of items, which most cms's revolve around but not limiting in any way.
2. Coding is pleasant using the Pimcore API and Zend Framework/ExtJS and fairly bug free for major features.
3. Lots of built in features out of the box that enterprise systems need like users/groups/permissions, versions, scheduling, cacheing, cdn, and i18n internationalization.
4. Lots of wow factor user interface stuff in the admin using ExtJS framework like drag and drop, grids, editing objects.
5. Modern website editing features/flexibility with in place editing, drag and drop/reorder content, content blocks, snippets and so on.
6. Not very many roadblocks or limiting factors, basically it's open to anything you want to do and rarely do you run into something that is a complete road block requiring editing core files.
7. Most use cases are covered and flexible enough to allow improvements and customization without being a nightmare.
8. Built in upgrading mechanism.
9. Plugin architecture.
10. PHP Unit testing plugin.
11. Built in admin UI for creating extensible classes and objects.
12. Admin UI for laying out the screens that allow editing object data using many preconfigured ui controls like textboxes, sliders, checkboxes, etc.

Even though Pimcore in early phases it is an excellent enterprise cms framework and will handle any task but be prepared to dive into code figure out stuff as you go. I'm sure this will change as it matures and they make it easier for people to contribute code and open up a marketplace for addons. Currently I wouldn't say it's a replacement for regular websites using wordpress or drupal with tons of themes and addons and end user UI fanciness for normal website cms operations. But since you are a coder and don't mind writing your addons using extjs and zend then it's well worth the flexibility in my mind. My recommendation right now is to go with concrete5 if you want a modern Zend MVC CMS website replacement that is easy to use but still pleasant to develop on. Over time pimcore will give all cms's a run for their money though due to it's awesome architecture.

Hope that helps!

这篇关于pimcore的（dis）优点是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！