Searchbox regressions

[g-francesca]

URL:

https://nodejs.org/en

Browser Name:

Chrome

Browser Version:

142.0.7444.176

Operating System:

MacOS Ventura 13.0

How to reproduce the issue:

While navigating the website and using the searchbox, I noticed a few regressions compared with the initial version of the searchbox. I'm reporting here all of them.

Prompt Suggestions
Clicking the prompt suggestions, nothing happens. They should open the chat sliding panel.

Mobile UI
There is no longer a dedicated mobile UI, so the same layout is now used for both desktop and mobile. Is this intentional? The original design included a full-screen modal specifically for mobile.

As is:

Expected:

Chat suggested prompts style
The style of the suggested prompts in the chat panel appears different from the previous version. Is this expected?

As is:

Expected:

[avivkeller]

There is no longer a dedicated mobile UI, so the same layout is now used for both desktop and mobile. Is this intentional? The original design included a full-screen modal specifically for mobile.

This is intentional, fwiw. The current UI works on mobile, so there's no need to maintain a separate mobile UI. Maintaining a mobile UI proved to be quite difficult when I was moving components to @node-core/ui-components to prep for more adoption of the new components.

[ovflowd]

@avivkeller was it shared that this would be intentional? I agree with the user, @g-francesca, this is definitely a subpar UI for mobile. And I think this will be even more relevant for our API docs where search is going to be used much much more.

Wdyt, do you think we could bring some mobile improvements here?

[ovflowd]

To be clear, just trying to better understand the complexity here 👀 and if we did this intentionally to have a first MVP, or initial complexity ... or? 🤔

[avivkeller]

The mobile UI Orama provided was fairly complex to move to ui-components, from what I could tell, since they provided unique mobile-only components with complex interactions. However, I can work on making part of it in ui-components (so it's shared with the docs)