Django FlatPages 与 Django-CMS
无需过多讨论，我正在构建一个 Django 网站，并且想要实现一个 CMS 解决方案，同时在页面布局、导航和组织方面具有很大的灵活性。
它主要用于我们的文档，到目前为止，我在试图弄清楚 Django CMS 的细节时遇到了很多麻烦。
经验丰富的 Django 开发人员会建议我使用像tiny_mce 这样的平面页面吗？
Without going into too much detail, I'm building a Django site and I wanted to implement a CMS solution, while having a lot of flexibility with page layouts, navigation, and organization.
It'd be mainly used for our documentation, and so far I've had a lot of headaches trying to figure out the ins-and-outs of Django CMS.
Would an experienced Django developer recommend I use flat-pages with like tiny_mce instead?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您还可以查看 Django wiki 中的 CMS 应用程序比较，甚至可以贡献任何内容缺少信息。
我听说过关于 FeinCMS 的好消息。
You could also take a look at the CMS apps comparison in the Django wiki and maybe even contribute any missing information.
I've heard good things about FeinCMS.
几乎所有 Django CMS 都是出于主要开发人员在一两个项目期间的必要性和要求而诞生的。他们中的大多数人做得太多，有些人做得太少。
如果您正在尝试构建一个 CMS，以便可以动态地使用网站的创建内容和布局（可以是内部或外部的），您可能会发现自己很困惑，从一个 CMS 跳到另一个，希望找到完美的一个。或者您可以只使用 mptt 或 django-categories 来为您提供导航和嵌套链接。将其与启用tiny_mce 的平面页面相结合，您将拥有一个满足您要求的简单cms。然后您可以根据需要添加其他内容。但如果您坚持，那么请尝试 djnago-pages-cms 和/或夹层，它们可以满足您的需求，但您将被锁定使用它们并围绕它们进行构建。
Pretty much all the Django CMS(s) out there are born out of the necessity and requirements of the primary developers during a project or two. Most of them do too much, some do too little.
If you are trying to build a CMS so you could dynamically use create content and layout of a site which could be internal or external, you may find yourself confused jumping from one cms to another in the hope of finding the perfect one. Or you can just use mptt or django-categories to give you navigation and nested links. combine that with tiny_mce enabled flat-pages and there you'd have a simple cms that satisfies your requirements. Then you can go and add other stuff if you need to. But if you insist, then try djnago-pages-cms &/or mezzanine which do what you are looking for, but you'd be locked in to use them and build around them.
我不太喜欢平面页面的“检查 404 然后返回结果”方法，但是 http://www.punteney.com/writes/django-simplepages-basic-page-cms-system/ 可能会给你足够的力量让平面页面工作在这种情况下，无需使用成熟的 Django CMS。
我的方法通常是“构建只是足够大”，除非开箱即用的东西满足所有功能要求，您的里程可能会有所不同。
听起来你本质上是在寻找维基？
I'm not a big fan of the 'check 404 then return result' methods of flat-pages, but http://www.punteney.com/writes/django-simplepages-basic-page-cms-system/ might give you just enough power for flat-pages to work in this scenario, without using a full-blown Django CMS.
My approach is generally 'build it just big enough' unless something out of the box meets all feature requirement, your mileage may vary.
Sounds like essentially you're after a wiki?