SharePoint 2013 Highlights: Better BI, Mobile, Public Website Support

Better branding for Your Web Presence. What used to be an arduous process that involved complicated designer assets, style sheets and a confusing packaging process has now been made much easier. Now, any Web designer with proficiency in HTML, CSS and JavaScript can in a short amount of time brand a SharePoint site and create a public-facing or internal site that looks good. This will reduce your internal support expense, as well as make it less costly to use SharePoint itself as a platform for public-facing websites.

Improved public-facing website hosting. Hosting a public website (e.g., your .com site) on SharePoint 2007 was an exercise in frustration. Hosting that same site on SharePoint 2010 was better, but that product wasn’t as full-featured as some competing platforms.

SharePoint 2013’s capabilities in this regard are a natural evolution into maturity. The new release includes the capability to serve up pages to different devices (such as mobile phones and tablets) based on their characteristics. SharePoint 2013 also includes numerous features for search engine optimization (SEO), including XML based sitemaps, friendly URLs, SEO settings by different site collections rather than sites, and robots.txt support to define out of bounds areas for search engine crawlers.

Enhanced business intelligence. Using SharePoint as a platform to expose business intelligence and big data reports had its coming-out party with the 2010, but the capabilities have expanded in the 2013 release to really make SharePoint the choice to dig deeper into business insights and analytics. Integration between SharePoint and Excel is even tighter, too.

Finally, the PowerPivot program has gotten even more powerful in SharePoint 2013; you can work with billions and rows and columns directly in memory, while features such as PerformancePoint Services, Dashboard Designer and Visio Services all work together to paint a picture of your business’ health and metrics.

End-user training. SharePoint 2013 includes a new feature called “deferred site collection upgrade.” This essentially lets a specific set of site collections run under SharePoint 2010 while SharePoint 2013 code is installed. You are basically running SharePoint 2010 code within the 2013 product, which makes it easier to test and maintain compatibility with any custom code and applications you have built on top of SharePoint.

It also eases the transition for your users between the look and feel of how SharePoint 2010 libraries and sites operates. You can get the benefit of deploying the new product while you manage the timeline on which you convert the look and feel of your site and turn on the new features and capabilities that face your end users. This is a good thing.