This was another option explored to match the style with how we show namespaces on commons. But as you can see (as indicated by the pink line) the alignment looks disorganized which negatively impacts scanning of information. Hence we should go with the option mentioned in the description.

@Seddon

In T307605#7939828, @Sneha wrote:

This was another option explored to match the style with how we show namespaces on commons. But as you can see (as indicated by the pink line) the alignment looks disorganized which negatively impacts scanning of information. Hence we should go with the option mentioned in the description.

@Seddon

The advantage of this one though is that it matches the style used on MediaSearch. Should we be considering alignment there?

Media search does not have the alignment issues as they don't need to mix results with thumbnails. They are all without thumbnails as far as I checked.

Stupid question, I'm sure, but would a thumb on the right work?
Something along these lines:

Google also does something similar, it appears:

(it would probably also make it easier to deal with main namespace articles lacking thumbs; wouldn't even need a placeholder then)

@matthiasmullie with thumbnails on the right we still have alignment issue on the left with blue titles. Also having thumbnail on the right does not lend itself well for opening quick view and the affordances we need for users to know that tapping on snippet will open something on the right. Thumbnails are also connected with article title as they both take you directly to the article.

The only issue with not having quickview for the other name spaces is that we are moving the metadata into the panel. Not a deal breaker I suspect, but there are real possible benefits to serving things like Table of Contents etc. in that panel. It could be an interesting venue for explaining process pages etc. to users. This is all out of scope at the moment, but it feels like a real area of opportunity. But I don't think adding more than metadata needs to be an immediate priority right now though.

Generally (though not ubiquitously) the default namespace is the main article space and you need to have expressed an interest in including other administrative or discussion focused namespaces to see them. is an option of adding it above the title?

I do find the namespace tag useful so this could even be a feature if we have time later down the line or in the future that we could have people enable or disable in preferences.

Yeah having the tags above is a good option. It may make the individual results height a bit variable so will try and see how it looks.

Good point about metadata! In that case I think we should leave the metadata outside for now until we figure out (through user research) how editors use search. The current changes in the experiences are done with readers in mind. I would assume namespaces is mostly used by editors and what would be useful for them is still not clear and so would not introduce quick view for it yet without doing proper research. The changes we are doing for phase 1 are mostly reader focused.

just an observation on the screenshots: the redirect information in wikipedia search is shown next to the title which seems better. If we do tags it should only be reserved for namespaces.

I did some more explorations on using namespace tags. I prefer exploration #1 as it keeps the main elements in the same location. #2 the tags float around a bit too much as it will depend on the length of the title and #3 the varying heights in the results makes the page look less cohesive.

Exploration 1 (preferred)

Exploration 2

Exploration 3

Hello, since we have not reached a solution yet I wanted to summarize all the explorations here and feedback I received from design review.

I found out that there is a discussion happening about how namespaces are shown on the pages itself here. So Alex pointed out that tags may differ from how they are shown on actual pages and make it a little inconsistent. While tags really help distinguish the namespace results from article results we lose the opportunity to educate advance searchers that they can directly type the namespace and colon in front of the query to search for it.

I do wish we had more data on how users are using advanced search - if they are searching in multiple namespaces at once then making it more prominent makes sense. If they are searching one at a time then it is perhaps okay to go with text only approach. If they are using search bar to search namespace then its perhaps one at at time.

If we want to keep tags there was a unanimous agreement that having it in the front/top is better than at the end of content. However there is still mixed preferences for having it at top/front of article vs next to metadata. We can also explore using the thumbnail space i.e. come up with a thumbnail sized tag for each.

Or we can leave it as is for now which I think would be okay given we don't fully understand how they are being used.

Let me know if you have any thoughts on this before I explore any further.

Based on community feedback, we've decided to put this ticket into the backlog for now to revaluate later:

Some users were concerned that adding namespace tags might make copying the search results more difficult. There was also discussion that the visible namespace tags might be confusing to newcomers who don't know what they mean. A user also noted that namespace tags don't appear elsewhere in the UI, and so this wouldn't be consistent.