I've had a lot of success with Django-CMS. It's very, very easy to write custom content-type plugins, extend menu nodes with custom nav elements, such as a list of product categories, etc. It's dead-simple to hook custom application code to any page in the navigation hierarchy.
As you mentioned in your question, Zinnia also plugs into Django-CMS for a nice blogging solution that is also extensible. Adding a cart app, whether it's from the DIVIO team or not should be an easy task.
Django, DjangoCMS and Python in general, have very low learning curves in my opinion. In 14 years of development, Django is the only web framework that hasn't gotten in my way, and Python is an absolute pleasure to work with on a daily basis.
I think you'll find that the Django ecosystem is much more holistic than any of the other Python frameworks, it's also very, very well documented and there are literally hundreds of 3rd party apps. Plus, Django admin can potentially save you many weeks of dev time, and you can override, skin and extend it to do just about anything.
Yeah, right after I posted I realized I was heavy on comparison of frameworks but light on suggested solutions to your problem (i.e. existing appliances). I think that Django probably has more matured addins/apps. That being said, crafting your own blog in web2py (a simple blog) is probably only a little harder than configuring one for another framework.
There is the wordpressclone appliance: http://web2py.com/appliances/default/show/36 (you can extract existing wordpress data and get it in here, i'm pretty sure there's a WP export and an import function on this appliance)
There is KPax CMS, as you said, but i think this one might be out of date, unless it was updated recently. The integration between these should be possible, you can share sessions across apps and I think if you have the same auth_user db, it should work.
I would try installing these and see if they are close to meeting your needs -- especially KPax since I'm not sure the state it's in.
-- END EDIT --
Both Django and Web2py are very good frameworks in my opinion. I think you would be happy with either. That being said, having not used frameworks I would say to with web2py, unless you NEED certain modules that only exist in the django world. Web2py probably has a little more gradual learning curve. Also, it can do RSS out of the box, there's a screencast somewhere showing how to create a blog app in about 5 minutes (including comments), and the community is (usually) very responsive. I don't think there is anything that web2py can do that django can't (except DB migrations -- but i think you can make django do them with some 3rd party code), or vice versa.
Django favors a "explicit is better than implicit" development methodology, which requires to you import various modules and doesn't have all the "magic" of web2py. Using django, you will be more aware of exactly what is going on under the hood. The django templating language is easy to learn and provides a lot of functionality for common markup tasks. Their is a LOT of documentation, a larger user-base and tons of 3rd party modules/plugins/whatever.
Web2py favors a "everything should have a default" approach, and enables to to focus on the big picture without getting bogged down by the minutia of web development. I'm not saying this is in contrast to django, but rather that web2py is very strong on this point. It allows you to rapidly develop applications, and takes the headache out of things like updating a table schema (i.e. it does database migrations). I also prefer web2py's templating language to django's, as it allows pure python and does not require one to learn a separate templating language at all.
I think both frameworks have decent internationalization/localization features. I'm not sure if Django's is still under development or not? Web2py's is easy to use, but I think you might have to provide a lot of the translations yourself.
As for the lack of replies on the web2py list, maybe it's because this topic is becoming more and more frequent? I'm not sure. You could ask people on the web2py freenode channel.
web2py is a great framework, but currently light on reusable CMS, blog, and particularly e-commerce applications. It sounds like you have already stumbled upon the main options -- plugin_wiki, Powerpack, and Instant Press.
I don't think there is a mature and currently maintained e-commerce application, but you may be able to make use of web2py-estore. There are also some options for accepting credit card payments (see also).
plugin_wiki includes comment functionality, and there is also plugin_comments. For PDFs, pyfpdf comes with web2py, and there is also web2py_appreport. web2py also includes RSS support.
EDIT: Also, another web2py CMS under development, to be released soon: SimplrCMS
发布评论
评论（3）
我在 Django-CMS 方面取得了很大的成功。编写自定义内容类型插件、使用自定义导航元素扩展菜单节点（例如产品类别列表等）非常非常容易。将自定义应用程序代码挂接到导航层次结构中的任何页面非常简单。
正如您在问题中提到的，Zinnia 还可以插入 Django-CMS，以获得一个很好的可扩展的博客解决方案。添加购物车应用程序（无论是否来自 DIVIO 团队）都应该是一项简单的任务。
在我看来，Django、DjangoCMS 和 Python 的学习曲线通常都很低。在 14 年的开发中，Django 是唯一没有妨碍我的 Web 框架，而每天使用 Python 绝对是一种乐趣。
我认为您会发现 Django 生态系统比任何其他 Python 框架都更加全面，它的文档也非常非常完善，并且实际上有数百个 3rd 方应用程序。另外，Django admin 可以为您节省数周的开发时间，并且您可以覆盖、换肤和扩展它以执行几乎任何操作。
我的 0.02 美元:)
I've had a lot of success with Django-CMS. It's very, very easy to write custom content-type plugins, extend menu nodes with custom nav elements, such as a list of product categories, etc. It's dead-simple to hook custom application code to any page in the navigation hierarchy.
As you mentioned in your question, Zinnia also plugs into Django-CMS for a nice blogging solution that is also extensible. Adding a cart app, whether it's from the DIVIO team or not should be an easy task.
Django, DjangoCMS and Python in general, have very low learning curves in my opinion. In 14 years of development, Django is the only web framework that hasn't gotten in my way, and Python is an absolute pleasure to work with on a daily basis.
I think you'll find that the Django ecosystem is much more holistic than any of the other Python frameworks, it's also very, very well documented and there are literally hundreds of 3rd party apps. Plus, Django admin can potentially save you many weeks of dev time, and you can override, skin and extend it to do just about anything.
My $0.02 :)
-- 编辑 --+
是的，就在我发布后，我意识到我很注重框架的比较，但很少关注针对您的问题的建议解决方案（即现有设备）。我认为 Django 可能有更成熟的插件/应用程序。话虽这么说，在 web2py 中制作自己的博客（一个简单的博客）可能只比为另一个框架配置博客难一点。
有 wordpressclone 设备： http://web2py.com/appliances/default/show/36< /a>
（您可以提取现有的 WordPress 数据并将其放在这里，我很确定此设备上有 WP 导出和导入功能）
有一个电子商店（尚未使用过）： http://web2py.com/appliances/default/show/24
正如你所说，有KPax CMS，但我认为这个可能已经过时了，除非最近更新过。这些之间的集成应该是可能的，您可以跨应用程序共享会话，我认为如果您有相同的 auth_user 数据库，它应该可以工作。
我会尝试安装这些，看看它们是否接近满足您的需求 - 特别是 KPax，因为我不确定它所处的状态。
- 编辑结束 -
在我看来，Django 和 Web2py 都是非常好的框架。我想你都会对其中任何一个感到满意。话虽这么说，在没有使用过框架的情况下，我会说使用 web2py，除非你需要某些仅存在于 django 世界中的模块。 Web2py 可能有更渐进的学习曲线。此外，它可以开箱即用地执行 RSS，某个地方有一个截屏视频，展示了如何在大约 5 分钟内创建一个博客应用程序（包括评论），并且社区（通常）反应非常灵敏。我不认为 web2py 可以做 django 做不到的事情（除了数据库迁移——但我认为你可以让 django 使用一些第三方代码来完成它们），反之亦然。
Django 倾向于“显式优于隐式”的开发方法，这需要您导入各种模块，并且不具备 web2py 的所有“魔力”。使用 django，您将更加了解幕后到底发生了什么。 django 模板语言易于学习，并为常见标记任务提供了大量功能。他们有大量的文档、更大的用户群和大量的第三方模块/插件/等等。
Web2py 倾向于“一切都应该有默认值”的方法，并且能够专注于大局，而不会陷入 Web 开发的细节之中。我并不是说这与 django 形成对比，而是 web2py 在这一点上非常强大。它允许您快速开发应用程序，并消除更新表模式（即进行数据库迁移）之类的麻烦。与 django 相比，我也更喜欢 web2py 的模板语言，因为它允许纯 python，并且根本不需要学习单独的模板语言。
我认为这两个框架都有不错的国际化/本地化功能。我不确定 Django 是否仍在开发中？ Web2py 很容易使用，但我认为您可能必须自己提供很多翻译。
至于web2py列表上没有回复，也许是因为这个话题越来越频繁？我不知道。你可以询问 web2py freenode 频道上的人。
另外，一定要查看此链接：
针对初学者开发人员的 Django 与 web2py
第一个回应来自 web2py 的首席开发人员，但我认为他做出了相当平衡的比较。
另外，上一个线程包含到此处的链接（web2py 的好与坏）：
http ://www.mengu.net/post/django-vs-web2py
-- EDIT --+
Yeah, right after I posted I realized I was heavy on comparison of frameworks but light on suggested solutions to your problem (i.e. existing appliances). I think that Django probably has more matured addins/apps. That being said, crafting your own blog in web2py (a simple blog) is probably only a little harder than configuring one for another framework.
There is the wordpressclone appliance: http://web2py.com/appliances/default/show/36
(you can extract existing wordpress data and get it in here, i'm pretty sure there's a WP export and an import function on this appliance)
There is an e-store (haven't used it): http://web2py.com/appliances/default/show/24
There is KPax CMS, as you said, but i think this one might be out of date, unless it was updated recently. The integration between these should be possible, you can share sessions across apps and I think if you have the same auth_user db, it should work.
I would try installing these and see if they are close to meeting your needs -- especially KPax since I'm not sure the state it's in.
-- END EDIT --
Both Django and Web2py are very good frameworks in my opinion. I think you would be happy with either. That being said, having not used frameworks I would say to with web2py, unless you NEED certain modules that only exist in the django world. Web2py probably has a little more gradual learning curve. Also, it can do RSS out of the box, there's a screencast somewhere showing how to create a blog app in about 5 minutes (including comments), and the community is (usually) very responsive. I don't think there is anything that web2py can do that django can't (except DB migrations -- but i think you can make django do them with some 3rd party code), or vice versa.
Django favors a "explicit is better than implicit" development methodology, which requires to you import various modules and doesn't have all the "magic" of web2py. Using django, you will be more aware of exactly what is going on under the hood. The django templating language is easy to learn and provides a lot of functionality for common markup tasks. Their is a LOT of documentation, a larger user-base and tons of 3rd party modules/plugins/whatever.
Web2py favors a "everything should have a default" approach, and enables to to focus on the big picture without getting bogged down by the minutia of web development. I'm not saying this is in contrast to django, but rather that web2py is very strong on this point. It allows you to rapidly develop applications, and takes the headache out of things like updating a table schema (i.e. it does database migrations). I also prefer web2py's templating language to django's, as it allows pure python and does not require one to learn a separate templating language at all.
I think both frameworks have decent internationalization/localization features. I'm not sure if Django's is still under development or not? Web2py's is easy to use, but I think you might have to provide a lot of the translations yourself.
As for the lack of replies on the web2py list, maybe it's because this topic is becoming more and more frequent? I'm not sure. You could ask people on the web2py freenode channel.
Also, definitely check out this link:
Django vs web2py for a beginner developer
The first response is from the lead developer of web2py, but I think he makes a fairly balanced comparison.
Also, the previous thread includes a link to here (the good and bad of web2py):
http://www.mengu.net/post/django-vs-web2py
web2py 是一个很棒的框架，但目前只关注可重用的 CMS、博客，尤其是电子商务应用程序。听起来您已经偶然发现了主要选项 - plugin_wiki，Powerpack 和 即时按下。
我认为没有成熟且当前维护的电子商务应用程序，但您也许可以使用 web2py-estore。还有一些接受信用卡付款的选项（ 另请参阅）。
plugin_wiki 包含评论功能，还有 plugin_comments。对于 PDF，pyfpdf 附带 web2py，还有web2py_appreport。 web2py 还包括 RSS 支持。
编辑：另外，另一个 web2py CMS 正在开发中，即将发布： 简单CMS
web2py is a great framework, but currently light on reusable CMS, blog, and particularly e-commerce applications. It sounds like you have already stumbled upon the main options -- plugin_wiki, Powerpack, and Instant Press.
I don't think there is a mature and currently maintained e-commerce application, but you may be able to make use of web2py-estore. There are also some options for accepting credit card payments (see also).
plugin_wiki includes comment functionality, and there is also plugin_comments. For PDFs, pyfpdf comes with web2py, and there is also web2py_appreport. web2py also includes RSS support.
EDIT: Also, another web2py CMS under development, to be released soon: SimplrCMS