Tech Blog Menu

Maps are awesome. A good map implementation reacts to user’s current context and provides relevant information. Since maps are great at visualizing relevance, the Coveo for Sitecore product team decided to experiment with that concept. While exploring the concept, several use cases related to customer requests have emerged. This article will serve as a guide for these specific cases while remaining primarily focused on geospatial research.

Before we start, you can refer to the code here, and have a look at the live map here

On The Menu

• Geospatial Search
• Persistent Queries
• Custom TypeScript Coveo Components
• Push API
• Advanced Relevance Tuning

Storing parameters securely accross multiple environments with employees having different level of access in each of those can be challenging. AWS Systems Manager Parameter Store offers a nice solution to that problem with lots of advantages such as:

• being hosted, highly available, and scalable
• history tracking
• encryption with KMS
• audits in CloudTrail
• notifications with CloudWatch or SNS
• granular security using IAM policies

Every security team’s dream.

When we decided to store our deepest secrets in the Parameter Store, I searched right away for an integration with Spring Boot/Cloud for our Java microservices. I was left empty-handed.

This post is the second part on how we built our Elastic Search demo. You can read the previous post The Elastic Search Demo, Part 1: Build the Index on how we got the content inside our index.

Use case

• Build a demo on top of Coveo for Elasticsearch to show what you can do with the platform.
• Use public content that everybody is familiar with.
• Build it in 2-4 weeks time.

This is the second blog post of a new series entitled “Build it with the Coveo Cloud Platform”. The series will present innovative use cases for the Coveo Platform, always including full code samples. Read the previous post Building a resource locator.

Use case

• Build a demo on top of Coveo for Elasticsearch to show what you can do with the platform.
• Use public content that everybody is familiar with.
• Build it in 2-4 weeks time.

Search is great. It gives you the power to find information without having to go through every page of a website. But sometimes, search alone is not enough, and you need filters and sorting options to help you find what you’re looking for. One fantastic way to narrow large sets of content is faceted navigation. In fact, faceted navigation may be the most significant search innovation of the past decades.

Now that we have created and tested our custom component, we want to integrate it like any other component in the Coveo for Sitecore Hive Framework.

This post offers a step by step approach to adding a custom component in the Coveo for Sitecore integration.

Update: Links to the Blitz registration page were added.

Blitzday

Saturday. 7 AM. Normally I’d be sleeping in. But alas, this Saturday is not like your regular Saturday. I’m wide awake and super hyped. No, this isn’t the first chapter of my new fantasy book, it’s real. It’s Blitzday. I’m ready to crush through code like never before.

Update: Links to the Blitz registration page were added.

A New Competition Appears! And Its Name Is Coveo Blitz

The first time I heard about the Coveo Blitz was through a spam^H^H^H^H email from my school faculty informing me that some company I’d never heard of from Quebec was organizing a coding competition. Having nothing else to do and looking for some way to hone my coding skills, I enlisted my friends to register for the competition as a group. After all, the only requirement they asked for registration was to be able to send an email (something I, and others apparently, still fail to properly do even today).

Now that we have created a custom component, we want to test its interactions with the Coveo JavaScript Search Framework.

This post offers a deep dive into the Custom Coveo JavaScript component testing world.

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.