SharePoint 2013 does great job configuring things for you in search-driven publishing scenarios but there are a few things you should keep in mind to save yourself trouble.
With the recent release of Office Delve and Office Graph I decided to change my session and present about leveraging Office Graph for building custom solutions.
Today I released the Single Page App version of mavention.com.
Content Targeting with User Segments just works with Content Search Web Parts but some additional work is needed if you want to leverage it with the Search REST API.
Leveraging SharePoint 2013 Search REST API for anonymous users allows you to build powerful search-driven solutions. Often, particularly in the early stages of the project, queries might not work as expected. So how do you find out what’s wrong?