[Search] Create search result component

[kweku5]

Feature Request

As an AEM Author, I want a search results page that displays page results from a search term entered in the search field, so I can provide search a results page as a core component.

Details:

Search Results page contains:

• Search
• Field
• Results of search term
  • Page Title
  • Page Description (Metadata Property)
  • Date Published
  • Tags
• Facets
  • Configurable tags (Author has the ability to add existing tags and they are displayed as facets on the page)
  • Facets will display tag terms and be represented by link and number of results associated with term
  • If user selects the link it becomes bold and results are filtered with content associated with selected term
  • Facets will only display if resulting matches exist
  • Facets should be optional (display / do not display)
• Pagination
  • Results total represented by a displayed total number
  • forward link to move to the next page (does not display on the last page
  • back link to move to the previous page (does not display on the first page)
• Configurable default result number (Author has the ability to enter a number in the component to display the default total results)
• Sort by:
  • Relevance
  • A-Z
  • Z-A
  • Newest to Oldest
  • Oldest to Newest

1. The component should call an endpoint and pass it a keyword then generate a JSON result that includes:

• Result items
• Title
• Tags
• Description
• Publish Date
• Author
• Total Results (to generate the total pages with 10/20 per page)

2. facets

• Category Tags
• Total (items matching tags)

Acceptance Criteria:

1. Author is able to add search component to a page
2. Author is able to configure:

• Facets
  • Include categories yes/no (default no)
  • If yes: - option opens to navigate to Tag group - select a tag root
  • Selected tag root will be displayed as Category label
  • All content with category tag will be displayed

3. Default total for page results 10/20/40 (or enter a #)
4. User is able to see results displayed matching criteria
5. User is able to select Category filter and results re-load with matching filter
6. User is able to turn off facets/categories

[JasonUSC]

Regarding search facets, I would want a bit more flexibility:

1. The "root" of a facet could be any level in the taxonomy, not just the top-level namespace
2. The category name displayed on the page can default to the tag label but should also be customizable
3. Need the ability to have multiple facet categories on the page
4. Showing the number of matches for a tag should be optional

[vladbailescu]

Initial proposal at https://github.com/adobe/aem-core-wcm-components/pull/653, still being worked on.

[aahlawat]

Few updates to above RTC:-

1. Instead of pagination 1 2 3.. we will be having load more button.
2. Sort options will be titile, last modified date and relevence

[abhishekagg19]

As per earlier discussion, the following requirement was mentioned: Search path - Auto-detecting the current page language and use it to derive the search path for executing the search query.

Is it required for this first release of the search component?

[JasonUSC]

Hopefully this component gets traction soon, it's one of those basic building blocks for websites that would be great to leverage out of the box.

[tamelang]

Is this one going to happen?