Listening session with Steven

Notes from listening session with Steven, DrupalCon Prague 2022:

• read the status message first thing
• asked "is this Search API?"
• Wanted to install straightaway from the button; seeing a modal with instructions was discouraging
• Wondered where links on the project detail page would go (noted drupal.org). ed. note: will these open in a new tab by default?
• Was looking for a _category_ called "paragraphs" to try to find things in that ecosystem.
• once he clicked a category, he saw he had 0 results. figured out quickly that it was because he still had a keyword search on. he erased it.
• wondered why there was a CCK category at all, given that this was Drupal 9. (ed. note: explained that a module tagged with that may still have a D9 release, because it was tagged with it back at its Drupal 6 version)
• poking around, went in and enabled a second source plugin! had a hard time getting back to where that was. (ed. note: but then had no idea how to use that or what it did. I pointed out that it went to a tab at the top of project browser. then was interested in how they differed)
• user noted that it was good that "install" opened in a new tab; noticed that right away
• the project browser encouraged him to explore and find modules and try them out (jquery_fireworks)
• Sources Tabs: he didn't think he could click them, which is why he initially didn't find it, because the cursor doesn't change to a pointer
• User intuited what the shield icon meant
• User stated that the one thing that really felt like it was missing was the five-star rating system.
• Was missing the "active installs" info on the card view. Suggested it to go on card view with a shorter version "(i) 43" with a tooltip explaining full meaning
• User stated they were very happy that the back button just behaved exactly as they expected
• User said current way to find a specific module is to google "drupal [modulename]"
• User noted that if I'm using this to experiment and play, I don't like that "uninstall" doesn't remove the module from my codebase. Would be good to have additional instructions around removing it. Didn't want to leave a mess behind. Since [install] button links you right to how to enable it, might it be better to do another modal there, with instructions for removal or the link direct to enable it... since you might want to do either of those two things from that state.
• Noted that the install link did not work for jquery_fireworks module, because it links to #module-jquery_fireworks, though the actual id needed is #module-jquery-fireworks (underscore should be replaced with hyphen)
• User stated they wanted a (x) icon to clear their keyword filter with one click, instead of having to backspace it all.