Benefits of SharePoint 2016 over SharePoint 2007
Increased Browser Support
Part of Web Content Management is accessibility.
SharePoint 2007 is for the most part jailed to
Internet Explorer. Sure, you can load any SharePoint
site in Firefox or Chrome, but it’s not fully
supported and several features do not function
correctly. SharePoint 2016 supports several commonly
used web browsers, like IE 10, Firefox and Chrome.
Better Rich Text Editor
The new and improved Rich Text Editor (RTE) provides a
"Word-like" editing experience that most people take
for granted in a non-browser world. The RTE in
SharePoint 2016 provides rich formatting of text, live
preview of formatting options, easy embedding of
images and videos directly into the RTE and drag and
drop capability to place them exactly where you want.
The rich editor integration with the new UI and ribbon
will cut down on page loads, it shows quick access to
the tools and actions you use most often, and
automatically updated to the content you are working
on.
E.g. it will shows media options when you are working
on an media web part.
Easily able to add Rich Media eg. a YouTube link
SharePoint 2016 makes it easy for authors to select
and add rich media content (like images, audio, video
and Silverlight controls) to their pages. Authors have
quick access to Media, Video and Silverlight Web Parts
that they can add to their pages. We’ve also
introduced a new experience for selecting rich media
content that has features like getting to preview and
play the video before you select it.
Device Channels
One of the new capabilities of SharePoint 2016 are
Device Channels. Using Device Channels you can
optimize how your website is displayed on different
devices. By using different Master Pages with
different channels and by ensuring the right markup is
generated using the Mobile Panel controls, you can
improve the user experience for all the different
devices.
Responsive Design (Dynamically changing via Page
Layout templates)
Page Layouts (templates) provide a way to apply a
consistent look and feel to a page. In SharePoint
2016, changing page layout is as easy as picking a
layout from a gallery in the Ribbon while the author
is editing the page.
Managed Metadata service
This helps solidify SharePoint as a solid web-based
tool for managing content across all of your sites.
SharePoint 2016 introduces a powerful set of features
around defining and managing taxonomies and then
leveraging those "terms" to tag content in SharePoint.
Leveraging these managed metadata fields in web
content enables scenarios around showing dynamic
content (discussed above), driving dynamic navigation
based on metadata and helps with search engine
optimization.
Friendly URLs
By using managed navigation and category pages, the
URLs of category pages can be built from the terms
that you have specified in the term set, such as
Computers or Marketing. For individual catalog items,
you can specify that the URL consists of additional
properties from the library or list that is shared as
a catalog. This lets you create more meaningful,
user-friendly URLs, instead of having URLs that
consist of strings that do not make sense to users. In
SharePoint Server 2016, the URLs for publishing sites
included the name of the Pages library — for
example,
www.contoso.com/Pages/Computers.aspx#/ID=453&Source=http%3A%2F1010101
. In SharePoint Server 2016, you can create URLs that
are more user-friendly — for example
www.contoso.com/Computers/model101
.
Better CSS (Web site styling) without being so table
heavy
Sharepoint 2016 uses DIV instead of tables which
provides faster loading pages.
Web Analytics
An important part of any site is understanding what is
going on with the content, users and the servers
powering the site. SharePoint 2016 provides a range of
new Web Analytics capabilities that monitor different
aspects of site usage. In addition to the out of box
reports, you can subscribe to alerts to monitor
changes on key metrics. Beyond traffic insight, there
is support for search insight around search queries,
popular terms and queries that are succeeding or
failing. It also recommends new best bets for the
search system by watching what links people are
clicking on the search result page so you can promote
these to the top of the page.
Server Health Monitoring
SharePoint 2016 has made some big investments in
logging infrastructure from the analytic side that
will help you monitor the performance of your
SharePoint deployment. You can now easily find the
slowest pages (in terms of rendering) on your site. So
in case you have customization where you have one or
more Content Query Web Parts making expensive queries
and forgot to turn on caching then we’ll help
you find that page. Since sites are highly customized
with custom web parts and field controls, we’ve
introduced the Developer Dashboard feature that allows
a developer investigating why a certain page renders
slowly to see at a page level which queries went to
SQL backend and how long they took. Introduction of
Sandboxed solutions allows site administrators to
upload custom code that runs in its own sandbox in a
way that it can be monitored and throttled so it
doesn’t impact the quality of service to other
users on the farm.
Image rendition (automatically reduces)
Finally, SharePoint Server 2016 supports image
renditions. Image renditions let you display different
sized versions of an image on different pages. When
you create an image rendition, you specify the width
and height for all images that use that image
rendition. For example, if the site has a news article
page layout that contains an image field, you can
create an image rendition named Article_image to
display the full-sized image in the article page. A
second image rendition named Thumbnail_small can be
used to display a smaller version of the image
associated with a particular article when the image is
displayed in a Web Part that lists all recent news
articles on the site home page. To use image
renditions, you first define the image rendition
sizes. Next, you generate the default image preview by
uploading an image, which you can adjust if it is
necessary. Finally, you add the image to a page and
specify which image rendition to use on that page.
By default, the image preview that is displayed for an
image rendition is generated from the center of the
image. You can adjust the image preview for individual
images by selecting and resizing the portion of the
image that you want to use as the image preview. For
example, if a photo contains a person’s face but
the default image preview does not show the whole
face, you can change the selected image area so that
the whole face is displayed.
Image renditions let you have large source images on
the site and also have places on the site where pages
only use smaller versions. This reduces the size of
the file that is downloaded to the client, which
improves site performance. Image renditions also let
you have multiple versions of the same image that are
cropped differently without having to upload multiple
images. This reduces the storage space that is
required for images. Finally, image renditions are
useful in mobile scenarios, where different versions
of images can be displayed based on the device that is
used.
Cross Site Publishing when you have multiple websites
Cross-site publishing lets you store and maintain
content in one or more authoring site collections, and
display this content in one or more publishing site
collections. When you change the content in an
authoring site collection, those changes are displayed
on all site collections that are reusing this content.
Cross-site publishing uses search technology to
retrieve content. On a site collection where the
Cross-Site Collection Publishing feature is enabled,
libraries and lists have to be enabled as catalogs
before the content can be reused in other site
collections. For more information, see Catalog-enabled
libraries and lists. The content of the library or
list catalogs must be crawled and added to the search
index. The content can then be displayed in a
publishing site collection by using one or more
Content Search Web Parts. For more information, see
Content Search Web Part.
Managed Navigation
Managed navigation lets you define and maintain the
navigation on a site by using term sets. Managed
navigation supplements the existing SharePoint
navigation that is based on site structure. You create
the managed navigation structure by adding terms to
term sets in the Term Store Management tool. You can
copy the navigation term set and translate it into the
same languages that are used for variations labels.
App Support for extensibility
Apps provide easier discovery & installation.
Microsoft now provides an app store which is
seamlessly integrated into SharePoint 2016 which
allows you to access a marketplace where you can
purchase additional components. Developers can now
easily write applications and use the app store deploy
this additional functionality which you can easily add
to your SharePoint site.
The following are the advantages of Apps from the
Developer perspective:
-
Web Programming skills are reusable in creating Apps
-
Common web standards of HTML, JavaScript, CSS can be
used to develop Apps
-
Opportunity to create & publish Apps to the
SharePoint store, which could be installed on
different SharePoint site
-
More potential in developing revenues through Apps
Sharepoint Search service
Without having to open each search result, users can
quickly identify useful results in ways such as the
following:
-
Users can rest the pointer over a search result to
preview the document content in the hover panel to
the right of the result
-
Users can quickly distinguish search results based
on their type. For example, Microsoft Office
documents display the application icon in front of
the title of the search result. Newsfeed
conversation results display the number of replies
and the number of likes to the right. Site results
list the top links that users often click on the
site. People in results show the picture and the
Lync availability status to the left
-
By default, certain types of related results are
displayed in groups called result blocks. A result
block contains a small subset of results that are
related in a particular way. For example, results
that are PowerPoint documents appear in a result
block when the word "presentation" is one of the
search terms. Administrators and site owners can
also create result blocks to group other results.
Like individual search results, you can promote
result blocks or rank them with other results
Book a SharePoint Expert