Tiberiu Ichim

@JeffersonBledsoe unless we have some way of stashing the search block configuration on the backend, there's no way of having non-content routes "content aware". In principle we would need an...

@JeffersonBledsoe I'm fine with this, but there will be some work ahead for the brave soul that works on this, I'm thinking especially at the multilanguage integration, as the search...

@djay Yes... but as the Search is a block and the rest of the page is basically editable, it will introduce the need for an extra settings (once this is...

@djay On multilingual websites the search page is exposed as /en/search, /de/search, etc, see https://github.com/plone/volto/blob/7044eca789d836786e9e789036669085cc22bee7/src/routes.js#L59-L62 The bug is that the search widget hardcodes the action as `/search`. That bug has...

@djay How would the following work? - As a multilingual website editor, - I want to edit the /search page, - so that I can add additional text or multilingual...

@djay The problem is that on multilingual websites, a translated content sits in a Language Root Folder (/en, /nl, /de, etc). So, if I translate /en/my-page to Dutch, it's going...

@djay no, but that would be a good idea.

@ionlizarazu I think we should strive to do better here, Volto aims to provide server-side rendered "default views". We're moving way too much into SPA teritory here.

@stevepiercy that's because it's broken syntax. In react the kebab-case becomes camelCase, so it should be ariaLabel="Cancel"

@sneridagh ok, so it's not broken syntax, just the lexer being unaware of things. Ok, TIL