Chatbot: question-matching on questions input

[melissasamworth]

Acceptance criteria

CSS (Melissa, Archana)

• Make sure visuals of input match design (including hover state)

Other stuff (Nemo, Buddy)

• As soon as the user starts typing, the most closely matching answer in our database shows above it for user to click
• Functions the same as the current search in that the matches will show right away
  • "No matches" is the same as just not showing the bar above at all
• If the user clicks the bar above, it's the same as clicking one of the buttons (search loads right away)
• This functionality is on every page, even if we're already in a convo with the bot

Links https://www.figma.com/file/qqfeYAh6Z7QdyJXsQjIUfh/Stampy?type=design&node-id=1156%3A19240&mode=design&t=dg1esxPyfTqHQMnF-1

[melissasamworth]

@mruwnik right now when I click on the question that shows above nothing happens!

[melissasamworth]

@varchanaiyer do you have any interest in taking the visuals for this one? The text in the little thing that shows above with a question should be bigger (.default I think) to match the input text size. Also ideally a hover state, the bg becomes super light teal (remember to use vars and reference the pre-existing type classes!)

[melissasamworth]

Update: visuals should be good to go, pr of mine pending

@mruwnik there seems to be a significant lag in some places, e.g. type in "What is AI Safety" and it takes a few seconds to show up when otherwise the answers show instantly

[melissasamworth]

Going through again.

This is not a huge deal so if it takes a long time don't do it.

But the logic for choosing a question seems not right. For instance

"What is" produces

But "What is " with a space produces

"What is AI safet" produces nothing but "What is AI safety" shows

Ideally if there is a match to a question e.g. "Do people seriously worry about existential risk from AI?" then every version of this that is less characters e.g. "Do people seriously" will also show something. It wouldn't appear then disappear then show again.

[mruwnik]

the last bit is more complicated, as it changes how search works - I propose creating a separate task for that