Chapter 1, Getting Started With SharePoint 2013 Search, gives you a taste of the new features SharePoint 2013 search brings to the table and then dives deep into the architecture that holds this system together.

Chapter 2, Using the Out of the Box Search Components, shows you how to use query rules and result sources and get a taste of building a simple search-driven application. SharePoint 2013 provides a rich out of the box experience for developing search-driven applications.

Chapter 3, Using the New CSOM and RESTful APIs, explains how to work with these new APIs and build a SharePoint hosted search-driven app using the new App developing approach. SharePoint 2013 changes the way we developers extend the platform by providing a whole new set of client-based APIs.

Chapter 4, Customizing the Look, focuses on creating display templates that define how a search result will render, and result types that define which display template a result should have. SharePoint 2013 opens up a whole new way to design our search results.

Chapter 5, Extending Beyond SharePoint, introduces how to create an external indexing connector and understand how to work with external data. In a real-world environment, not all the information we wish to search for is hosted within SharePoint. Business Connectivity Services (or BCS for short) enables us to extend beyond the realms of SharePoint and index data from external systems.

To run the examples shown in this book you will need a SharePoint 2013 server with Visual Studio 2012 installed.

If you don't have access to a full SharePoint 2013 server, Office 365's SharePoint Online and Visual Studio 2012 can also be used to run most of the examples in this book.

This book is written for SharePoint and JavaScript developers who wish to get started working with SharePoint search. The book assumes working knowledge with previous versions of SharePoint and some experience with JavaScript and client-side development.

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "We can include other contexts through the use of the include directive."

A block of code is set as follows:

[default]
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

[default]
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)

Any command-line input or output is written as follows:

# cp /usr/src/asterisk-addons/configs/cdr_mysql.conf.sample
     /etc/asterisk/cdr_mysql.conf

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "clicking the Next button moves you to the next screen".

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.