We want to combine the search/ and articles/ endpoints and forms so that the user experience is seamless and they only have one set of order by, relevance, etc.
We are thinking of:
making full-text search a facet in the class-based view
preserving enough of the current functionality (namely the view) to support people who have built something on top of it
Some sorting options are dependent on context: Relevance is only available on search and will need to be considered. We discussed making relevance the default option when the user actively navigates to the search page (clicks on search button or interacts with a search bar)
It has been noted that a few views are not currently using the Article list CBV pattern.
I've added this so we can discuss it in triage.