我在一家大型地方政府组织工作，该组织即将开始使用 SharePoint 将我们老化的内部网替换为一个能歌善舞的协作网站。 Intranet 的重点将是用 SharePoint 安装替换散布在整个组织中的随机文件、内容页面和文档，这将神奇地使所有这些变得有序。
已经做出在 Intranet 中使用 SharePoint 的决定。
我们在公共网站上使用的 CMS 也需要更换。 我建议使用 UmbracoCMS，但由于我们的 Intranet 上的 SharePoint 实施尚未完成，我的老板建议网站也使用 SharePoint。 他从纯粹逻辑的角度提出了这一建议，因为他不是开发人员，我可以理解为什么这种行动方针可能看起来是明显的前进方向。
我对使用 SharePoint 来覆盖我们的网站非常怀疑。 我们只需要它的实际“内容管理”元素，网站的其余部分由现有的 .NET 应用程序组成。
对于我们的 Intranet，使用 SharePoint 开发一些东西似乎是显而易见的，因为它将与电子邮件和 Office 集成，并允许共享内容并与我们的 Active Directory 集成（或者这就是我的假设）。
然而，我们的网站完全不同，包含许多应用程序以及陈旧的 CMS。 这是一个公共部门网站，因此网站的可访问性和互操作性是关键。 它需要易于使用并生成干净的可访问输出和有效的 XHTML 兼容代码。 我们的网站不需要 SharePoint 的任何协作或文档共享功能。
我对网站使用 SharePoint 的直觉是这是一个非常糟糕的主意。
我建议使用 UmbracoCMS 作为控件，我希望我们将拥有比 SharePoint 更好的控件，它与 .NET 的集成意味着我们将能够比 SharePoint 更轻松地将所有应用程序结合在一起。
有没有人有使用这两个产品中的一个或两个产品的经验，或者知道 SharePoint/Umbraco 中的任何很酷的功能，我可以让这更清楚一些？
I work for a large local government organisation who are about to embark on using SharePoint to replace our ageing intranet with an all-singing all-dancing collaborative site. The focus for the intranet will be replacing random files, content pages and documents that are spread across the organisation with a SharePoint installation which will magically bring order to all of this.
The decision to use SharePoint for the intranet has already been made.
The CMS we use on our public website also needs replacing. I have proposed using UmbracoCMS, but due to the pending SharePoint implementation on our intranet, my boss has suggested using SharePoint for the website too. He's suggested this from a purely logical point of view as he's not a developer, and I can understand why this course of action might appear to be the obvious way forward.
I am very skeptical about using SharePoint to cover our website. We would only need the actually 'content managerment' elements of it with much of the rest of the website being made up of existing .NET applications.
For our Intranet, developing something with SharePoint seems obvious as it will integrate with email and Office and will allow sharing of content and integrate with our Active Directory (or that's what I assume).
However, our website is completely different and contains many applications together with an archaic CMS. This is a public sector website so website accessibility and interoperability are key. It needs to be easy to use and generate clean accessible output and valid XHTML compliant code. We don't need any of the collaborative or document sharing features of SharePoint for the website.
My gut feeling with using SharePoint for the website is that it is an extremely bad idea.
I have suggested UmbracoCMS as the control I expect we will have will be greater than with SharePoint and it's integration with .NET means that we will potentially be able to knit all of our applications together more easily than with SharePoint.
Does anybody have any experience of using either or both of these products or know of any cool features in either SharePoint/Umbraco that I might make this a little more clear cut?
发布评论
评论（10）
在不了解您的完整要求的情况下，Windows SharePoint Services 3.0（相对于 Microsoft Office SharePoint Server 2007）是一个很好的解决方案。 许可是免费的，并且它作为面向公众的网站的框架运行良好。 使用 WSS 3.0，您将能够利用 MOSS 2007 基础架构、管理和用户培训。 我使用 SharePoint 为各种客户开发了许多成功的面向公众的网站，并对结果感到满意。
此链接提供了 WSS 3.0 和 MOSS 2007 之间的全面比较：
http://office .microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx
Without knowing your complete requirements, Windows SharePoint Services 3.0 (as opposed to Microsoft Office SharePoint Server 2007) is a good solution. Licensing is free and it works well as the framework for public-facing websites. Using WSS 3.0, you'll be able to take advantage of your MOSS 2007 infrastructure, administration, and user training. I have developed a number of successful public-facing sites using SharePoint for various customers and am happy with the results.
This link provides a comprehensive comparison between WSS 3.0 and MOSS 2007:
http://office.microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx
许多公共组织将 SharePoint 用于面向公众的互联网和协作网站。 当按照您的规范构建、设计和实施时，SharePoint 可以满足您所描述的要求（包括辅助功能要求）。
SharePoint 的真正问题（与任何主要的软件工程项目一样）是您拥有一支由有能力的专业人士组成的团队，他们知道自己在做什么。
以下是一些使用 SharePoint 的网站列表的链接，可帮助您更好地了解现有组织如何使用 SharePoint：
Many public organizations use SharePoint for publicly-facing internet and collaboration sites. When architected, designed, and implemented to your specifications, SharePoint can meet the requirements you have described (including the accessibility requirements).
The real gotchas with SharePoint (as with any major software engineering project) are that you have a team of competent professionals who know what they are doing.
Here are some links to lists of sites that use SharePoint to get a better idea of how existing organizations are using SharePoint:
SharePoint 可以用于面向公众的网站吗？ 哦，是的，确实如此。 如果您有疑问，请查看此网站：http://www.topsharepoint.com，您可以在其中您会找到诸如 Ferrari、沃尔沃汽车，国会图书馆，嘉士伯，维亚康姆，毕马威 和许多其他知名公司或政府组织。
必须承认，如果您仅依赖 Microsoft Office SharePoint Server (MOSS) 的开箱即用功能，SharePoint 可能会遇到辅助功能方面的挑战，但随着时间的推移，这些问题也都得到了解决。 ARF 是一个很好的示例，说明了如何解决其中一些问题（现在甚至可以制作 Web 部件来进行验证）。 另一个是 AKS，甚至微软也正式参与其中。 第三个是 BKS。
如果人们今天仍在 SharePoint 中创建非验证网站，很可能是因为他们没有进行彻底研究或没有优先考虑它。
如果您考虑到验证的挑战，我想说，既然您已经决定将 SharePoint 用于 Intranet，那么就没有理由不对您的公共网站也这样做。 事实上，在 MOSS 上运行的许多 Intranet 都基于它的 CMS 模板，因为这样您就可以两全其美。 大多数情况下，所有协作功能也可以轻松地为 CMS 站点启用。 事实上，您将获得一个非常成熟的、企业级的、可扩展的产品 i MOSS，它还包括一系列其他功能，例如简单的代码包部署、企业级搜索、工作流程、预定的服务器到服务器内容部署、详细的用户配置管理和一长串其他功能。
我可以继续谈论 SharePoint，但最后我不得不说，即使是免费的 WSS 部分也可以制作成 CMS 系统，这一点已被诸如 Tozit 和 CompleteSharePoint.NET 。 您很可能还会发现，如果您需要顾问或雇用人员来完成这项工作，那么让 SharePoint 人员加入比 Umbraco 更容易，这仅仅是因为支持 SharePoint 平台的大型社区。
Can SharePoint be used for public facing web sites? Oh yes, indeed. If you have your doubts, check out this site: http://www.topsharepoint.com, where you'll find sites such as Ferrari, Volvo Cars, Library of Congress, Carlsberg, Viacom, KPMG and a lot of other high profile company or government organizations.
Admitted, there can be accessibility-challenges with SharePoint if you rely only on the Out of the Box-features from Microsoft Office SharePoint Server(MOSS), but in time even these issues have all been addressed. The ARF is a nice example of how some of these issues have been addressed (and now even web parts can be made to validate). Another is AKS, which even has Microsoft officially involved. A third is BKS.
If people are still making non-validating sites in SharePoint today, it could very well be because they haven't researched thoroughly or aren't prioritizing it.
If you look above the challenges of validation, I would say since you've already decided on using SharePoint for intranet, there's very little reason not to do so for your public sites also. A lot intranets running on MOSS are in fact based on it's CMS-templates, because then you get the best of both worlds. All the collaborative features can, for the most parts, be easily enabled for CMS-sites as well. In fact you get a very mature, enterprise-ready, scalable product i MOSS which also includes a range of other features like easy code-package deployment, enterprise-ready search, workflows, scheduled server-to-server content deployment, detailed user-management and a long list of other features.
I could go on and on about SharePoint, but in closing I just have to say that even the free WSS-part can be made into a CMS system, proven by sites such as Tozit and CompleteSharePoint.NET. You will most likely also find, that should you need consultants or hire people for the job, it's easier to get SharePoint-people on board than Umbraco, simply because of the big community supporting the SharePoint-platform.
我的公司已经开始测试 Sharepoint Services (WSS 3.0)，因为它是免费版本，它缺少 MOSS (Sharepoint 2007) 的一些功能，但它是免费的，并且附带了公司可能需要的许多功能。 然而，它是微软的产品，所以它总是有一些许可“陷阱”。
WSS 在文档管理、团队协作、wiki/博客类型功能方面为我们内部工作得很好，它与 LDAP/Windows 身份验证集成（毕竟是 MS）。
My company has started testing Sharepoint Services (WSS 3.0) as it is a free version, it is short some features of MOSS (Sharepoint 2007) but it is free and comes with much of the things a company may require. However it is a Microsoft product so its always got some licensing 'gotchas'.
WSS has worked fine for us internally with document management, team collaboration, wiki / blog type functionality, it integrates with LDAP / Windows authentication (it is MS after all).
不要忘记将用户接受度纳入您的决定中。 如果有很多人更新网站，必须在两个不同的系统上进行培训很快就会成为 PITA。
Dont' forget to factor in user acceptance into your decision. Having to train on two different systems can quickly become a PITA if there are a number of people updating the site.
由于对 sharepoint 没有太多深入的了解（仅将其用于内部站点），我只能在 Umbraco 部分提供帮助。 作为一名开发人员，我喜欢对 xhtml 输出的控制，没有意外，而且非常灵活。 为美国以外的 Conde Nast 网站、Heinz、Hasselblad 等大型网站提供支持意味着它确实实现了规模化。 但是，我认为最大的资产是社区，如果您遇到任何问题或有疑问，很容易获得很大的帮助。 请参阅http://our.umbraco.org。 我还可以推荐这些视频，我认为这是学习基础知识的一种非常好的方法，与 Warren Buckley 的创意网站入门套件（可从包存储库中获取）相结合。
Without much deep knowledge of sharepoint (only used it for internal sites), I can only help out on the Umbraco part. As a developer I love the control I have over the xhtml output, no surprises and extremley flexible. Powering large sites such as Conde Nast sites outside USA, Heinz, Hasselblad + many more means that it does scale. But, I think the biggest asset is the community, it's so easy to get great help should you encounter any problems or if you have a question. See http://our.umbraco.org. I can also recommend the videos, I think it's a very nice way to learn the basics combined with the Creative Website Starter kit by Warren Buckley (available from the package repository).
我对 UmbracoCMS 一无所知，但我想说，使用共享点系统将允许您做现在需要做的事情，并将该功能扩展到未来。 作为对上述内容的补充，请记住，您将需要此外部站点具有某种发布功能。 WSS和MOSS可以容纳该功能。 内容迁移也很有趣，因为您可以在当前场上开发功能，然后有选择地将这些功能推送到外部场。
总结：
尽管设置仍然很麻烦，但如果您的拓扑是同质的，您将获得更好的管理体验。 毕竟，这就是你当前的问题……为什么要制造更多混乱呢？
Not knowing anything about the UmbracoCMS, i would say that using a sharepoint system will allow you to do the things you need to do now as well as extend that functionality into the future. As an additional comment to those made above, keep in mind that you will want some kind of publishing feature for this external site. WSS and MOSS can accomadate the feature. Migration of content is also interesting since you can develope functionality on your current farm and then selectivly push these features onto the external farm.
To sum up:
Though the setup is still a pain in the butt, you will have a much better administrative experience if your topology is homogenous. After all, this is what you current problem is anyway... why create more chaos?
在 MOSS 2007（外联网/内联网/互联网）上构建最大的面向公众的纯 Web CMS 站点之一的最后阶段，我可以相当自信地说，它作为一个 CMS 绝对是出色的。 协作门户？ 相当不错。 文件管理？ 一点也不差。 WCMS？ 可怕。 可怕。 远离。
为什么？ 当然你可以让它工作，因为有很多例子。 你可以从外面看一下成品，它看起来可能还不错。 但你不知道到达那里时发生了多少痛苦、挫折、成本超支、延误和普遍的糟糕情况。 相信我，可能会很多。
Being on the tail-end of building one of the largest public-facing, pure web CMS sites on MOSS 2007 (extranet/intranet/internet), I can say quite confidently that it absolutely blows as a CMS. Collaboration portal? Pretty decent. Document management? Not bad at all. WCMS? Awful. Horrible. Stay away.
Why? Sure you can make it work, as there are plenty of examples out there. You can look at the finished product from the outside and it might look pretty decent. But you have no idea how much pain, frustration, cost overruns, delays, and general badness happened to get there. Trust me, it can be quite a lot.
将 Microsoft Office SharePoint Server 用于公共网站的主要问题是许可成本非常高。 您将需要诸如 Office SharePoint Server 2007 for Internet Sites 许可证之类的东西。 Microsoft 定价页面上列出的价格为 41,134 美元。 除此之外，我发现 SharePoint 功能非常丰富，当然适合“标准 Intranet”以外的网站。
The main problem of using Microsoft Office SharePoint Server for your public web site is the very high licensing cost. You will require something like an Office SharePoint Server 2007 for Internet Sites license. The price is listed as USD 41,134 on the Microsoft pricing page. Other than that I have found that SharePoint is very feature rich and certainly suited for web sites other than the "standard intranet".
我不同意马丁的观点，认为高许可成本是主要问题。 主要问题是 Sharepoint 并不是为面向公众的网站设计的 CMS。 曾经看过 Sharepoint 默认输出的 HTML 吗？ 您可以解决所有这些问题，但我已经与这样做的人交谈过，他们都说将 Sharepoint 用于面向公众的网站没有意义。 因此，如果可访问性和互操作性很重要，请不要使用 Sharepoint。
我同意共享点非常适合构建内部网。
我认为 umbraco 是面向公众的网站的最佳CMS。 它旨在完全控制输入，您可以集成任何网站设计（无限制），并且可以使用现有的 .net 控件。 这就是为什么我在 2007 年选择 Umbraco 作为我的客户的默认 CMS。
干杯，
Richard
I don't agree with Martin that the high licensing cost is the main issue. The main issue is that Sharepoint isn't designed to be a CMS for public facing websites. Ever looked at the HTML that Sharepoint spits out by default? You can fix all those issues but I've spoken to people who did that and they all say that it doesn't make sense to use Sharepoint for your public facing website. So if accessibility and interoperability are important don't use Sharepoint.
I'll agree that sharepoint is great to build an intranet.
I think umbraco is the best cms for public facing websites. It's designed to have full control over the input, you can integrate any website design (No limitations) and you can use your existing .net controls. That's why I've chosen Umbraco as the default CMS for my customers in 2007.
Cheers,
Richard