In our last post about Randomizing Results from a Coveo Index, we talked about how we managed to create a search page that returns random results from our index. Following this, we wanted to have a full-fledged custom component for the sake of doing things cleanly (we love “clean” at Coveo).
This post will go in-depth about our journey to “Component-ize” our randomizer using TypeScript.
I’ve been working with the Salesforce platform at Coveo for about 3 years. In those 3 years, I always had the feeling that there was something missing in our continuous integration setup. A couple of years ago, we’ve automated the process of creating a managed package using PhantomJS. As a software developer, this is a well-deserved upgrade.
Since then, we were able to gain a lot of speed in our release process. But still, there was something missing. There was a void in my developer life. Demoing, reviewing, and testing new features on our package was near impossible and needed a lot of effort. Since Salesforce organizations can’t be created easily, a developer had to create a new org, push all the code to that org from their machine, give credentials to everyone, etc. A lot of works on my machine(TM) and Jenkins is weird happened using that method.
Continuous integration (CI) is the act of automatically compiling code and running its tests every time a change is made. It is an important step in a project to ensure quality and save time. It needs to be implemented before continuously deploying an application.
In this post, I will explore how to configure CI with AppVeyor using the Sitecore Habitat demo project.
Companies are becoming more and more aware of the importance of offering a good search experience on their website. From increases in purchases on ecommerce websites to getting fewer cases on their support and community websites, companies are realizing that helping users find what they are looking for faster and more easily results in a great overall experience.
In the previous blog post, I explained why having a prominent search box is essential. In the second part of this series, I will talk about the key elements to have in your search result page.
In my last post, I shared some of the wisdom I gathered over the 4 years I’ve worked with AWS Redshift. Since I’m not one for long blog posts, I decided to keep some for a second post. Here goes!
Organizations are becoming more and more aware of the importance of offering a good search experience on their website. From an increase in purchases on ecommerce websites to getting fewer cases on their support and community websites, companies are realizing that helping users find what they want faster and more easily results in a greater overall user experience.
In this series of blog posts, I will explain why having a good search experience is vital for any website. This blog post will tell you about the importance of the search box.
Over the last 4 years, I have been part of the team that builds the Usage Analytics solution here at Coveo. This solution is based on AWS Redshift, a petabyte scale columnar store. We were early adopters of this data warehousing solution and while it is an awesome product today, I probably don’t need to tell you that we hit some bumps along the way. Here are some of the tips, tricks, and overall best practices we gathered during those years.
Recently, I had to work on an interesting use case where my client wanted to display teasers of premium content to anonymous users in Sitecore. Once the users found what they were looking for, they were either redirected to a login page or to a subscribing page. No secrets, the strategy behind it is to increase conversion rates.
After working on the project, I realized that the business needs behind their request was fairly common. People want to show partial items to anonymous users, but still want them to be relevant and easy to find. Let me introduce you the