© 2017 Coveo Solutions Inc -Proprietary and Confidentialimpact.coveo.com/wp-content/uploads/2015/12/Coveo-Impact-2017... · 2 © 2017 Coveo Solutions Inc -Proprietary and Confidential

1 © 2017 Coveo Solutions Inc - Proprietary and Confidential

4.1 Overview

Simon Langevin

Product Manager | Sitecore MVP 2017

2 ©2017CoveoSolutionsInc- ProprietaryandConfidential

Coveo for Sitecore

The content presented at Coveo Impact may contain statements related to future businessdecisions and technology developments. Any forward looking statements made are based oncurrent expectations and certain assumptions which may be subject to change. Please consultwith your Coveo relationship manager if you have any questions.


Forward Looking Statements

4

▶︎ Why 4.1?

▶︎ Creation Process and Overview of the Components

▶︎ Demo

▶︎ Summary

©2017CoveoSolutionsInc- ProprietaryandConfidential

Agenda


Why 4.1?

Almost 3 years has passed since the release of Coveo for Sitecore.

The Sitecore community has provided us with a lot of feedback.


You are the reason

The components are too large and often require to all be present together to work.

The JavaScript resources are too heavy on the page.

Caching is not possible.

The component do not fit well with new design framework such as SXA.


Comments from the Community

Too Large Too Heavy Too Complex

The Results

Several clients built their own UI, which resulted in:

▶︎ Lack of basic Coveo functionalities

▶︎ No tracking of page events

▶︎ Incompatibility with Machine Learning

▶︎ Increased maintenance complexity



Creation Process and Overview

Guiding Principles

▶︎ Smaller re-usable components

▶︎ Giving the power to build a solution piece by piece

▶︎ Focus on data sources for content management

▶︎ Fast and performant

▶︎ Make every component cacheable out of the box

▶︎ Lighter and Powerful

▶︎ Reduce the amount of resources required on page load

▶︎ Keep the existing features intact



Working In-Line with the Newest and Greatest

Coveo for Sitecore 4.1



DemoAvideowillbemadeavailableattheendofJuly2017

4.1 Additional Details

▶︎ Lazy loading of JavaScript/CSS resources

▶︎ Support of Client Side rules

▶︎ MVC Only

▶︎ Legacy Components will still be supported

Beta Release planned for the end of July 2017

▶︎ Accessible to Coveo for Sitecore Certified Developers


The separation of components will give you the opportunity to do customizations at a smaller scale

Lazy-Loading of JavaScript and CSS resources will reduce the weight of the components

Selection of data sources when creating the component will facilitate Developer to Authors collaboration


In Summary

Smaller Lighter Easier


Next Step

Developer

North AmericaSan Francisco, USAAugust 28 (TBD) 2017

EMEALondon, UKSeptember 18 2017

www.coveo.com/en/support/trainingGet Certified!

Resources


Coveo for Sitecore Microsite | www.coveo.com/sitecoreMarketing material, download, pricing, features, …

Developers Portal | developers.coveo.com/display/SitecoreProduct Documentation, Best Practices, How to, …

Q&A Portal | answers.coveo.comDevelopment & configuration question Stack Overflow style

Clients’ Community and Support Portal | support.coveo.comReport any product issue to get support

Technical Blog | sources.coveo.comBlog from our R&D team, how do we build our product

Sitecore Stack Exchange


Sitecore Slack



Questions?

A Framework for Self-Service Success with Unified, AI-Powered Search

Ken Thomas & Drew Claybrook, Extreme Networks | Olympic Room

Getting the Most from Coveo Machine Learning

Richard Tessier, Coveo | Civic Room

The Coveo Lab: Discover Interesting & Innovative Use Cases

Gauthier Robe, Coveo | Concordia Room

UP NEXT | 11:15 – 12:00


Simon LangevinProduct Manager | Sitecore MVP 2017

[email protected]

https://www.linkedin.com/in/simonlouellet/

@SilaouO


Thank you

Documents

© 2017 Coveo Solutions Inc -Proprietary and Confidentialimpact.coveo.com/wp-content/uploads/2015/12/Coveo-Impact-2017... · 2 © 2017 Coveo Solutions Inc -Proprietary and Confidential