drupal | Kanopi Studios

Algolia is a powerful search and discovery API for creating fast and relevant search experiences. Designed to optimize user interaction, Algolia enables teams to build and refine custom search functionalities. It offers features like instant search, autocomplete, faceted search, and typo tolerance, ensuring users find what they need quickly and accurately.

Why we like (and use) Algolia

There several compelling reasons why we use Algolia here at Kanopi:

Speed & performance. Algolia provides lightning-fast search capabilities, enhancing the user experience on our websites.

Developer’s perspective: Offloading the search functionality to Algolia instead of relying on the main site database significantly speeds up overall site performance. By handling search queries separately, the primary database experiences reduced load and faster response times, leading to a smoother and more efficient user experience.

Relevance. The advanced search algorithms ensure highly relevant search results, improving user satisfaction and engagement.

Query suggestions. Algolia’s query suggestions feature provides users with real-time search suggestions as they type, enhancing the search experience by predicting and displaying relevant queries. Also, developers or editors can easily rank, add and/or remove query suggestions as needed, ensuring the search interface remains intuitive and relevant.

Customization. Algolia’s flexible API allows us to tailor search functionalities to meet specific client needs and preferences.

Developer’s perspective: Being able to easily customize the frontend to meet design and client expectations is a wonderful thing! Algolia’s ease of customization stands out, thanks to its extensive documentation and examples for adding search functionalities to a site.
Algolia covers all popular JavaScript frameworks, such as React, Vue, Angular, as well as iOS, Android, and vanilla JavaScript. This comprehensive support empowers frontend developers to effortlessly integrate and customize search interfaces to meet specific client requirements.

Scalability. As our clients grow, Algolia scales effortlessly, handling increasing volumes of data and traffic without compromising on performance.

Ease of integration. Algolia integrates seamlessly with various platforms and technologies, including Drupal, making it a perfect fit for our technical stack.

How we use Algolia

We use Algolia to enhance the search capabilities on our clients’ websites. Here’s a brief overview of our approach:

Search implementation. We integrate Algolia’s search API into the client’s CMS, customizing the search interface to match the website’s design and user needs.

Developer’s perspective: The Search API Algolia module for Drupal allows us to easily set up content for Algolia to build a search index using a method familiar to anyone who’s ever worked with the Drupal Search API.

However, Developers aren’t limited to this one Drupal module for sending data to Algolia. There are actually many ways to push and pull data to Algolia’s service. Developers can also create custom modules to meet specific client search needs if the Search API module doesn’t meet their requirements. The flexibility with which Algolia ingests data enables developers to curate the data before passing it to Algolia, ensuring a tailored and optimized search experience.

Indexing content. We set up and configure indexing rules to ensure all relevant content is searchable. This includes real-time indexing for dynamic content updates.

Developer’s perspective: When using the Drupal Algolia Search API module, any new, updated, or deleted content is immediately pushed to Algolia and can be searched almost instantly. This seamless integration makes indexing both new and existing content easy and efficient.

Search optimization. We fine-tune Algolia’s search settings to prioritize the most relevant results and ensure a seamless user experience.

Analytics and refinement. Using Algolia’s built-in analytics, we can continuously monitor search performance and user behavior, making data-driven adjustments to enhance search accuracy and effectiveness.

Using one of our clients — the Exploratorium — as an example, here are images showing examples of Exploratorium’s Algolia Analytics metrics:

Several charts demonstrating Algolia's analytics interface

Examples of Algolia in action with Exploratorium

Renowned San Francisco public learning laboratory the Exploratorium needed to revamp their search experience. We used Algolia to create an intuitive, responsive search interface that caters to diverse visitor needs. The improved search functionality has significantly boosted user engagement, search relevancy, and satisfaction. (See the full case study for Exploratorium here.)

Specifically, we used Algolia’s Autocomplete and InstantSearch.js UI libraries:

Example of Algolia Autocomplete library

We integrated the Autocomplete library into the header, providing users with real-time suggestions as they type into the input field. This autocomplete feature predicts and displays full terms or results, forming the core of the autocomplete experience.

An example of Algolia's autocomplete library using the back-end of the Exploratorium website while searching for the term "eclipse"

Example of Algolia InstantSearch.js

InstantSearch.js provides faceted search results.

A screengrab of the back-end of the Exploratorium website showing the InstantSearch interface

Let’s say your organization needs a new website. You meet with your team to discuss the best way forward. Some are touting the benefits of an open-source content management system (CMS) like Drupal or WordPress. Meanwhile, others argue that a proprietary system is the right way to go. But you’re the one who has to make the final call. So, which one will it be? In this post, we’ll look at open source vs. proprietary CMS and what each one has to offer.

If you know anything about us, you already know that we strongly prefer open source for a long list of reasons. We’ll get into those reasons below, but we’ll also give proprietary systems a fair shake — promise. Hopefully, the more you know about each option, it will be clear why we’ve built our organization around open source right from day one.

What is a proprietary CMS?

A proprietary CMS is a software platform owned and controlled by a company. Its users need to purchase licenses or subscriptions for access and updates. It typically offers limited customization compared to open-source CMS, with restricted access to the source code.

Organizations that choose the proprietary route usually cite a few main reasons:

Dedicated Support: Proprietary CMS platforms typically have dedicated customer support, offering immediate help with technical issues, bugs, and updates.
(Perceived) Security: With a closed-source environment, clients sometimes have the perception that proprietary CMS platforms have fewer vulnerabilities, since the code is not accessible to the public. The vendor manages security updates and patches. (Below, I’ll get into why this is more about perception than reality.)
Tailored Solutions: Proprietary CMS vendors may offer customized solutions, features, or integrations to meet specific business needs within a particular industry.
Legacy: In many cases, the client is already deeply invested in other proprietary platforms/software from a provider (their suite of office applications for example), so they’ll also use their CMS for the sake of convenience and continuity. There’s a pretty large company whose name starts with ‘M’ that relies heavily on this in their sales pitch.

These benefits, however, often come with trade-offs, such as higher costs and limited flexibility compared to open-source CMS options.

So, what about open source?

Open-source CMS platforms like WordPress, Joomla, and Drupal account for a majority of websites on the internet. WordPress alone powers approximately 62.7% of all sites. They’re also usually more cost-effective to maintain in the long run compared to proprietary CMS platforms for a number of reasons:

For Starters, They’re Free: Open-source platforms like WordPress and Drupal are free to use, eliminating the need for expensive licensing fees associated with proprietary software.
No Vendor Lock-In: With a proprietary CMS, the vendor retains ownership of the code, limiting your control and flexibility. With an open-source CMS, clients own and control the code, meaning full customization and portability is yours. Using open-source software also means you’re not dependent on a single company for updates, support, or hosting.
Flexibility and Customization: Drupal and WordPress offer extensive customization options with thousands of themes, plugins, and modules; users can tailor their websites to meet their needs without being locked into vendor restrictions.
Community Support: Open-source platforms have large, active communities of developers and users who contribute to forums, create plugins/modules, and more. This collective knowledge base can provide faster solutions and innovations.
Continuous Improvement: Open-source platforms are regularly updated with security patches, new features, and enhancements contributed by the community, making them more dynamic than proprietary software, which might have slower release cycles.
Ownership and Control Is All Yours: With open-source software, you have full ownership and control over your website, including the ability to host it anywhere and modify the underlying code. Proprietary systems may impose hosting restrictions and limit access to the source code.
Security and Transparency: Open-source platforms are generally considered to be more secure because the code is publicly available for scrutiny, allowing security experts to identify and patch vulnerabilities quickly. Proprietary systems may be more opaque, making it harder to spot and fix security issues. So while it’s true that many more people have access to open-source code, this results in greater platform security — despite what many proprietary system providers (and their sales teams) would like you to believe.
Scalability: Open-source platforms like Drupal are highly scalable, making them suitable for both small websites and large enterprise-level applications, whereas proprietary solutions may have limitations or require expensive upgrades to scale effectively.
Integration Capabilities: Drupal and WordPress are known for their ability to integrate with a wide range of third-party tools, APIs, and systems, providing more flexibility in building feature-rich websites — while proprietary platforms may restrict integrations or charge extra for them.
Innovation: Open-source platforms often lead in innovation, as developers from all over the world can contribute new ideas and functionalities, fostering a continuous flow of creativity and technical advancement.

It’s your call.

So, returning to our opening paragraph scenario, it’s your call; you have proponents in your organization on each side of the coin. Which do you choose? Do you listen to those team members clamoring for a proprietary CMS and its benefits? Or do you choose the flexibility and efficiency of an open-source platform?

Not that we would openly encourage you to choose one over the other. Good heavens, no! However, if you should decide to go with an open-source CMS — specifically Drupal or WordPress — we have a little motto here at Kanopi:

Never build alone.

Since 2010, we’ve been building websites that meet our clients’ unique needs, whether designing and developing from the ground up or enhancing existing sites with upgrades and CMS migrations. Our approach combines UX research, discovery, and visual design to create a user-friendly digital experience, followed by expert development to bring your vision to life. Even after launch, we provide ongoing support to ensure your site continues to perform at its best. With us as your partner, even the staunchest proprietary fans will be tipping their hats to you.

Have a look at some of our favorite Drupal and WordPress projects.

Tag: drupal

Algolia for Search