For example, if you want to query content across sites and/or across domains, SPServices will be a better way to go. There are no Content Editor Web Parts to delete or edit accidentally.Ī note of caution: before committing to this simple, customizable Nivo slider for SharePoint, consider that an approach such as Mark Rackley’s SPServices-based slider may be preferable, depending on your requirements and the architecture of your environment. Create a slider from any list or list view containing the required columns. uses out of the box functionality: a SharePoint list and simple configuration using views.It is also just as easy to implement – and far simpler to customize – than the out of the box Content Search Web Part slider Display Templates available in SharePoint 2013. This out of the box XSLT approach has some major advantages relative to using heavier weight scripting (in the form of CSOM or SPServices) that may be used to query a SharePoint list and construct a slider.
The full, customizable SharePoint jQuery Nivo slider XSLT is provided at the end of the post. This post shows how you can do just that: create a simple, reusable, customizable jQuery Nivo slider from a SharePoint list. Hardly surprising, then, that SharePoint folks should want to harness the power of Nivo within SharePoint 2013 (or SharePoint 2010) without the need for custom development, and driven only by a standard SharePoint list. Nivo slider is the industry standard, and understandably so: a versatile, customizable jQuery content slider used on at least 2.5 million web sites to date. So, what if you could create a jQuery Nivo slider from a SharePoint 2013, 2010 or O365 List using only out of the box functionality (and a single file in your Style Library) – allowing anyone to deploy a custom slider simply by adding a standard list Web Part to a SharePoint page?įigure 1: a custom jQuery Nivo slider driven by a SharePoint list Quality, reusable, customizable SharePoint sliders are frustratingly few and far between.
0 kommentar(er)
