Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Search results template #146

Open
sukhrajghuman opened this issue Jul 10, 2019 · 5 comments
Open

Search results template #146

sukhrajghuman opened this issue Jul 10, 2019 · 5 comments
Labels
enhancement New feature or request.

Comments

@sukhrajghuman
Copy link
Contributor

sukhrajghuman commented Jul 10, 2019

Search/results pages are common in government websites. Would be good if we could create a template that focuses good UX

@gordongrace gordongrace added the enhancement New feature or request. label Jul 24, 2019
@KiriHoy KiriHoy self-assigned this Aug 7, 2019
@gordongrace
Copy link
Contributor

@gordongrace
Copy link
Contributor

gordongrace commented Aug 16, 2019

Deployed with Netlify at:
https://govau-design-system-search-results-template.netlify.com/search-results/

Interesting points for further discussion / refinement:

  • Use of role="status" for search result count display (first time we've used this). Displaying at both top and bottom of search results
  • Additional skip link to bypass search filters / refinements and go directly to result Fixing issues with Windows (browsersync, onchange) and updating documentation #1
  • Use of ol for search results, with expectation that start value will be changed programatically
  • Prevent search engines from indexing and following search result pages
  • Multiple search result types (with tags, with date, with metadata, with image)
  • Conditional display of 'No results' (or similar) page alert.

New styles required:

  • mark
  • Whitespace modifications to override headings/paragraphs in search results
  • Inline dl display for per-result metadata
  • Muted display of per-result dates

Pending progress from other components

  • Improved search result pagination
  • Improved search input form in header
  • Per-result metadata marked up using dl
  • Improved search input with autosuggest / autocomplete

Potential bugs discovered:

  • Focus state on targets for additional skip links persists
  • Mis-aligned focus states for radio/checkbox inputs
  • select input chevron display
  • Excessive padding on form

Other items for discussion:

  • Back to top links?
  • Sort != Refine/Filter
  • Click target in mobile view (esp. where results have image)
  • Faceted search variants vs post-search parametric refinement
  • Per result breadcrumbs?
  • Related searches

@gordongrace
Copy link
Contributor

Enhancements in potential future iterations:

  • Highlighted "Best Bet" results
  • Feature box results (for example, searching 'sbr' at ato.gov.au
  • Tab-based scope switching
  • Disabling browser-default autocapitalize, autocomplete, autocorrect, spellcheck behaviours for the input

@sukhrajghuman
Copy link
Contributor Author

For sprint 137.

  • Open a draft PR
  • Encourage feedback from others on this template

@gordongrace
Copy link
Contributor

While we wait for the pagination component to come online, I'd propose an initial iteration of this template that uses direction links for Prev/Next functionality.

@KiriHoy KiriHoy removed their assignment Apr 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request.
Projects
None yet
Development

No branches or pull requests

3 participants