This makes the search string to go again quite far from the page results main body (although it's close to facets!) and makes the page feeing a bit too wide. Imagine a user changing the searched text on the lhs and then changing sorting options or output formatting options on the rhs. Also, the search hit descriptions are running very wide.
Was there a need to go for such a wide-content-box design during latest update? Isn't 2 preferable to 3?
psaiz
commented
10 months ago
Search for something like "cms" and observe the search results page.
(1) The current production looks like: https://opendata.cern.ch/search?page=1&size=20&q=cms
The problem here was that the search string was "far" from the main page body.
(2) We have addressed the situation during the previous Invenio upgrade sprint in 2021 to bring it closer to the page body, see the master branch at commit 1b8cd2257db89fb6b6f2ed8ab910ed52faa074b1 leading to: http://127.0.0.1:5000/search?q=cms&l=list&order=asc&p=1&s=10&sort=bestmatch
The search string is now closer to the page body.
(3) The latest Invenio upgrade (#3450) makes the page very wide with the search box going "from coast to coast": https://opendata-dev.cern.ch/search?q=cms&l=list&order=asc&p=1&s=10&sort=bestmatch
This makes the search string to go again quite far from the page results main body (although it's close to facets!) and makes the page feeing a bit too wide. Imagine a user changing the searched text on the lhs and then changing sorting options or output formatting options on the rhs. Also, the search hit descriptions are running very wide.
Was there a need to go for such a wide-content-box design during latest update? Isn't 2 preferable to 3?