Build sites for SharePoint
Learn about the new site authoring and publishing model for websites in SharePoint.
Introduction to site publishing for designers and developers in SharePoint
SharePoint introduces a site authoring and publishing model to create publishing sites. You can use publishing sites to publish content on intranet or Internet sites. Publishing sites differ from other types of SharePoint sites, such as team sites, mainly due to their purpose—many users read publishing site content, but only a few contribute by adding, updating, and deleting content from one or more site collections. Contrast these sites with team sites, where many people may collaborate and contribute to the content.
Authoring and reusing site content.
Branding and designing your site's look, feel, and behavior.
Managing metadata—you can build a taxonomy-driven site navigation system.
Publishing content smoothly to the current site collection, or publishing content across site collections—even spanning the intranet and Internet site boundary.
Accessibility—you can use to improve the accessibility of your published sites.
If you want to see a summary of what's new for designers and developers of publishing websites in SharePoint, see What's new with SharePoint site development.
Authoring, design, and branding in SharePoint
SharePoint also provides a new approach to content and authoring. The content-creation workflow is revised so that you can create content using any authoring and branding tool and author great content. To brand your site without having to write custom ASP.NET code, use the Design Manager. You can import design elements and create an HTML-based master page to define the shared framing elements—the chrome—that all of your site's pages and page layouts share. If you choose to write custom code when branding your site, you can use the publishing and taxonomy libraries.
Publishing sites, client object model programming, and the new SharePoint app model
Page model for publishing websites
SharePoint includes a page model for publishing websites. The page model includes master pages, page layouts, and other components that render your site structure, content, look and feel, and behavior. To learn more, see Overview of the SharePoint page model.
Master pages and page layouts
A master page is the main template that defines the shared structural elements of your site—the chrome. All of the pages on the site share these elements, which define the regions of the page that display page layout content.
Page layouts are used by individual pages of a certain type. They are populated with arrangements of page fields. These pages define individual elements on the page. Individual pages are based on page layouts and are created in your web browser either by custom code or by how the site's users fill out the page's fields. To learn more about the page model in SharePoint, see Overview of the SharePoint page model.
Client-side rendering controls
Sites and mobile devices
Publishing websites in SharePoint are optimized for mobile development. You can define channels for one or more devices (device channels) and assign an alternate master page for each channel, giving it unique structural elements, or chrome. You can choose to include or exclude portions of any page layout in a channel, and preview how mobile channel design is progressing while it's being developed.
Metadata and navigation in SharePoint
Managed metadata capabilities introduced in Microsoft SharePoint Server 2010 are improved and extended in SharePoint for better performance, easier access through the user interface, and taxonomy-driven navigation—called managed navigation. You can use managed navigation or navigation based on the SharePoint website structure—called structured navigation—to build your site navigation. To learn more about managed navigation, see Managed metadata and navigation in SharePoint and Managed navigation in SharePoint.
Publishing content in SharePoint
SharePoint offers the following new content publishing features that enable you to develop publishing sites that support more flexible, more accessible, and more complex topologies and scenarios.
SharePoint introduces catalogs, which you can use to publish content across site collections. Cross-site publishing features depend on catalogs. You can use them to reuse content across your sites and across the boundary between your intranet sites and Internet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the Content Search web part in SharePoint.
SharePoint introduces a cross-site publishing feature to reuse content across multiple site collections. It uses built-in search capabilities to enable publishing scenarios and architectures. For the first time, you can design sites that cross SharePoint farms—enabling your sites to span the boundary between intranets and the Internet. You can use the CSWP to display search data published from across sites and site collections.
Variations and multilingual sites
You can use the variations feature in SharePoint to create multilingual sites or other sites where you want to vary the presentation of your content. The variations feature is constrained to one site collection. That is, you can create target language/locale "variants" of a source language/locale as current websites within the same SharePoint site collection. Variations supports friendly URLs and the ability to export or import content for translation by a third party in XLIFF file format. You can include labels, a page for translation and replication, a variety of list items (for example, document libraries.md), and navigation in your export packages.