P02. Search
Release notes
Date | Update | Updated by |
---|---|---|
17 Jan 2022 | Component finalised | @Japneet Kaur (Deactivated) @Steven Mao (Unlicensed) |
Overview
Site search enables users to type keywords and find relevant content and resources on the website.
This tool was identified as high importance given the importance of clients being able to find things more quickly. The search experience caters to three key audiences:
Users who are looking for a specific thing
Users who are searching for a general topic area
Users who do not know what they are searching for
Key user groups:
All user groups are expected to interact with search (how they use it may differ)
User flows:
Users can access search from any website page on the website header.
Business rules
BR-# | Business rule |
---|---|
BR-1
| The search function will be built as a single page application (SPA) |
BR-2 | The labels and content can be configured in the CMS. Any changes to the single page application (SPA) gets updated through Application Programming Interface (APIs). |
BR-3 | The Application Programming Interface (API) request to the search engine will be handled in the front-end if feasible and secure |
BR-4 | The single page application (SPA) will be embedded in the Adobe Experience Manager (AEM) page for the best user experience |
BR-5 | The placeholder text in the search bar will be: "Search Legal Aid NSW".
|
BR-6 | The search is fully responsive |
BR-7 | The search function allows users to search from website databases using free text search |
BR-8 | Users are able to see digital assets (e.g. images, videos, PDF's) as part of the search results |
BR-9 | On the search results page, users can filter search results in two main ways: Relevance
Advanced filters
|
BR-10 | Clients have the option to select a microphone to enable speech to text functionality. |
Design
Description | Desktop | Mobile |
---|---|---|
Screen 1 - User has not selected search (inactive state)Key user goals:
Design behaviour:
Use of icons:
|
|
|
Screen 2 - User conducts a searchKey user goals:
Design behaviour:
|
|
|
Screen 3 - User lands on the search results pageKey user goals:
Design behaviour:
|
Advanced filters:
Sort by:
| |
Screen 3.1 - No search results foundKey user goals:
Design behaviour:
|