需要一个简单的CMS。我应该自定义现有的CMS还是从头开始构建？ [英] Need a simple CMS. Should I customise an existing CMS or build from scratch?

问题描述

我正在建立一个非常简单的网络托管服务，以满足ma和pa类型的小型企业。

I'm building a VERY simple web hosting service that will cater to the ma and pa type small business.

现在我的困境是，划痕或使用现有的CMS。 CMS需要是可定制的，因为我希望构建我自己的客户端。我只想让用户必须放一个标题和内容。

Now my dilemma is whether I should built it from scratch or use an existing CMS. The CMS needs to be customisable, as I wish to build my own client. I only want the user to have to put a title and content. Everything else will be hidden from the end user.

稍后我想将自己的自定义构建的Web应用程序关联到给定的页面，因此CMS需要

Later on I want to be able to associate my own custom built web applications to a given page, so the CMS needs to be able to cater for that.

另一个要求是它需要基于Java（Groovy可接受）。

The other requirement is that it needs to be Java based (Groovy acceptable).

任何想法？

推荐答案

即使是一个简单的CMS是一个相当复杂的应用程序， ，安全性，可扩展性等。有很多很多事情你可以错了。主要的CMS有遭受大量的维护问题和安全漏洞，并有相当数量的人才在他们工作。如果你认为你的CMS会不同，我建议它不会。您需要不断更新和维护它。如果您使用现成的解决方案，您应该能够从其他开发人员正在做的工作中受益。

Even a "simple" CMS is a fairly complicated application once you start doing things like user authentication, security, scalability, etc. There are many many things you can get wrong. The major CMSes out there suffer from lots of maintenance problems and security bugs and there are a fair number of talented people working on them. If you think your CMS will be different, I suggest that it will not be. You will need to update and maintain it constantly. If you use an off-the-shelf solution you should be able to benefit from the work those other developers are doing. If you want to write your own code, consider customizing an off-the-shelf CMS or contributing new features or bug fixes.

自己的CMS：

• 对功能的完全控制


• 低成本




• 只有您了解它并且可以修复
。

• 没有来自其他开发者的错误修复

• Total control over the features
• Low cost
• Easy for you to understand
• Only you understand it and can fix it
• No bug fixes from other developers

现成的CMS：

• 您可以简单安装它， / li>
  
• 陡峭的学习曲线


• 很多托管解决方案和在线帮助


• 很多人都可以管理


• 供应商发布错误修正和安全性更新


• 更多限制在自订等方面


• 有人需要保留更新并安装它们，否则客户可能是蠕虫的受害者，例如WordPress蠕虫。使用自己的CMS，不太可能有人会为您创建一个蠕虫。

• You can simply install it, then concentrate on adding value
• Steeper learning curve
• Lots of hosted solutions and online help
• Lots of people can admin it if you're not around
• Bug fixes and security updates are released by the vendor
• More limited in terms of customization, etc
• Someone needs to keep on top of the updates and install them, or else the customer might be victim to a worm such as the WordPress worms. With your own CMS it's less likely that someone will create a worm just for you. (But your customers are still at risk of other security problems).

考虑每个网站面临的典型安全问题：XSS， CSRF，SQL注入，配置错误，宽松的安全性，会话劫持，参数验证错误，竞争条件等。您需要处理所有这些情况，但CMS供应商已经为您做这件事。

Consider the typical security issues that face every website faces: XSS, CSRF, SQL Injection, configuration errors, loose security, session hijacking, parameter validation errors, race conditions, etc. You need to handle all those cases, but the CMS vendors are already doing that for you.

对于您的Java需求，Resin web服务器附带一个PHP解释器，如果您选择一个PHP CMS，可能允许您使用Java部署一个PHP应用程序。还应该可以在几小时内将PHP引擎移植到另一个servlet容器中（我认为它是GPL）。

As for your Java requirement, the Resin web server ships with a PHP interpreter which might allow you to deploy a PHP app in Java should you choose a PHP CMS. It should also be possible to port the PHP engine to another servlet container in a few hours (I think it's GPL).

这篇关于需要一个简单的CMS。我应该自定义现有的CMS还是从头开始构建？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！