No CMS - No Tools: you have a very good developer with a strong HTML background, some server side expertise and plenty of time on his/her hands.
No CMS but a light weight tool: You have a person or two who are comfortable with the basics of HTML, you site is mostly static and it is already built, but you need to update - you can consider any number of tools from (yes it is true) DreamWeaver, Aptana, Visual Studio WebExpres)
You have a small to medium web team and you have a medium for large site that is mostly content. I have found this to be the bulk of all projects that I have every seen. May times thes types of engagements end up with a large enterprise system becasue they incorrectly understood the two or three of the main factors that should drive an Enterprise CMS (read costs more that $250 and way more than free). Open source blogging engines like WordPress are very powerful and extensible. Add in a free editorial tool like LiveWriter and you have a lot if distributed editorial power, cheap, and it takes care of lots of things like Standards and SEO because it is just build solidliy in that respect. Plus there are a lot of people who can help you out. And it is very extensible.
Enterprise CMS: Three factors should guide your decisions regarding CMS:
Large distributed editorial team that requires rigorous (usually complex) editorial workflows.
The site design and operation has been deemed secondary to some other functioanlity provided byt the CMS (simple SarBox Compliance, easy support for localizing the site to many languages)
In house experience with the product that has been positive and has proven ROI - but be clear, having purchased licenses is no reason to deploy. I have seen far too many cases where a large scale CMS was purchased (licensed) only to find it would not suit the true needs of the project. In some cases the clients were wise and moved on. In others they stuck to their purchase and to this day live in a world of hurt.
Start simple and grow - The average website had a half-life of 3 years. Make a series of small mistakes that you can easily correct through fast itteration. Only go for the big stuff when you are sure.
Instant smell that you are buying more than you need - you can't find out the price of the product until a sales person visits you and you can't get demo bits of the system untl you attend their traning session. By the time you get done with that, you could have an awsome site up and be buying everyone at your firm some nice libations.
For a company website, if you write your own, you're probably going to be reinventing a lot of what a CMS already gives you. The content on your site will most likely change frequently, and the company will probably want non-developers to maintain the content. With your own implementation, you'll have to provide management pages for non-devs to upload new content (text, images, docs, etc.), so it might make sense to just look at existing CMS frameworks.
The downside of a CMS is that you might have to work around styling issues to give the site the exact look-and-feel you're going for. Usually a good HTML/CSS developer can style any page in any way you want, so this isn't too big of a concern.
个性化。 CMS 可以 定制，但更糟糕的是 设计一些预制 html 的样式 设计一个预先设计的样式（因为你 想你想要怎样） html。
速度。
Web 标准 - 辅助功能 - 不显眼的 JavaScript
I think differently. A company website should be unique, personal, I thus I would avoid using a CMS.
Maybe you want a huge enterprise website, in this case a CMS will be better for you, but I'd rather write my simple content management than using a bloated, new hardware dependent website.
Oh, and the users will notice the difference in speed surfing through your hand-written website.
There are 3 points I think are important:
Personalization. CMSs can be customized, but it's much worse to style some pre-made html than styling a pre-styled (since you thought how you'd like it to be) html.
Speed.
Web Standards - Accessibility - Unobtrusive JavaScript
Most CMS's are very extensible. You have a framework to start with, and from there you can add whatever you want. Also since practically all CMS's have modules/components/plugins from their community, you can immediately add to the core with even more features for exactly what you need.
Andy's right, too. You can layer the design on top of the the CMS, and it's very easy to extend the front end even more with all the great JS libraries out there - which will be largely CMS & language agnostic, so if you ever migrate from one CMS to another you can still keep a large portion of that code, too.
In short, modern CMS's are mature, easy to set up, highly extensible and customizeable so ... Don't reinvent the wheel unless you have some very strong, specific, compelling reason to do so.
发布评论
评论（4）
首先让我们考虑以下选项：
无 CMS - 无工具：您拥有一位非常优秀的开发人员，具有强大的 HTML 背景、一些服务器端专业知识以及充足的时间。
没有 CMS，但有一个轻量级工具：您有一两个人熟悉 HTML 基础知识，您的网站大部分是静态的并且已经构建，但您需要更新 - 您可以考虑任意数量的工具来自（是的，确实如此）DreamWeaver、Aptana、Visual Studio WebExpres）
您有一个中小型 Web 团队，并且您有一个中大型网站这主要是内容。 我发现这是我见过的所有项目的大部分。 有时，这些类型的参与最终会出现在大型企业系统中，因为他们错误地理解了推动企业 CMS 的两三个主要因素（读取成本超过 250 美元，而且远远超过免费）。 像 WordPress 这样的开源博客引擎非常强大且可扩展。 添加像 LiveWriter 这样的免费编辑工具，你就拥有了很多分布式编辑能力，而且价格便宜，而且它可以处理很多事情，比如标准和 SEO，因为它在这方面构建得很扎实。 另外，还有很多人可以帮助你。 而且它的可扩展性很强。
企业CMS：
应根据三个因素来指导您做出有关 CMS 的决策：
大型分布式编辑团队需要严格（通常很复杂）的编辑工作流程。
网站设计和运营被认为次要于 CMS 提供的其他一些功能（简单的 SarBox 合规性、轻松支持将网站本地化为多种语言）
该产品的内部经验是积极的，并且已经证明了投资回报率 - 但要明确的是，购买许可证并不是部署的理由。 我见过太多这样的案例：购买了大型 CMS（获得许可）后却发现它无法满足项目的真正需求。 在某些情况下，客户是明智的并继续前进。 而另一些人则坚持购买，直到今天仍生活在一个充满伤害的世界中。
从简单开始，不断成长——网站的平均半衰期为 3 年。 犯一系列小错误，您可以通过快速迭代轻松纠正这些错误。 只有当你确定的时候才去买大东西。
立即感觉到您购买的数量超出了您的需要 - 在销售人员拜访您之前您无法了解产品的价格，并且在您参加他们的培训课程之前您无法获得系统的演示部分。 当你完成这些工作时，你就可以建立一个很棒的网站，并为你公司的每个人都买一些美味的酒。
First lets consider the options:
No CMS - No Tools: you have a very good developer with a strong HTML background, some server side expertise and plenty of time on his/her hands.
No CMS but a light weight tool: You have a person or two who are comfortable with the basics of HTML, you site is mostly static and it is already built, but you need to update - you can consider any number of tools from (yes it is true) DreamWeaver, Aptana, Visual Studio WebExpres)
You have a small to medium web team and you have a medium for large site that is mostly content. I have found this to be the bulk of all projects that I have every seen. May times thes types of engagements end up with a large enterprise system becasue they incorrectly understood the two or three of the main factors that should drive an Enterprise CMS (read costs more that $250 and way more than free). Open source blogging engines like WordPress are very powerful and extensible. Add in a free editorial tool like LiveWriter and you have a lot if distributed editorial power, cheap, and it takes care of lots of things like Standards and SEO because it is just build solidliy in that respect. Plus there are a lot of people who can help you out. And it is very extensible.
Enterprise CMS:
Three factors should guide your decisions regarding CMS:
Large distributed editorial team that requires rigorous (usually complex) editorial workflows.
The site design and operation has been deemed secondary to some other functioanlity provided byt the CMS (simple SarBox Compliance, easy support for localizing the site to many languages)
In house experience with the product that has been positive and has proven ROI - but be clear, having purchased licenses is no reason to deploy. I have seen far too many cases where a large scale CMS was purchased (licensed) only to find it would not suit the true needs of the project. In some cases the clients were wise and moved on. In others they stuck to their purchase and to this day live in a world of hurt.
Start simple and grow - The average website had a half-life of 3 years. Make a series of small mistakes that you can easily correct through fast itteration. Only go for the big stuff when you are sure.
Instant smell that you are buying more than you need - you can't find out the price of the product until a sales person visits you and you can't get demo bits of the system untl you attend their traning session. By the time you get done with that, you could have an awsome site up and be buying everyone at your firm some nice libations.
对于公司网站，如果您自己编写网站，您可能会重新发明 CMS 已经提供的很多内容。 您网站上的内容很可能会经常更改，并且公司可能会希望非开发人员维护这些内容。 通过您自己的实现，您必须为非开发人员提供管理页面来上传新内容（文本、图像、文档等），因此仅查看现有的 CMS 框架可能是有意义的。
CMS 的缺点是您可能必须解决样式问题才能为网站提供您想要的确切外观和感觉。 通常，优秀的 HTML/CSS 开发人员可以按照您想要的任何方式设置任何页面的样式，因此这并不是什么大问题。
For a company website, if you write your own, you're probably going to be reinventing a lot of what a CMS already gives you. The content on your site will most likely change frequently, and the company will probably want non-developers to maintain the content. With your own implementation, you'll have to provide management pages for non-devs to upload new content (text, images, docs, etc.), so it might make sense to just look at existing CMS frameworks.
The downside of a CMS is that you might have to work around styling issues to give the site the exact look-and-feel you're going for. Usually a good HTML/CSS developer can style any page in any way you want, so this isn't too big of a concern.
我的想法不同。 公司网站应该是独特的、个性化的，因此我会避免使用CMS。
也许您想要一个巨大的企业网站，在这种情况下，CMS 会更适合您，但我宁愿编写简单的内容管理，也不愿使用臃肿的、依赖于新硬件的网站。
哦，用户会注意到通过您的手写网站浏览速度的差异。
我认为有三点很重要：
定制，但更糟糕的是
设计一些预制 html 的样式
设计一个预先设计的样式（因为你
想你想要怎样）
html。
I think differently. A company website should be unique, personal, I thus I would avoid using a CMS.
Maybe you want a huge enterprise website, in this case a CMS will be better for you, but I'd rather write my simple content management than using a bloated, new hardware dependent website.
Oh, and the users will notice the difference in speed surfing through your hand-written website.
There are 3 points I think are important:
customized, but it's much worse to
style some pre-made html than
styling a pre-styled (since you
thought how you'd like it to be)
html.
大多数 CMS 都具有很强的可扩展性。 您有一个可以开始的框架，然后您可以添加任何您想要的内容。 此外，由于几乎所有 CMS 都有来自其社区的模块/组件/插件，因此您可以立即向核心添加更多功能，以满足您的需求。
安迪也是对的。 您可以将设计分层在 CMS 之上，并且可以很容易地使用所有出色的 JS 库（主要是 CMS 和 JS）来进一步扩展前端。 与语言无关，因此如果您从一种 CMS 迁移到另一种 CMS，您仍然可以保留大部分代码。
简而言之，现代 CMS 成熟、易于设置、高度可扩展和可定制，因此... 不要重新发明轮子，除非您有一些非常有力、具体、令人信服的理由这样做。
Most CMS's are very extensible. You have a framework to start with, and from there you can add whatever you want. Also since practically all CMS's have modules/components/plugins from their community, you can immediately add to the core with even more features for exactly what you need.
Andy's right, too. You can layer the design on top of the the CMS, and it's very easy to extend the front end even more with all the great JS libraries out there - which will be largely CMS & language agnostic, so if you ever migrate from one CMS to another you can still keep a large portion of that code, too.
In short, modern CMS's are mature, easy to set up, highly extensible and customizeable so ... Don't reinvent the wheel unless you have some very strong, specific, compelling reason to do so.