Summer is winding down and we're back to getting together. Join us at Milwaukee Tool's Headquarters in Brookfield for a night of Sitecore discussion.
5:30 - 6:00 - Food, refreshments, networking
6:00 - 7:00 - Presentation: Automation and Integration Tests in Sitecore
7:00 - 8:00 - Presentation: Beyond Components: Maximizing the Editing Experience for Content Authors
Sitecore and NightwatchJS: Automation and Integration Tests in Sitecore by Hugo Santos, Coveo For Sitecore Developer
It doesn’t matter if you are developing a new website or creating a Sitecore module. We all know how complex Sitecore can be and testing the integration between all the different components of your project can be painful. Especially if you are trying to do this manually. That’s why I decided to take a few minutes to share with you our journey here at Coveo on using NightwatchJS to help us automating those tests.
With over nine years of experience developing desktop and web applications, Hugo joined Coveo in 2016 to help them evolve even more their products. His first contact with Sitecore was in 2014, working as a back-end developer at SapientRazorfish. Since then, he's been always involved in Sitecore projects building websites for a few big companies and more recently working on the Coveo For Sitecore integration package.
Beyond Components: Maximizing the Editing Experience for Content Authors by Brandon Bruno, Lead Technical Consultant, Perficient
The Sitecore Experience Editor is the perfect way for non-technical content authors to manage website content. Once you've built components that utilize datasources and can be personalized in the Experience Editor, what comes next?
As developers, Content Authors are our customers, and it's important to give them the best editing experience possible. After we empathize with a Content Author's frustrations, we will learn about all the governance and configuration necessary to make the most of the content editing experience. After this session, you will be able to identify common pitfalls of a bad editing experience, then streamline them via enhancements in the Content Editor (insert options, branch templates, less is more, etc.) and Experience Editor (datasource location, swappable components, etc.). Expect a discussion that balances the technical and non-technical aspects of designing great components for your authors.