Partner Webinar Patrick Schweizer Director of Sales Enablement pas@sitecore.net May 2013 Page 1
Quick Info Important New Features: Item Buckets The ability to store a LOT of content, any content Upgraded Search (Lucene with support for SOLR) much faster with many new capabilities bring OOTB search on the same level as 3 rd party enterprise search solutions. Search Facets, Tags, and Boosting features contributing to finding relevant content quickly. Component Content Queries retrieve content for a component by using a search query New Development Tools and Search API lets developers retrieve the right content with fewer lines of code. Demo Availability A complete demo-deck will be available on SPN this week A downloadable demo available towards the end of June. Page 2
Why does Sitecore 7 matter? The opportunity: With the explosion of new trends such as social, the quantity of content has increased exponentially. Not all content can fit into a standard tree structure anymore and marketers needs to quickly and accurately retrieve this content to provide a relevant and personalized experience. The benefit: Sitecore 7 can scale to massive amounts of content, and allow users to search, filter and target that content in more sophisticated ways than ever before. The differentiator: Sitecore 7 empowers the marketer with settings and features that are usually available to developers. Controlling search optimization and personalized content queries all through a simple interface allows for frequent fine-tuning to a customer s experience. Rapid development with tools such as LINQ Page 3
Problems that Sitecore 7 solves I have 1.3 million products, I don t need all the content to live in Sitecore but I want to be able to use all CEP features. My customers need to be able to refine their search results quickly and we want to easily be able to manage their search experiences. Our promotion department needs a way prioritize featured products during a search. I know my customers are using words when searching for our content that are not returning any results. The list of services on the home page frequently change and manually choosing them takes too much time. The development and configuration time of our new system needs to be significantly shorter, our ROI needs to start in the same year as the software purchase Page 4
Sitecore 7 Goals Store and retrive a LOT of content Sitecore customers can store, but more importantly, easily manage massive volumes of content. Content and websites don t always fit neatly into tree structures, and customers certainly don t feel compelled to adhere to a website s navigation. Better way for developers to access content New content access APIs such as LINQ make quering content easier with less lines of code. Development and testing time can be reduced dramatically with content structures now being higly visible durring the coding process. Provide a best in class search and personalized experience Search facets, result boosting, and tagging give the customers a relevant as well as immediate search experience. Once static lists of content now can be dynamic and based on personalized queries, easily defined by marketers. Page 5
What will Sitecore 7 do for customers? Content and promotions at scale Old content does not need to be deleted or archived for performance reasons if its still relevant Marketers do not need to be selective with content streams, the more the merrier. Reduce the need for a marketing army The same person that maintains content can also manage search. The content maintenance process is not longer a look in every room process but instead a quick and actuate search. Quicker development = lower start up cost = 100% ROI sooner New development tools and methods that are all designed to streamline common tasks. Fewer lines of more simple code result in fewer initial bugs and shortened testing. Page 6
New Sales Opportunities Heavy social collaboration sites Organizations in which social content is key to their business. They must have copies of this valuable content and local storage is best way to moderate the social channels. Content aggregators Sites looking to pull in as much content as possible from external feeds. Manufactures with HUGE product catalogs Management and import of very large product catalogs Syndication of product information to resellers Resellers with many product information sources PIMS systems that reside at the manufacture Syndicated product information streams Pulling from multiple/external product review sources Page 7
Sitecore 7 New Features Page 8
Item Buckets I have 1.3 million products, I don t need all the content to live in Sitecore but I want to be able to use all CEP features. Now store 10s of millions of content items. Free-from-the-tree items are now retrieved using a search tool instead of traversing the content tree. A bucket can contain many different types of content and have some shared attributes. Batch operations can take place on a list of results such as group tagging. All Sitecore content (bucked and non-bucketed) are returned in the new search tool. Page 9
Search Facets My customers need to be able to refine their search results quickly and we want to easily be able to manage their search experiences. Search facets can be defined and maintained by the marketer. They can be set at the item or template-levels through nondeveloper interfaces. These facets appear in the backend and optionally appear in the frontend search's. A single facets can span many different content types, forming a aggregated result set. Items counts are displayed along side each facet. Page 10
Boosting Our promotion department needs a way prioritize featured products during a search. Search boosting allows items to be pushed higher in the result set of both the backend and frontend searches. Boosting rules can be created and maintained by business users with the standard rules editor interface. Global, template, and item-levels boosting rules can be defined. A boosting value is applied once a rule condition is satisfied, which can both increase or decrease an items position in the search results Page 11
Tagging I know my customers are using words when searching for our content that are not returning any results. Search tagging lets items be quickly and easily assigned a term that can be used in both free text and querybased searches. Tags are not metadata but more of a semantic field used for shaping search results. Tags can be applied to an entire result set, a template, or a single item. There can be multiple and/or shared tag repositories across sites. Page 12
Dynamic Data Sources The list of services on the home page frequently change and manually choosing them takes too much time. Components that list 1 or more items can have assigned criteria that determines their results. Business users are able to set queries using a simple search interface. Personalization can be used to enable multiple queries for each component. Example: All people that been looking at summer clothes, now sees a list of summer sale items on the home page. Page 13
New Developer Stuff The development and configuration time of our new system needs to be significantly shorter, our ROI needs to start in the same year as the software purchase Hibernate Ultimately allows developers to write C# classes and properties that are strongly typed and map to Sitecore items and fields. Currently works with the new search and will eventually fall into the category of object relational mapping (ORM) software. Caution: not a strict implementation of hibernate but hibernate-like. New search APIs Give Sitecore a competitive advantage in the long run Provides the ability to integrate faster and with more search vendors. Other vendors who also support LINQ Most of the C# open source competitors support LINQ at some level, and so has Sitecore in the past. Most apps just use LINQ to SQL or XML and say they support it. Sitecore is actually implementing the LINQ API instead of just using it with existing implementations. Page 14
Additional Questions? Please contact your local partner manager. Page 15