- Introduction to Creating High-Performance SharePoint Server 2007 Publishing Sites
- Benchmarking a SharePoint Server Publishing Site
- Resolving Common Coding Performance Issues
- Taxonomy: Designing Site Structure and Authorization
- Improving Page Load Time in Publishing Sites
Microsoft introduced the capability to create, host, and maintain content-centric Internet-facing sites in Microsoft Office SharePoint Server 2007 with Web Content Management (WCM) and publishing sites. Previous versions of SharePoint, either Windows SharePoint Services 2.0 or Microsoft SharePoint Portal Server 2003, were not designed to be Internet-facing solutions. Internet-facing solutions have some requirements that are different from those that are not Internet-facing. When building Internet-facing sites, developers and designers must handle higher concurrent client requests, consider multiple user agents, and consider multiple connection speeds—among other things that are not usually as critical in internally facing sites.
This article addresses some of the more important aspects developers and designers need to consider when creating Internet-facing Office SharePoint Server 2007 publishing sites. Some of the guidance in this article can be applied to any site based on Windows SharePoint Services 3.0, including publishing sites, while other things are exclusive to Office SharePoint Server 2007 publishing sites. This article also contains information specific to developers, designers, or those who are implementing Internet-facing Office SharePoint Server 2007 publishing sites. It does not address information architecture, server or network topology, or other administrator or IT professional-related topics; the primary audience is those who are actually building publishing sites.
This article uses the sample Office SharePoint Server 2007 publishing site Adventure Works Travel. This sample site is a good subject because it contains a custom branding with many external files references and sample content.