Change Details

== Background - We would like to explore recommendations in a few different places on the page, including alongside articles. One of the things we want to explore is reusing the current extension to == User story - As a product team, we want the ability to test more recommendation features in a lightweight way, so we can learn quicker == Requirements [] No changes must be seen by end user while we're building out this functionality. Deployment will be handled separately. [] At lower screen resolutions it does not show at all. [] For long titles limit to 2 lines. [] Build feature as per requirement using MoreLike API. The cards shown should be identically sourced to the empty search experiment. [] Instrumentation for recommendations alongside articles must be as follows: - We want to detect whether clicks come from people using browser extension or not - We want to count the number of clicks on recommendations on the side of the article - Instrumentation should be distinguishable from the previous experiment - previously we used experiment.emptySearch use experiment.sidebar === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design TBD == Acceptance criteria - Complete all requirements - Flag any unknowns and ask appropriate stakeholders - Set up ticket for launching experiment == Communication criteria - does this need an announcement or discussion? - Another survey perhaps == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //

== Background - We would like to explore recommendations in a few different places on the page, including alongside articles. One of the things we want to explore is reusing the current extension to == User story - As a product team, we want the ability to test more recommendation features in a lightweight way, so we can learn quicker == Requirements [] No changes must be seen by end user while we're building out this functionality. Deployment will be handled separately. [] At lower screen resolutions it does not show at all. [] the menu cannot be pinned and is always shown [] For long titles limit to 2 lines. [] Build feature as per requirement using MoreLike API. The cards shown should be identically sourced to the empty search experiment. [] Instrumentation for recommendations alongside articles must be as follows: - We want to detect whether clicks come from people using browser extension or not - We want to count the number of clicks on recommendations on the side of the article - Instrumentation should be distinguishable from the previous experiment - previously we used experiment.emptySearch use experiment.sidebar === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design TBD == Acceptance criteria - Complete all requirements - Flag any unknowns and ask appropriate stakeholders - Set up ticket for launching experiment == Communication criteria - does this need an announcement or discussion? - Another survey perhaps == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //

== Background - We would like to explore recommendations in a few different places on the page, including alongside articles. One of the things we want to explore is reusing the current extension to == User story - As a product team, we want the ability to test more recommendation features in a lightweight way, so we can learn quicker == Requirements [] No changes must be seen by end user while we're building out this functionality. Deployment will be handled separately. [] At lower screen resolutions it does not show at all. [] the menu cannot be pinned and is always shown [] For long titles limit to 2 lines. [] Build feature as per requirement using MoreLike API. The cards shown should be identically sourced to the empty search experiment. [] Instrumentation for recommendations alongside articles must be as follows: - We want to detect whether clicks come from people using browser extension or not - We want to count the number of clicks on recommendations on the side of the article - Instrumentation should be distinguishable from the previous experiment - previously we used experiment.emptySearch use experiment.sidebar === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design TBD == Acceptance criteria - Complete all requirements - Flag any unknowns and ask appropriate stakeholders - Set up ticket for launching experiment == Communication criteria - does this need an announcement or discussion? - Another survey perhaps == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //