Closed Bug 737484 Opened 12 years ago Closed 9 years ago

[Tracker] Implement tailored search result pages on Phonebook

Categories

(Participation Infrastructure :: Phonebook, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bram, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [UX][Re-Design][Triage 2015-04-17])

Attachments

(19 obsolete files)

Attached image 2 Logged In (obsolete) —
After a user log in, she will be presented with the most common groups, as well as a list of general stewards to contact.

The purpose is encourage browsing, which will allow us to deliver more accurate results, rather than searching blindly.
Attached image 3a Search “webdev” (obsolete) —
When user search for common terms for group, change the search query to the actual group name that people uses. When people search for websites, we should display the result for the group “WebDev”.

Note that group information, steward to contact and search keyword suggestions (“What members have in common”) are presented so that the user can act and browse in a more coordinated way.
Attachment #607599 - Attachment description: 3 Search “webdev” → 3a Search “webdev”
Attached image 3b Search “Language” (obsolete) —
When user search for common terms for group, change the search query to the actual group name that people uses.

Search queries for language should lead to translation and localization-related subjects. It should also display language tags that have the most usage (number of people, number of users).
Attached image 3c Search “Firefox” (obsolete) —
When user search for “firefox”, we know that it can mean many things, so let’s direct users to Firefox products (‘firefox mobile’), or people that are directly responsible for engineering/design/release (‘fx-team’).

Let’s also direct users to departments, or areas, that works on Firefox. Add-ons, for example.

The areas ont the sidebar is not final. They’re there to show possibilities.
Attached image 3d Search 404 (obsolete) —
Search keywords should always display helpful information, even if they lead to an empty search result page.

In 404 pages, have a list of the top groups so user can start browsing. This page mirrors the phonebook start page.
Overall, this looks great and is going towards the right direction. Here's my feedback!

2. Logged In
* What would "browse groups" look like?
* How should stewards be chosen to be shown? Automatic or manual (e.g. alphabetically)?


3a. "webdev"
* This could result in a lot of page loads if we don't have a suggestions box. Basically, users will be finding a group page (which is what I believe is shown here) when they may or may not have committed to "WebDev". 
** How about having a UI for the search field, like Quora or Facebook, that show a suggestion of what they may have meant. This will let the user choose and remove any tricky areas where a results shows up when it shouldn't have.
* I like the idea of going straight to the group page as a search result.

3b. "language"
* What you're suggesting is someone finding a system level group where there is a hierarchy attached to it. For example, if someone searches for "engineering" or any other group that is attached to our org structure, they'll find the related groups to that system group.
* I like this as another group page, but specifically for system level groups. 
* How would the "did you mean" bubbles show up and become prioritized?

3c. "firefox"
* Looks like another opportunity for a system level group. Look at the feedback for 

3d. Search 404
* Looks good, but I'd worry about making the popular groups section look a bit more organized. Even though its balsamic, it probably should be easier to understand
* How about offering a way for a user to invite the person they couldn't find in the phonebook?


