Search Listings feature

[dylankelly]

Overview/Vision

SDP is wanting to create a new content type that allows for the creation of a page containing a specified collection of content and provide a reusable template from which to build collection pages that feature a search / filtering interface. The tool will replace hard coded collection pages pages and any pages containing the ‘Custom Collection’ component that won’t be migrated to Ripple 2. This will provide a huge cost saving for SDP by reducing the time spent on the requests, reduce the delay on creating these pages and allow clients to focus on content creation and citizen experience.

Currently when a client requires a collection of content featuring keyword search and/or filter functionality, the creation/editing of pages requires a developer to create the page on their behalf as either a custom coded page or a page with custom content collection component that utilises the json blob to be built.
The SDP delivery team is devoting significant resources to construct these pages for clients, which leads to excessive time spent on repetitive tasks and delays the delivery of higher value projects.

Proposal

• Create a new content type "Search Listing" in Tide
• Add fields that allow entering JSON configuration of search data
• Create a Ripple framework module which implements the content type and uses the JSON configuration data to configure
  • the search fields to query on
  • the filters to apply that implement business logic (eg scoping to only a single content type or specific field value for instance)
  • The form fields to display in the UI and how to apply them to the search query
  • The component to render each result
  • Optionally, the component to render all results (eg for grid / list / table views)
  • The sort order and custom sort fields to show the user

Proof of Concept

See #613 for a proof of concept implementation