Need to create Search block in AEM EDS Universal Editor System | Community
Skip to main content
T
TapasaranjanSa3
July 21, 2025
Solved

Need to create Search block in AEM EDS Universal Editor System

  • July 21, 2025
  • 1 reply
  • 367 views

Hi Their,

 

Good day.

Need to implement a search block for my site which is being built on AEM Edge Delivery Service (universal editor based). Please provide me useful link/videos/page resources explaining about extending the OOTB search block on EDS, how does it function, what are the best practices, how a search API endpoint is established which can be consumer by the search block.

 

 

Thanks,

Tapas 

 

Best answer by SantoshSai

Hi @tapasaranjansa3,

The search block in AEM Edge Delivery Service (EDS) with Universal Editor is powered by a client-side implementation that queries a pre-built search index. To extend or customize the OOTB search block, you'll typically override the default block behavior and connect it to your own search API or index.

I recommend reviewing the following resources to understand how it works, how to extend it, and best practices for creating a search endpoint that integrates well with the EDS ecosystem:

1 reply

SantoshSai
Community Advisor
SantoshSaiCommunity AdvisorAccepted solution
Community Advisor
July 22, 2025

Hi @tapasaranjansa3,

The search block in AEM Edge Delivery Service (EDS) with Universal Editor is powered by a client-side implementation that queries a pre-built search index. To extend or customize the OOTB search block, you'll typically override the default block behavior and connect it to your own search API or index.

I recommend reviewing the following resources to understand how it works, how to extend it, and best practices for creating a search endpoint that integrates well with the EDS ecosystem:

Santosh Sai
    T
    TapasaranjanSa3Author
    August 21, 2025

    Thanks @santoshsai ,

     

    for the response.

    we extended the OOTB search block functionalities, modified the helix-query.yaml for indexing. Updated the component-definition/model/filter json similar to other blocks. In the search.js imported fetchPlaceholders from ffetch library ( import fetchPlaceholders } from /scripts/placeholder.js)

    As you know the helix-query.yaml entries gets transformed to query-index.json dynamically it worked properly we were able to render the matching search results accordingly.

    We added few extra features like highlighting search words inside DOM, displaying search suggestion during the user type entry etc.

    The only design issue which we couldn't figure out is including DAM: assets/pdf in the search result because the original implementation of search block is designed to index only pages not DAM assets.

     

    regards,

    Tapas

    Terms & ConditionsAccessibility statement

    Loading footer...