Other Mockups Likely Needed:
* A regular search without these suggestions mockup. I know its obvious to both you and I, but it likely isn't for devs. 
* Suggestions area while typing synonyms, similar words and mistypings
Whiteboard: [UX][Re-Design]
Depends on: 706626
(In reply to Aakash Desai [:aakashd] from comment #6)
> 2. Logged In
> * What would "browse groups" look like?

I was originally thinking of deploying some sort of a tag cloud interface (ie. ordering groups by occurrence and usage), but this is not a helpful way to browse, so I am nicking it off the page, at least until I think of a better way to navigate. For now, top 10–20 groups should be enough to get a new contributor (or old) started.


> * How should stewards be chosen to be shown? Automatic or manual (e.g.
> alphabetically)?

Given that this page appears after the user has been vouched, perhaps adding general-level stewards would be redundant? An email to general stewards would have been dispatched the moment a new user joins.

Perhaps replacing this, we should give a list of good first bug?

It would be more helpful if the bugs are categorized, but I don’t know how to delineate. I can immediately think of “HTML/CSS/JS”, “Python”, “Visual Design”, “UX”, “Content and Copywriting”, “Firefox Platform”. I wonder how many is helpful?

I wonder if this categorization is not helpful at all, and if we can just list the bugs? A search for “goodfirstbug” and “good-first-bug” produces a total of 13. See attached for a mockup with bugs included and stewards removed.


> 3a. "webdev"
> * This could result in a lot of page loads if we don't have a suggestions
> box. Basically, users will be finding a group page (which is what I believe
> is shown here) when they may or may not have committed to "WebDev".

Actually, while “WebDev” looked like a group page, in reality it is a search result page that has been beefed up with an infobox. Think of DuckDuckGo’s “Meanings of x” that appear when you search for certain keywords: https://duckduckgo.com/?q=Firefox

All top groups and search terms should have their own infoboxed search result pages. There don’t need to be many. I am thinking of around 20 total. But we will need to create the ability for search result page to be manually tailored, and create templates and contents around it.

The good news is, we will not need to create group pages. Just normal search result pages, and ones with infobox on top. Plus, by making search pages more relevant for certain keywords, we also won’t need a way to order system-level groups hierarchically.


> ** How about having a UI for the search field, like Quora or Facebook, that
> show a suggestion of what they may have meant. This will let the user choose
> and remove any tricky areas where a results shows up when it shouldn't have.
> * I like the idea of going straight to the group page as a search result.
>
> * How would the "did you mean" bubbles show up and become prioritized?

You are correct. Initially, I was thinking of auto-correcting the user’s search term, so “firfox” automatically counts as “firefox” in the search engine.

Now I am thinking that “wrong” keywords should return search suggestion (“did you mean”). These suggestions will only appear when the search term entered was not “correct”. If it’s correct, then we will either display results normally, or for certain keywords, display results with an added infobox up top.

 
> 3d. Search 404
> * Looks good, but I'd worry about making the popular groups section look a
> bit more organized. Even though its balsamic, it probably should be easier
> to understand

I agree. If you see my comment up top about dividing good first bugs under areas, maybe popular groups should also be divided along areas?

A good place to start would be to
1. Get a list of groups (we have this) along with numbers of Mozillians who have it (we don’t have this)
2. Sort this list to find the top, say, 100 most used groups
3. Make categories that will fit this top 100
4. Implement the category to make “Popular Groups” more organized, and even browsable


> * How about offering a way for a user to invite the person they couldn't
> find in the phonebook?

Good idea. I have revised the 404 page mockup to address this particular problem.


> Other Mockups Likely Needed:
> * A regular search without these suggestions mockup. I know its obvious to
> both you and I, but it likely isn't for devs. 

I have added a mockup called “4. search results” to get a regular search without suggestion.


> * Suggestions area while typing synonyms, similar words and mistypings

I have added a mockup called “3e. search suggestion” to get a search with “did you mean x?”
Attached image 2 Logged In + Good First Bugs (obsolete) —
A variant of the logged in page with the addition of good first bugs.
Attached image 3a Search “webdev” (obsolete) —
* Added “Search results: xyz” on top of search results
* Highlighted all occurrence of keyword
Attachment #607599 - Attachment is obsolete: true
Attached image 3c Search “Firefox” (obsolete) —
* Added “Search results: xyz” on top of search results
* Highlighted all occurrence of keyword
Attachment #607602 - Attachment is obsolete: true
Attached image 3d Search 404 (obsolete) —
* Added invite section
* Modified the wording to “search popular groups”
* Removed “contact these stewards”
Attachment #607603 - Attachment is obsolete: true
Attached image 3e Search Suggestion (obsolete) —
When we have a synonym for a search keyword (for example: “firfox” > “firefox”, “modzila” > “mozilla”), we should display a “Did you mean xyz?” on top of the search result page, so user can easily correct mistake.
Attached image 4 Search Results (obsolete) —
This is a vanilla search result page with no infobox up top and no search suggestion.
Blocks: 699812
Attachment #609244 - Attachment description: 3 Search “webdev” → 3a Search “webdev”
Attached image Search box autocomplete (obsolete) —
Note how partial matches are highlighted, and meta-categories like group and location are given not only descriptions, but also a visual indicator.
Depends on: 741840
Blocks: 699598
Blocks: 694660
Blocks: 700479
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Version: unspecified → other
Attached image 2 Logged In (obsolete) —
* Removed the “browse” link from the popular groups list
* The stewards list now has contact details, as it should be
Attachment #607597 - Attachment is obsolete: true
Attached image 3a Search “webdev” (obsolete) —
Removed the “contact” field and replace it with people’s email addresses and IRC nick
Attachment #609244 - Attachment is obsolete: true
Attached image 3b Search “Language” (obsolete) —
Updated the display of search results to fit with the rest of the mockups. List of names should also contain avatar, email, IRC and groups. The previous version only displayed name and avatar
Attachment #607600 - Attachment is obsolete: true
Attached image 3c Search “Firefox” (obsolete) —
Fixed the display of search results. Clarified what’s actually done during search.

The behavior:
When a search keyword produces duplicate related groups, first we would display all the related groups up there, and then we would do a normal keyword search below.
Attachment #609245 - Attachment is obsolete: true
Attached image 4 Search Results (obsolete) —
This is a normal, plain old search result page.

This page will show up when no synonym can be found. 

We would only autocomplete name, location and group, so if no keyword can be mapped to any of these fields, this is what would happen.
Attachment #609248 - Attachment is obsolete: true
Attached image 3e Search “foxfire” (obsolete) —
The behavior:
When a search keyword is typed the wrong way, treat it as if the search was done for the right keyword. Look at the synonym list for common mistypes.
Attachment #609247 - Attachment is obsolete: true
Attached image 3g Search “contribute” (obsolete) —
When user try to search for keywords like “Contribute”, they may mean “How do I get started with helping?”

The search engine should do a search for the “stewards” group and then display the results.

This kind of search is really just a standard group search that is done if the keyword has synonyms.
In this attachment: https://bug737484.bugzilla.mozilla.org/attachment.cgi?id=610454

I feel the user entering text box should be of the same width as the result text box.
Depends on: 765957
This is far too large of a bug. I'm making this into a tracking bug for implementing tailored search results and breaking it up into smaller bugs.
No longer depends on: 765957
Summary: Implement tailored search result pages on Phonebook → [Tracker] Implement tailored search result pages on Phonebook
No longer blocks: 699598, 699812, 694660, 700479
Depends on: 699598, 699812, 694660
Depends on: 766134
Depends on: 766139
Depends on: 766143
Depends on: 763513
Attachment #619872 - Attachment is obsolete: true
Attachment #619881 - Attachment is obsolete: true
Attachment #619882 - Attachment is obsolete: true
Attachment #609243 - Attachment is obsolete: true
Attachment #609246 - Attachment is obsolete: true
Attachment #610454 - Attachment is obsolete: true
Attachment #619862 - Attachment is obsolete: true
Attachment #619863 - Attachment is obsolete: true
Attachment #619868 - Attachment is obsolete: true
Attachment #619878 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 9 years ago
No longer depends on: 766134
Resolution: --- → FIXED
Whiteboard: [UX][Re-Design] → [UX][Re-Design][Triage 2015-04-17]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: