For many years organizations have used SharePoint to create Intranet environments, a single location that can be used as a starting point to obtain all the information needed for employees to complete their work. Because SharePoint offered a rich set of tools that allowed for non-technical users to update the content, it became a platform of choice for many organizations. SharePoint 2013 offers additional functionality that will greatly enhance SharePoint’s capability for providing these types of solutions internally.
Let’s look at some of the web content management features that are going to make developing an intranet within SharePoint 2013 a much nicer experience.
Reuse Content Across Multiple Sites
One of the pain points experienced in previous versions of SharePoint was around the fact that content that was created within one site collection could not easily be reused in a separate site collection. Since many organizations required multiple site collections, this limitation created a few cases where duplicate content was required.
With 2013, the concept of Cross-Site publishing has been introduced. When using this feature you can store and manage content in one location and then display the content in other site collections. Using this approach you can display the data in as many places that are needed, while still only managing and maintaining one single point of truth.
Navigation and User Friendly Links
Next up, are the new navigation features and the ability to base a navigation structure off of an existing term set. In many cases this allows for organizations to more centrally manage their environments and to provide meaningful navigation structures within the multiple site collections in their environment.
In addition to these updates in navigation, new features have been included that allow for the creation of friendlier names when linking to pages and content within SharePoint. In previous versions of SharePoint you were required to have longer URLs that contained references to the specific location you were trying to access. Within SharePoint 2013 you can now configure the URL so that it can be more easily referenced. An example of this would be the following two URLs:
- Previous SharePoint Versions: http://www.contoso.com/Pages/Computers.aspx#/ID=453&Source=http%3A%2F1010101
- SharePoint 2013 Friendly URL: http://www.contoso.com/Computers/model101
You can see that by removing the required URL parameters for ID and Source you are able to create friendly, memorable URLs for your sites and pages.
Changing Web Parts
We have covered a few aspects of creating and accessing content, but in most Intranets there is also a need to be able to “gather” and “present” data to users. In previous versions of SharePoint this was done through either the Content Query Web Part or a custom Roll Up solution.
Because of limitations in performance, the Content Query Web Part was restricted in how it could be utilized across organizations. If you had many users who needed to roll up a large amount of content it is likely that you could experience performance issues in using the web part.
SharePoint 2013 adds a new web part that will allow you to provide the same functionality as the Content Query Web Part, but is instead based on the search functionality available within SharePoint. Because this web part is based on search, many of the existing limitations have been reduced.
In SharePoint 2013 there are many new techniques that can be used to aide in the branding and customization of your sites. One of the biggest impacts is the ability to create a SharePoint custom design in any design tool of choice. This means your designers are not limited to only working within SharePoint Designer to build their custom design.