Exploring different ideas on we can show content from Wikipedia and sister projects in one place on the www.wikipedia.org portal.
Hey @MSyed, don't you think this "universal language search" mock conflicts a bit with the language picker within the search box?
On mock 1, as a user I don't understand what "1200 more" refers to... I would prefer more explicit "Find Wikipedia in 1200+ languages:" but then comes the i18n issue.
On mock 2, as a user I understand what it is though I don't really expect this regular link to open such a big search box... When I look at it it looks a little weird, but why not.
Also, when you do mocks, I would sincerely love to see mobile mocks. I believe in mobile first, because whatever we design on desktop will most of the time need to be redesigned on mobile... (applies for all these mocks)
For this test: the trending articles will be “static” - we’re looking to see who clicks on the trending articles rather than making sure the trending algorithm works. The trending articles will have localized (based on the top 10 languages) labels for the trending articles and we’ll use the user’s browser’s preferred language.
A different look for the portal - using the Picture of the Day (has attribution) with search box under wikipedia word mark image.
Another look for the portal - using the Picture of the Day (has attribution) with a globe in the lower left hand corner and word mark/search box in the top right hand side of the image.
When clicking / hovering over the globe in the lower left hand side will bring up a modal - showing two different looks for the modal.
Modal showing links to sister Wiki sites in table order:
Modal showing links to sister Wiki sites around the picture of the day small image:
I've some concerns with the large Picture of the Day background image idea. I've shared them with most of Portal team members already but want to share them here too, just for the record:
- Having a large background image will slow down the load times of the page tremendously, esp. for people with bad connections.
- Since the background image will take a long time to load, the content on top of the background image needs to look good with or without the background image. Which is going to add another layer of difficulty.
- Picture of the day will have unpredictable colors, so we will have to take that into account too, to make sure that the content on top of the image is visible. To do this, we will need to have some human curation layer involved every day the image changes.
- The image visually overwhelms the page and takes attention from other important parts of the page, like the search box.
- Most importantly, I don't see a clear pressing user-need being addressed with this feature. If we want to give our users access to commons picture of the day, I think there are other ways to do it without making it too overwhelming, design and byte-size wise. But that user need is not our top priority right now because there's so much other things to improve on the page :)
Thanks, @MSyed, for your comments. Can you go ahead and mock up a treatment of the portal page where a link to the picture of the day could be used?
I think it'd be a good A/B test, to see if using the link to the PotD is something that visitors to the page will click through to view.
Attached are mocks for the next few A/B tests.
Test 1, language dropdown:
Test 1, mobile web:
Test 2, mobile web:
Test 3, mobile web:
Test 4, mobile web: