任何人都在 Sharepoint 网站上使用过 CSS 蓝图
有人在 Office Sharepoint 服务器发布网站上使用过蓝图 (http://www.blueprintcss.org/) 吗？ 如果是，你觉得怎么样？ 有什么问题或问题吗？ 它真的可以节省时间并轻松地使网站在跨浏览器上正常运行吗？
Anyone used the blueprint (http://www.blueprintcss.org/) with Office Sharepoint server publishing sites?
If yes, what do you think? Any catches or problems ? does it really save time and make it easy to make the site working fine cross browsers?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
去年，我在一个项目中使用了带有 SharePoint (MOSS) 的 Blueprint CSS。
我是一名英国承包商，这是一个为期 3 个月的项目，有 1 名技术资源（我）。 所涉及的公司（为银行业提供服务的英国大型公司）已有一个 Intranet 安装，并希望迁移到基于 MOSS 发布站点的 Intranet。
该设计是基于固定宽度 (960px) 的列，因此我查看了当时可用的 CSS 框架，蓝图看起来简单而灵活（设计工具位于 http://kematzy.com/blueprint-generator/ 来构建自定义网格）。
Blueprint 本身运行良好，我使用它遇到的问题与任何涉及对母版页/页面布局进行大量自定义的 MOSS 项目几乎相同。 我最终编写了自己的重置 CSS，而不是使用默认 CSS，因为我不想完全破坏 MOSS 样式。 陷阱：
话虽如此，它与母版页配合得很好，并且非常适合页面布局（不同的列/布局以及具有“杂志风格”首页）。 我们用空闲的时间完成了这个项目，所以是的，我会再次使用它并推荐它 - 只要你乐于很快地深入了解 CSS。
I used Blueprint CSS with SharePoint (MOSS) on a project last year.
I'm a UK-based contractor and this was for a 3 month project with 1 technical resource (me). The company involved (large UK company providing services to the banking industry) had an existing intranet installation and wanted to move to a MOSS publishing site based intranet.
The design was column based with a fixed width (960px) so I took a look at the CSS frameworks available at the time and Blueprint looked simple and flexible (design tool at http://kematzy.com/blueprint-generator/ to build a custom grid).
Blueprint itself worked well, and the problems I encountered using it would be pretty much the same as any MOSS project that involves large customisations to the master page / page layouts. I did end up writing my own reset CSS rather than use the default one as I didn't want to completely clobber the MOSS styles. Gotchas:
Having said all that, it worked well with the master pages and was great with page layouts (different columns/layouts and having a 'magazine style' front page). And we got the project done with time to spare so yes, I'd use it again and recommend it - as long as you're happy to be knee-deep in CSS quite quickly..
作为一名辅助功能传播者，我也走上了使用蓝图的相同道路，努力使事情更加符合标准。 说实话我不会再这样做了。
试图击败 MOSS 2007 并使其易于访问是注定失败的。 即使是像 AKS（SharePoint 辅助工具包）这样伟大的项目，也只不过是向由过时的 .NET 控件呈现的大量嵌套表添加一个摘要参数而已。
如果不重写所有这些控件，就没有任何意义。 不使用太多这些的 SharePoint 发布网站可能会更容易管理。 但在我看来，你最好还是等待 2010 年，它在这方面做得更好。
如果现在满足 WCAG 很重要，那么您最好选择另一个开箱即用的 CMS，或者至少让我们您轻松完成此任务。
Being an accessibility evangelist I also went down the same path of using Blueprint in an effort to make things more standards-compliant. TO be honest I would not do it again.
Trying to beat MOSS 2007 into submission and make it accessible is a lost cause. Even great projects like the AKS (Accessibility Kit for SharePoint) do little more than add a summary paramater to the swarm of nested tables rendered by woefully out-dated .NET controls.
Short of rewriting all these controls there's just no point. SharePoint publishing sites that don't use too many of these might be slightly easier to manage. But IMO you'd be better of waiting for 2010 which does a much better job of this.
If meeting WCAG is important now then you're far better off going with another CMS that does this out-of-the-box, or at least let's you do it without too much pain.