`/search` page isn't customisable through-the-web

Is your feature request related to a problem? Please describe. The current ‘CMS’ search page (/search) is a custom component. This means that the only way to customise its look or functionality is to shadow the component and implement it themselves. We already have a Search block which mirrors the existing functionality of this, but offers all the through-the-web customisability options of the block editor. This could either be fixed to having just a search block on the page, or a full ‘block’ editor to allow site admins more customisation of the search page.

Describe the solution you’d like Make /search a block form that contains a Search block out-the-box.

[tiberiuichim]

@JeffersonBledsoe In one of my websites I did this (not sure it’s enough):

  config.settings.nonContentRoutes = [
    ...config.settings.nonContentRoutes.filter((p) => p !== '/search'),
    ];

and I’ve created a /search page with a search block;

[erral]

And what about delegating this configuration to plone.volto? We can add a preconfigured search page with a search block when installing plone.volto.