The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) https://people.wikimedia.org/~jgirault/react-top9-cards/Trending Showing top 10 articles (full screen) https://people.wikimedia.org/~jgirault/react-top10-fs/
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
Thanks for starting this thread, Julien!
This idea very nicely aligns with the 'revolutionary' and 'evolutionary' improvements idea that I've been harping about for a while. The "labs" page is our space to do revolutionary prototypes, making some crazy things. And the production portal page is where we do evolutionary testing, changing things slowly and more deliberately. This is the only way to find new maximas and not get stuck at a local maxima, https://en.wikipedia.org/wiki/Maxima_and_minima
Looking forward to hearing everyone's thoughts on this.
On Fri, Jan 22, 2016 at 5:58 PM, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) https://people.wikimedia.org/~jgirault/react-top9-cards/Trending Showing top 10 articles (full screen) https://people.wikimedia.org/~jgirault/react-top10-fs/
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
Hi!
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
This looks pretty cool, though I think we need some explanation why these pages are shown.
Also, if you look at it, number 4 is porn site. Which is I guess accurate according to data, but this would produce several problems - starting from obvious appropriateness and PR issues, and to the problem of what happens when companies (even much less controversial than porn sites) learn that they can be easily featured on the front page of Wikipedia. So we may want to be careful there.
Also, https://people.wikimedia.org/~jgirault/react-top10-languages/ is buggy for me: for Hebrew, it shows the name as: <bdi dir="rtl">עברית</bdi> (yes, with HTML tags visible).
Once upon a time, a man called David had an idea for a way to make search better. So he hacked together a little thing and put it in Labs: http://suggesty.wmflabs.org/suggest.html. You guessed it, that turned into the completion suggester that over ten thousand users are trialling as a beta feature. So, yes, setting up some spaces in Labs to do experimental work is a great idea! :-)
The important thing for me to note is that experimental work, like any other work, should be tracked in Phabricator, prioritised by the relevant product owner (Deb in this case), and have clear deliverables. This makes sure we're not just building prototypes for the sake of it because they look awesome and make us feel good, and makes the tradeoffs involved (experimental vs A/B test) more clear.
Naming: I like Portal Labs, because the URL will almost certainly end up looking something like portal.wmflabs.org, portal-2.wmflabs.org, and so on, and that's already got the word labs in there. ;-)
Thanks, Dan
On 22 January 2016 at 17:58, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) https://people.wikimedia.org/~jgirault/react-top9-cards/Trending Showing top 10 articles (full screen) https://people.wikimedia.org/~jgirault/react-top10-fs/
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On Fri, Jan 22, 2016 at 6:25 PM, Dan Garry dgarry@wikimedia.org wrote:
The important thing for me to note is that experimental work, like any other work, should be tracked in Phabricator, prioritised by the relevant product owner (Deb in this case), and have clear deliverables.
Quick minor process point here (which I know Dan knows, but just didn't spell out in this case): Experimental work done during your "10% time" does not need to be prioritized by any product owner. For that work, it might make sense to track it in phab, but it might not, so use your judgment there, or chat with your product owner about it.
Within the few months that Discovery has been officially supporting "10% time" projects, they have already produced some really good work, and have been turned into production features on multiple occasions.
Experimental work that isn't part of the 10% absolutely needs to be phabbed, and then prioritized by the PO.
Kevin
On 25 January 2016 at 14:29, Kevin Smith ksmith@wikimedia.org wrote:
On Fri, Jan 22, 2016 at 6:25 PM, Dan Garry dgarry@wikimedia.org wrote:
The important thing for me to note is that experimental work, like any other work, should be tracked in Phabricator, prioritised by the relevant product owner (Deb in this case), and have clear deliverables.
Quick minor process point here (which I know Dan knows, but just didn't spell out in this case): Experimental work done during your "10% time" does not need to be prioritized by any product owner. For that work, it might make sense to track it in phab, but it might not, so use your judgment there, or chat with your product owner about it.
Thanks, that's exactly what I meant.
Dan
Julien,
I would like to see some examples that are run for the sister wikis, at the moment the trend is for the examples to be very wikiPedia specific. It would be useful to see how these things are useful for the whole wikimedia set of sites. Also for portals, there would be value in providing results in other languages, and sisters. That we limit a search result to the one place we stand rather than the neighbourhood in which we live, indicates living in a world with imposed blinkers.
-- billinghurst
On Sat, Jan 23, 2016 at 12:58 PM, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) Trending Showing top 10 articles (full screen)
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
Setting up a page in labs isn't too hard, you and jan both have admin access to the `search` project in wikitech. I've gone ahead and booted up a new instance there for you, portal.eqiad.wmflabs. I've also added a proxy for it, http://portal.wmflabs.org.
Quite often the easiest way to set something like this up is to make a git repository, and then have a cronjob on the portal just auto-update the git repository. If you want to go that way i can make you a new repo in gerrit or however you want to do it.
For the moment i just copied rutherfordium.eqiad.wmnet:~jgirault/public_html to portal.eqiad.wmflabs:/var/www
On Fri, Jan 22, 2016 at 6:52 PM, billinghurst billinghurstwiki@gmail.com wrote:
Julien,
I would like to see some examples that are run for the sister wikis, at the moment the trend is for the examples to be very wikiPedia specific. It would be useful to see how these things are useful for the whole wikimedia set of sites. Also for portals, there would be value in providing results in other languages, and sisters. That we limit a search result to the one place we stand rather than the neighbourhood in which we live, indicates living in a world with imposed blinkers.
-- billinghurst
On Sat, Jan 23, 2016 at 12:58 PM, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal
page
looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can
have
an option to bookmark the page, and maybe make one of the experiments
their
default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype
page
that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) Trending Showing top 10 articles (full screen)
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think
about
it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On Fri, Jan 22, 2016 at 6:16 PM, Stas Malyshev smalyshev@wikimedia.org wrote:
Hi!
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
This looks pretty cool, though I think we need some explanation why these pages are shown.
Agree. Note that these are *early* prototypes, they haven't gone through any product/design/community/engineer reviews. They're here mainly to illustrate the idea. Nonetheless, I love seeing feedback already.
Also, if you look at it, number 4 is porn site. Which is I guess accurate according to data, but this would produce several problems - starting from obvious appropriateness and PR issues, and to the problem of what happens when companies (even much less controversial than porn sites) learn that they can be easily featured on the front page of Wikipedia. So we may want to be careful there.
Good points Stas. The Reading team is also interested in trending articles. There will be a meeting soon to discuss all together about the issues around this feature and the possible implementation(s). Thanks for bringing this up. ^ Deborah: you can start a list :)
Also, https://people.wikimedia.org/~jgirault/react-top10-languages/ is buggy for me: for Hebrew, it shows the name as: <bdi dir="rtl">עברית</bdi> (yes, with HTML tags visible).
Good catch. There are bugs indeed (as well as many minor improvements to do), and they'll have to be fixed (as much as we can) before we deploy to our users. Again, these are early prototypes :)
On Fri, Jan 22, 2016 at 6:52 PM, billinghurst billinghurstwiki@gmail.com wrote:
Julien,
I would like to see some examples that are run for the sister wikis, at the moment the trend is for the examples to be very wikiPedia specific. It would be useful to see how these things are useful for the whole wikimedia set of sites.
I'd like to point to https://phabricator.wikimedia.org/T110070#1653320 where Dan explains better than me that we are not responsible for the sister portals. Not that we don't care, but we just don't have the resources to improve all sites at the same time, so we decided to focus our efforts on the portal that gets huge traffic.
Jan and I have met mxn (the maintainer of sister portals) in person, and he was convinced that the new typeahead would be a great improvement for, at least, www.wiktionary.org . Jan coded the typeahead feature in a way that's exportable. If the community wants to follow our path and implement what they like from what we do, they sure can. The code is open source, and we may even find some time to help if needed.
Also for portals, there would be value in providing results in other languages, and sisters. That we limit a search result to the one place we stand rather than the neighbourhood in which we live, indicates living in a world with imposed blinkers.
Agree. This is something we definitely want to explore. We have an incredible amount of knowledge, why should we only expose a part of it to our users?
But this kind of test is hard to do right now without changing the page too much. This is exactly why I feel having a faster, more revolutionary train - that does not impact our users negatively - will drive discovery up.
*Thank you for your comments. * Please keep telling us what you think about this.
On Fri, Jan 22, 2016 at 7:45 PM, Erik Bernhardson < ebernhardson@wikimedia.org> wrote:
Setting up a page in labs isn't too hard, you and jan both have admin access to the `search` project in wikitech. I've gone ahead and booted up a new instance there for you, portal.eqiad.wmflabs. I've also added a proxy for it, http://portal.wmflabs.org.
Quite often the easiest way to set something like this up is to make a git repository, and then have a cronjob on the portal just auto-update the git repository. If you want to go that way i can make you a new repo in gerrit or however you want to do it.
For the moment i just copied rutherfordium.eqiad.wmnet:~jgirault/public_html to portal.eqiad.wmflabs:/var/www
Thank you for jumping on this, though the aim of this thread was to have a discussion and move forward (with this kind of technical operations) *only once* we get a common feeling that this is a good idea and we figured out the concerns that people may have.
Nonetheless, I'm sure removing this is just as easy as setting it up, so I don't see any harm for now.
On 22 January 2016 at 20:43, Julien Girault jgirault@wikimedia.org wrote:
Thank you for jumping on this, though the aim of this thread was to have a discussion and move forward (with this kind of technical operations) *only once* we get a common feeling that this is a good idea and we figured out the concerns that people may have.
Nonetheless, I'm sure removing this is just as easy as setting it up, so I don't see any harm for now.
Yeah, these things can be pulled down and replaced with something else with just a few console commands, so I don't think there's any problems here either. :-)
Dan
I really like this idea but I'd recommend we use it for more qualitative than quantitative feedback, unless we have a solid plan to surface the labs page to a good sample of users.
On 23 January 2016 at 00:07, Dan Garry dgarry@wikimedia.org wrote:
On 22 January 2016 at 20:43, Julien Girault jgirault@wikimedia.org wrote:
Thank you for jumping on this, though the aim of this thread was to have a discussion and move forward (with this kind of technical operations) only once we get a common feeling that this is a good idea and we figured out the concerns that people may have.
Nonetheless, I'm sure removing this is just as easy as setting it up, so I don't see any harm for now.
Yeah, these things can be pulled down and replaced with something else with just a few console commands, so I don't think there's any problems here either. :-)
Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
On Billinghurst's point I would really love to see the changes that have been successful tested on (particularly) Wikisource, where I imagine that the dropdown metadata could be tremendously valuable.
On 25 January 2016 at 07:42, Oliver Keyes okeyes@wikimedia.org wrote:
I really like this idea but I'd recommend we use it for more qualitative than quantitative feedback, unless we have a solid plan to surface the labs page to a good sample of users.
On 23 January 2016 at 00:07, Dan Garry dgarry@wikimedia.org wrote:
On 22 January 2016 at 20:43, Julien Girault jgirault@wikimedia.org wrote:
Thank you for jumping on this, though the aim of this thread was to have a discussion and move forward (with this kind of technical operations) only once we get a common feeling that this is a good idea and we figured out the concerns that people may have.
Nonetheless, I'm sure removing this is just as easy as setting it up, so I don't see any harm for now.
Yeah, these things can be pulled down and replaced with something else with just a few console commands, so I don't think there's any problems here either. :-)
Dan
-- Dan Garry Lead Product Manager, Discovery Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
-- Oliver Keyes Count Logula Wikimedia Foundation
For domain name and hosting: should it be a production domain name on a production host?
On Friday, January 22, 2016, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) https://people.wikimedia.org/~jgirault/react-top9-cards/Trending Showing top 10 articles (full screen) https://people.wikimedia.org/~jgirault/react-top10-fs/
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
...that is, if it is prioritized for a link from the portal homepage, anyway.
On Monday, January 25, 2016, Adam Baso abaso@wikimedia.org wrote:
For domain name and hosting: should it be a production domain name on a production host?
On Friday, January 22, 2016, Julien Girault <jgirault@wikimedia.org javascript:_e(%7B%7D,'cvml','jgirault@wikimedia.org');> wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) https://people.wikimedia.org/~jgirault/react-top9-cards/Trending Showing top 10 articles (full screen) https://people.wikimedia.org/~jgirault/react-top10-fs/
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
Good Q. I guess my question would be about the practical costs in setup, deployment and patch time for a prod service.
On 25 January 2016 at 11:24, Adam Baso abaso@wikimedia.org wrote:
...that is, if it is prioritized for a link from the portal homepage, anyway.
On Monday, January 25, 2016, Adam Baso abaso@wikimedia.org wrote:
For domain name and hosting: should it be a production domain name on a production host?
On Friday, January 22, 2016, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our portal page, things that are completely different than what the current portal page looks like, and deploy it on this site for real users to use. But without imposing a disruptive user experience to our users. We can put a link to this page on the production portal page (in the bottom?), and users can have an option to bookmark the page, and maybe make one of the experiments their default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype page that points to a Phab ticket where community can add comments/feedback).
To give you an example of what we mean by revolutionary ideas, I uploaded some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) Trending Showing top 10 articles (full screen)
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or beta portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
Yeah, had a similar concern. I was wondering if a non-indexed subdir would do the trick. Naturally any code deployed for potentially so many users would need scrutiny for simple stuff like XSS, and I imagine analytics scripts would have to factor in the sub site.
On Monday, January 25, 2016, Oliver Keyes okeyes@wikimedia.org wrote:
Good Q. I guess my question would be about the practical costs in setup, deployment and patch time for a prod service.
On 25 January 2016 at 11:24, Adam Baso <abaso@wikimedia.org javascript:;> wrote:
...that is, if it is prioritized for a link from the portal homepage, anyway.
On Monday, January 25, 2016, Adam Baso <abaso@wikimedia.org
javascript:;> wrote:
For domain name and hosting: should it be a production domain name on a production host?
On Friday, January 22, 2016, Julien Girault <jgirault@wikimedia.org
wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our
portal
page, things that are completely different than what the current
portal page
looks like, and deploy it on this site for real users to use. But
without
imposing a disruptive user experience to our users. We can put a link
to
this page on the production portal page (in the bottom?), and users
can have
an option to bookmark the page, and maybe make one of the experiments
their
default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on
the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also
collect
traffic and clickthrough rate to measure user satisfaction. We can also implement a "Send a Feedback" feature (or have a link on the prototype
page
that points to a Phab ticket where community can add
comments/feedback).
To give you an example of what we mean by revolutionary ideas, I
uploaded
some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) Trending Showing top 10 articles (full screen)
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs, or
beta
portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/discovery
-- Oliver Keyes Count Logula Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/discovery
All fantastic stuff!! :) Thanks, Julien, Jan and Erik for taking the initiative on this and getting things setup!
I'll start gathering notes and chat with Moiz on the best way to show a link on the portal page to direct users that would want to test out our ideas.
We'll also need to redo the "testing" site page so that each test is clearly explained and give the users a chance to make comments in a Phab ticket for the test.
So exciting! :)
Cheers,
Deb
-- Deb Tankersley Product Manager, Discovery Wikimedia Foundation
On Mon, Jan 25, 2016 at 9:32 AM, Adam Baso abaso@wikimedia.org wrote:
Yeah, had a similar concern. I was wondering if a non-indexed subdir would do the trick. Naturally any code deployed for potentially so many users would need scrutiny for simple stuff like XSS, and I imagine analytics scripts would have to factor in the sub site.
On Monday, January 25, 2016, Oliver Keyes okeyes@wikimedia.org wrote:
Good Q. I guess my question would be about the practical costs in setup, deployment and patch time for a prod service.
On 25 January 2016 at 11:24, Adam Baso abaso@wikimedia.org wrote:
...that is, if it is prioritized for a link from the portal homepage, anyway.
On Monday, January 25, 2016, Adam Baso abaso@wikimedia.org wrote:
For domain name and hosting: should it be a production domain name on a production host?
On Friday, January 22, 2016, Julien Girault jgirault@wikimedia.org wrote:
The Discovery Portal team has been thinking about a Portal Labs page.
The idea is that we can implement some revolutionary ideas for our
portal
page, things that are completely different than what the current
portal page
looks like, and deploy it on this site for real users to use. But
without
imposing a disruptive user experience to our users. We can put a link
to
this page on the production portal page (in the bottom?), and users
can have
an option to bookmark the page, and maybe make one of the experiments
their
default.
We would have two trains:
- Slow train: running regular A/B tests (like the one we just ran) on
the
official portal page and deploying small improvements as we learn.
- Faster train: "Revolutionary" prototypes in Labs where we also
collect
traffic and clickthrough rate to measure user satisfaction. We can
also
implement a "Send a Feedback" feature (or have a link on the
prototype page
that points to a Phab ticket where community can add
comments/feedback).
To give you an example of what we mean by revolutionary ideas, I
uploaded
some of my research time work: https://people.wikimedia.org/~jgirault/
Pay closer attention to: Trending Showing top 9 articles (grid) Trending Showing top 10 articles (full screen)
This would allow us to think outside the box and test different layouts/features, with real users who chose to.
This is kind of a crazy idea, and we want to know what you all think about it. Also we would need some naming ideas for it. Portal labs,
or beta
portal, or something else.
Please let us know what you think about this, how you think we can go towards making this happen and what we should name it.
Thanks! Julien
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
-- Oliver Keyes Count Logula Wikimedia Foundation
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery
discovery mailing list discovery@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/discovery