在不同的 CMS 系统中进行开发是否有益？
目前，我们正在开发 Sitecore 网站，并且每天都在积累经验。这意味着我们知道如何针对不同类型的客户调整我们的方法，并且我们能够更快地构建我们所做的每个项目的应用程序。当然，Sitecore 并不是唯一的 W-CMS，我们还研究了其他 W-CMS。 公司在不同类型的 CMS 中提供解决方案的优点和缺点是什么？这对于使用该 CMS 的程序员意味着什么？ 选择在更多 CMS 中提供解决方案是否会自动意味着每个 CMS 的全局体验会相对萎缩？ 希望周围有人拥有多个大型 W-CMS（Sitecore、KEntico、EPIServer 等）的经验。
At this point we are developing Sitecore websites and we are gaining experience every day. This means that we know how to adjust our approach to different types of customers and that we are able to build our applications quicker every project we do. Of course Sitecore is not the only W-CMS around and we have looked into other W-CMS's.
What are the pro's and the con's for a company to offer solutions in different types of CMS's and what would this mean for the programmers that are working with this CMS?
Would a choice to offer solutions in more CMS's automatically mean that the global experience per CMS will shrink relative?
Hope there are some people around with experience in multiple big W-CMS's (Sitecore, KEntico, EPIServer, etc.. etc..).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您真正喜欢使用 Sitecore，不妨考虑 Umbraco。 Umbraco 与 Sitecore 非常相似，而且更便宜（我相信前 Sitecore 员工甚至可能在那里工作）。提供高价 CMS (SC) 和同样基于 .NET (Umbraco) 构建的较便宜的替代方案可能会很好。我想说不要尝试支持大量的 CMS，因为数量太多了。重点关注少数几个。也许可以考虑根据其他人的市场以及他们的合作伙伴计划的运作方式来选择其他人（例如 Sitecore 会推荐您作为解决方案合作伙伴并帮助您进行销售）。
If you truly enjoy working with Sitecore than maybe consider Umbraco. Umbraco is very similar to Sitecore and cheaper (I believe former Sitecore employees may even work there). It might be nice to offer a high-priced CMS (SC) and a less expensive alternative also built on .NET (Umbraco). I would say don't try to support tons of CMS's since there are so many. Keep a focus on a select few. Maybe consider selecting others based on the market for them and how their partner programs work (i.e. like Sitecore will recommend you as a solution partner and help you with sales).
您准备好让您的程序员技能掌握您提供的每种不同的 CMS 解决方案了吗？如果您基于不同平台提供多种不同的解决方案，例如，如果您的程序员必须了解 C#、Java 和 PHP，因为这是各种 CMS 支持开发的内容，那么这可能会是很高的成本。因此，您可能希望坚持使用 .Net CMS，而不是过于冒险地进入不同的堆栈，因为这可能会带来维护技能的挑战。
Are you prepared to keep your programmers skills on top of each of the different CMS solutions you'd offer? That can be a high cost if you offer a number of different solutions based on different platforms,e.g. if you have programmers that have to know C#, Java and PHP because in this is what the various CMS support development be done. Thus, you may want to stick to .Net CMS rather than go venturing too far into a different stack as that can carry the challenge of maintaining skills.