问题描述
我想选择一个CMS作为我公司网站的基础架构的一部分。
在我真正选择一个之前，您需要问什么问题？
选择一个CMS就像选择一个框架。
I want to choose a CMS that will be part of my infrastructure for my company websites.
What do you think are the questions I need to ask before I really choose one?
Choosing a CMS is almost like choosing a framework.
谢谢
推荐答案
您的两个初始问题应该是关于人：
Your two starting questions should be about people:
- 谁将负责构建和维护该技术？如果您的组织的IT部门喜欢Microsoft解决方案，那么找到最好的.NET CMS，以满足您的需求（Umbraco，Kentico，DotNetNuke等）。如果你没有钱，但你是相当IT精明，有几个Web设计师轻轻地帮助你，然后一个设计师友好的免费系统，如是有意义的。如果你的一些人已经使用像Drupal这样的大系统，那么这是你的主要候选人。
- 谁将向系统添加内容？内部用户将需要一个奖励使用的界面 - 它必须快速反应，保护用户不会失去他们的工作，使内容容易找到，并简化任务，如创建新的页面，包括链接和图像。这可能会推动你走向CMS Made Simple，或者甚至WordPresss，如果你的需求是适度的。如果大部分内容是由用户社区贡献的，CMS必须支持强大的论坛功能。
- Who will be building and maintaining the technology? If your organisation's IT department is in love with Microsoft solutions, then find the best .NET CMS that meets your needs (Umbraco, Kentico, DotNetNuke etc). If you have no money but you're fairly IT-savvy and have a couple of Web designers on tap to help you out, then a designer-friendly free system like MODX Revolution makes sense. If some of your people have worked with a big system like Drupal, then that's your leading candidate.
- Who will be adding content to the system? Internal users will want an interface that rewards use - it must react fast, protect the user from losing their work, make content easy to find, and ease tasks like creating new pages and including links and images. That might push you towards CMS Made Simple, or even WordPresss if your needs are otherwise modest. And if most of the content will be contributed by a user community, the CMS must support a strong forum capability.
请参阅步骤2的文档 如何评估内容管理系统 。这些家伙知道他们的东西。您甚至可能想购买他们的内容管理要求工具包。他们的评估文档为您提供了评估的起点。
After that, take a look at Step Two's document How to evaluate a content management system. These guys know their stuff. You may even want to buy their Content Management Requirements Toolkit. Their evaluation document gives you a starting point for your evaluation.
请记住，不是所有的要求都是相等的。例如，许多CMS文本强调复杂的工作流和版本控制的重要性。在大型出版业务中，这些有时候很重要。在大多数小型组织中，他们并不重要。您的工作流程可能包括一个人将内容放入系统，另一个人批准它上线 - 这是可以通过分段服务器和电子邮件完成的任务。版本控制可以由常规备份充分覆盖。
Do bear in mind, though, that not all requirements are created equal. For instance, many CMS texts stress the importance of complex workflow and versioning. In large publishing businesses, these sometimes matter a lot. In most smaller organisations they don't matter as much. Your workflow may consist of one person putting content into the system and another approving it to go live - the sort of task that can be accomplished with a staging server and email. Versioning may be adequately covered by a regular back-up.
请记住，当您将CMS放在现有组织中时，您从事政治。你需要找出人们想要什么，告诉你提供它，向他们解释他们不知道但必须考虑的考虑，并说服他们你的行为，以使他们最好的工具。祝你好运。
And remember above all that when you put a CMS in an existing organisation, you're engaging in politics. You need to find out what people want, show you're delivering it, explain to them the considerations which they don't know about but which have to be taken into account, and convince them you're acting to bring them the best possible tool. Good luck.
这篇关于在选择CMS之前需要提出什么问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！