It looks great, well done.
However, I leave some comments:
* With my configuration, contents slightly overflow the page when using
a window of between 481 and 560 px wide. I would increase the border
between mobile and desktop view from 480 px to ~550 px (or would modify
contents so that we didn't need to modify that limit).
http://davidabian.com/screenshots/wikimedia/wikipedia-org-485.png
* Having written a topic in the search box, the selected summary
overflows the box after clicking.
http://davidabian.com/screenshots/wikimedia/wikipedia-org-results-overflowi…
* While a license (CC BY-SA 3.0) is specified in the HTML (<link
rel="license" href="//creativecommons.org/licenses/by-sa/3.0/">), no
license is displayed to the user.
And some questions:
* Are you planning to make something similar with wikimedia.org?
* Do you follow a specific order when linking to the sister projects? I
see that wikipedia.org and wikimedia.org show the projects in a
different order.
Thank you!
El 11/03/16 a las 19:18, Deborah Tankersley escribió:
> Hello!
>
> I'm very pleased to announce that we've updated the Wikipedia.org
> <http://wikipedia.org/> portal page with a brand new search box that is
> more prominent and will now display meta data with images (as available)
> in the search results (link
> <https://commons.wikimedia.org/wiki/File:New_searchbox_with_metadata.png>).
>
> This was a large effort by the Discovery Portal team to develop a
> JavaScript-only version of the language picker, so that JavaScript
> enabled browsers will see all the new meta data. Alongside that effort,
> we also ensured that in JavaScript (JS) disabled browsers (or older
> Internet Explorer versions), our visitors won't have a bad experience
> when choosing a language to search in. (Note 1: in older IE versions and
> JS disabled browsers, the type-ahead and meta data search results
> information will not be displayed.)
>
> We also implemented a shorter language code (ie: EN for English, ES for
> Spanish, etc) to allow for more characters to be typed into the search
> box. When a user toggles the language selector, the full language name
> will be displayed in the dropdown for easy finding of the language you
> prefer to search in. For the more technical minded - I've also uploaded,
> to Commons, a screenshot
> <https://commons.wikimedia.org/wiki/File:Sample_browsers_tested.png> of
> one of the ways we test our code, visually.
>
> We're interested in hearing your feedback or if you have any questions!
> (Note 2: My apologies for not getting this email out yesterday, but I
> had had issues with size limitations of my screenshots.)
>
> On behalf of the very happy Wikipedia.org Portal Team,
>
> Deb
> --
> Deb Tankersley
> Product Manager, Discovery
> Wikimedia Foundation
>
>
> _______________________________________________
> Wikitech-ambassadors mailing list
> Wikitech-ambassadors(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
--
David Abián - davidabian.com
Vocal de Comunicación
Wikimedia España
Vega Sicilia, 2
47008 - Valladolid
https://wikimedia.es
Wikimedia España es una asociación sin ánimo de lucro española con
CIF G-10413698 inscrita en el Registro Nacional de Asociaciones,
Grupo 1, Sección 1, Núm. Nacional 597390.
«Imagina un mundo en el que cada persona
tenga acceso libre a todo el conocimiento»
On 11 March 2016 at 16:09, Samuel Klein <meta.sj(a)gmail.com> wrote:
>
> Perhaps you could do this w two queries, one to a composite index that is
> only updated weekly.
>
Indeed, there are mechanisms that can make cross-wiki searching more
feasible. In fact, one mechanism we are in the very early stages of
exploring is merging all the projects in a given language into a single
index, so that one could search *all* projects in a language, rather than
just a single project in a given language. I have no timeline here; as I
said, we're in the very early stages, and of course we have other work on
the go at the same time.
> > Additionally, it would likely return you a bunch of really irrelevant
> results,
>
> Make this opt-in, add a different background color for results from the
> all-language index, & divide their search-relevance by a
> language-prominence factor...
>
I plan to worry more about the user experience implications that I
mentioned once we're a bit closer to solving the technical feasibility
questions. As you've shown, these are definitely solvable problems, but I
don't want to put the cart before the horse, as it were. :-)
Thanks,
Dan
--
Dan Garry
Lead Product Manager, Discovery
Wikimedia Foundation
On 11 March 2016 at 10:52, ViswaPrabha (വിശ്വപ്രഭ) <vp2007(a)gmail.com> wrote:
>
> Failed my dream :(
>
> Any string in any language in any wikipedia project. How far is my dream?
>
I share your dream! :-)
Unfortunately, the dream is quite far away from reality. Querying every
search index would put a big performance strain on the search servers.
Additionally, it would likely return you a bunch of really irrelevant
results, so there's a lot of user experience implications that would need
to be figured out as well. Discovery is not actively working on this at
present.
Thanks,
Dan
--
Dan Garry
Lead Product Manager, Discovery
Wikimedia Foundation
Hello!
I'm very pleased to announce that we've updated the Wikipedia.org
<http://wikipedia.org/> portal page with a brand new search box that is
more prominent and will now display meta data with images (as available) in
the search results (link
<https://commons.wikimedia.org/wiki/File:New_searchbox_with_metadata.png>).
This was a large effort by the Discovery Portal team to develop a
JavaScript-only version of the language picker, so that JavaScript enabled
browsers will see all the new meta data. Alongside that effort, we also
ensured that in JavaScript (JS) disabled browsers (or older Internet
Explorer versions), our visitors won't have a bad experience when choosing
a language to search in. (Note 1: in older IE versions and JS disabled
browsers, the type-ahead and meta data search results information will not
be displayed.)
We also implemented a shorter language code (ie: EN for English, ES for
Spanish, etc) to allow for more characters to be typed into the search box.
When a user toggles the language selector, the full language name will be
displayed in the dropdown for easy finding of the language you prefer to
search in. For the more technical minded - I've also uploaded, to Commons,
a screenshot
<https://commons.wikimedia.org/wiki/File:Sample_browsers_tested.png> of one
of the ways we test our code, visually.
We're interested in hearing your feedback or if you have any questions! (Note
2: My apologies for not getting this email out yesterday, but I had had
issues with size limitations of my screenshots.)
On behalf of the very happy Wikipedia.org Portal Team,
Deb
--
Deb Tankersley
Product Manager, Discovery
Wikimedia Foundation
Hi,
first of all: congrats for this new search box!
I noticed that you use action=query with both generator=prefixsearch and
list=prefixsearch.
IIRC when we looked at this (it was when we looked at the way some API
consumers generates their requests) we noticed that it generates 2
prefixsearch queries on the backend. I think this adds unnecessary latency.
Unfortunately I don't know why you need to use list and generator at the
same time, is this a limitation of the API?
If we can't fix the API call could we work on a cache at the backend
level to avoid 2 elasticsearch queries?
Thanks!
Hello!
I'm very pleased to announce that we've updated the Wikipedia.org
<http://wikipedia.org/> portal page with a brand new search box that is
more prominent and will now display meta data with images (as available) in
the search results (see attached image).
This was a large effort by the Discovery Portal team to develop a
JavaScript-only version of the language picker, so that JavaScript enabled
browsers will see all the new meta data. Alongside that effort, we also
ensured that in JavaScript (JS) disabled browsers (or older Internet
Explorer versions), our visitors won't have a bad experience when choosing
a language to search in. (Note: in older IE versions and JS disabled
browsers, the type-ahead and meta data search results information will not
be displayed.)
We also implemented a shorter language code (ie: EN for English, ES for
Spanish, etc) to allow for more characters to be typed into the search box.
When a user toggles the language selector, the full language name will be
displayed in the dropdown for easy finding of the language you prefer to
search in. For the more technical minded - I've attached a screenshot of
one of the ways we test our code, visually.
We're interested in hearing your feedback or if you have any questions!
On behalf of the very happy Wikipedia.org Portal Team,
Deb
--
Deb Tankersley
Product Manager, Discovery
Wikimedia Foundation
Hello!
As a result of a user report
<https://www.mediawiki.org/wiki/Help:CirrusSearch/CompletionSuggester#Does_n…>,
I've filed T129545 <https://phabricator.wikimedia.org/T129545> and set the
priority to "Unbreak now!". I've chatted with Erik about this briefly, and
he said he'd investigate. I'm writing this to the list because I think it's
good practice when super high priority stuff is dropped in the sprint. :-)
Thanks,
Dan
--
Dan Garry
Lead Product Manager, Discovery
Wikimedia Foundation
Hi everybody,
Following up on last week's email, the team has made significant
improvements to the *enhanced search box*:
- We developed a JavaScript-only version of the language picker, on top
of the previous patch, so that users who have JS enabled (93% of our
traffic) get a nicer version of the language picker.
- Shorter language code is displayed, allowing more space for text
within the search input.
- Triggers the native selector on mobile devices.
- The search box looks better overall.
Users who disable JavaScript, or are using old IE versions, get the native
selector already presented in last email.
*It's merged into master, and deployed on beta!*
*Check it out:* http://www.wikipedia.beta.wmflabs.org/
*Deployment to production *
(Phab ticket for reference: Epic T125472
<https://phabricator.wikimedia.org/T125472>)
The patch has been submitted for Thursday's Evening SWAT (Thu 00:00–01:00
UTC, Wed 16:00–17:00 PST)
<https://wikitech.wikimedia.org/wiki/Deployments#Thursday.2C.C2.A0March.C2.A…>
.
Last chance to enjoy the "good old search" https://www.wikipedia.org/ !
Chris <https://www.mediawiki.org/wiki/User:CKoerner_(WMF)> and Deborah
<https://www.mediawiki.org/wiki/User:DTankersley_(WMF)> will answer any
question or concern related to this deployment
*Some screenshots:*
*Modern browsers:*
Chrome, JS: http://i.imgur.com/Jb8JVbd.png
Chrome, no-JS: http://i.imgur.com/JcBfz2h.png (basic language picker
because no JS)
*IE browsers:*
IE8, JS: http://i.imgur.com/Nef2rn6.png (basic language picker because old
IE)
IE9, JS: http://i.imgur.com/o1yrhcA.png (basic language picker because old
IE)
IE10, JS: http://i.imgur.com/OY6MVwJ.png
IE11, JS: http://i.imgur.com/nQUk8fg.png
*Note: the CSS for the suggestions needs some attention, currently seeing
weird padding.*
*Mobile browsers:*
iOS, JS: http://i.imgur.com/7mbCKu6.png
iOS, no-JS: http://i.imgur.com/F2rQpEE.png (basic language picker because
no JS)
Note that JS is required for the typeahead/suggestions feature (this is
already the case with the current page, no regression).
If you don't have JS, you will have to submit the form in order to get
results.
*Next A/B test: Use language detection to re-arrange the primary links to
suit the user better*
*Coming soon!*
The team has also made significant progress, stay tuned!
For the Wikipedia.org portal team,
Julien.
I saw this today and thought it very interesting - Kraft changed their mac
n cheese recipe, last December, to be more healthful but didn't tell anyone
until now. The full story
<http://www.eater.com/2016/3/7/11173858/kraft-mac-and-cheese-different> and
a few key excerpts:
*Kraft announced that the revamped product would hit store shelves in
January — but unbeknownst to customers, it quietly began selling the
artificial-ingredient-free mac and cheese in December. (Only consumers who
paid careful attention to the tiny print of the ingredients list on the
back of the box might have seen the change.) Today, Kraft issued a
self-laudatory press release revealing its little experiment — which it has
deemed "the world's largest blind taste test" — and proclaiming that "fifty
million boxes later ... people didn’t notice a difference."*
*...*
*"We constantly talk to our consumers and get feedback from them, and we
knew they wanted to feel better about the ingredients they serve their
families," Greg Guidotti, vice president of meals at Kraft Heinz, tells
Eater. "We saw an opportunity in the marketplace to improve our ingredient
line, but we didn't want make the change before we had the right recipe."
While the company only announced its intentions to oust artificial
ingredients from mac and cheese in April, Guidotti says they've in fact
been working on the new recipe for more than three years.*
*The idea to do a surreptitious switcheroo with the new mac and cheese was
born out of the skeptical consumer response to Kraft's initial announcement
that it was changing the recipe. "When we announced in April [that we were
changing the recipe] there was excitement but also concern, so we saw it as
an opportunity," Guidotti says. "We knew the recipe still tasted just as
good as you expect from Kraft, but whenever you say you've changed
something, consumers will say it probably won’t taste as good. Since we
knew it tasted exactly the same, we wanted our fans to experience that for
themselves without even being prompted."*
Cheers,
Deb
--
Deb Tankersley
Product Manager, Discovery
Wikimedia Foundation
