Change Details

== Background Over the years it seems that other teams/community have chipped away at the feature and enabled AMC features for all logged in users. Doing a quick audit enabling AMC mode in 2026 does three things: * Disables a simplified view for watchlist, contributions and history page exposing power editor features * Adds recent changes, special pages and community portal to the left (main/hamburger) menu * Adds user talk, sandbox and watchlist to the user personal menu Given the above I think we should remove the AMC mode (see proposal) == User story As a user I should not need to enable an advanced mobile mode to access features. == Requirements - Add task requirements. Requirements should be user-centric, well-defined, unambiguous, implementable, testable, consistent, and comprehensive === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - Add mockups and design requirements == Proposal Instead of the existing AMC mode I suggest we enable features based on user behaviour. [] We expose the recent changes page once a user gets the rollback permission [] We expose the user talk page if a user has a non-empty talk page. [] We expose the sandbox page once a user has an edit count greater than 10 (TBC) [] We expose community portal based on edit count [] We expose special pages based on user rights (TBC) [] We expose the watchlist page once an editor has a certain edit count, user right OR has used features in the watchlist (eg. created labels or watched articles) [] We disable simplified view of watchlist, contributions and history page when a user gets the rollbacker or new page reviewer user right Once the above is done, we drop AMC and associated code. == Acceptance criteria - Add acceptance criteria == Communication criteria - does this need an announcement or discussion? - Add communication criteria == 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 Over the years it seems that other teams/community have chipped away at the feature and enabled AMC features for all logged in users. Doing a quick audit enabling AMC mode in 2026 does three things: * Disables a simplified view for watchlist, contributions and history page exposing power editor features * Adds recent changes, special pages and community portal to the left (main/hamburger) menu * Adds user talk, sandbox and watchlist to the user personal menu Given the above I think we should remove the AMC mode (see proposal) == User story As a user I should not need to enable an advanced mobile mode to access features. == Requirements - Add task requirements. Requirements should be user-centric, well-defined, unambiguous, implementable, testable, consistent, and comprehensive === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - Add mockups and design requirements == Proposal Instead of the existing AMC mode I suggest we enable features based on user behaviour. The logic for these decisions **would also apply to desktop editors**. [] We expose the recent changes page once a user gets the rollback permission [] We expose the user talk page if a user has a non-empty talk page. [] We expose the sandbox page once a user has an edit count greater than 10 (TBC) [] We expose community portal based on edit count [] We expose special pages based on user rights (TBC) [] We expose the watchlist page once an editor has a certain edit count, user right OR has used features in the watchlist (eg. created labels or watched articles) [] We disable simplified view of watchlist, contributions and history page when a user gets the rollbacker or new page reviewer user right Once the above is done, we drop AMC and associated code. == Acceptance criteria - Add acceptance criteria == Communication criteria - does this need an announcement or discussion? - Add communication criteria == 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 Over the years it seems that other teams/community have chipped away at the feature and enabled AMC features for all logged in users. Doing a quick audit enabling AMC mode in 2026 does three things: * Disables a simplified view for watchlist, contributions and history page exposing power editor features * Adds recent changes, special pages and community portal to the left (main/hamburger) menu * Adds user talk, sandbox and watchlist to the user personal menu Given the above I think we should remove the AMC mode (see proposal) == User story As a user I should not need to enable an advanced mobile mode to access features. == Requirements - Add task requirements. Requirements should be user-centric, well-defined, unambiguous, implementable, testable, consistent, and comprehensive === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - Add mockups and design requirements == Proposal Instead of the existing AMC mode I suggest we enable features based on user behaviour. The logic for these decisions **would also apply to desktop editors**. [] We expose the recent changes page once a user gets the rollback permission [] We expose the user talk page if a user has a non-empty talk page. [] We expose the sandbox page once a user has an edit count greater than 10 (TBC) [] We expose community portal based on edit count [] We expose special pages based on user rights (TBC) [] We expose the watchlist page once an editor has a certain edit count, user right OR has used features in the watchlist (eg. created labels or watched articles) [] We disable simplified view of watchlist, contributions and history page when a user gets the rollbacker or new page reviewer user right Once the above is done, we drop AMC and associated code. == Acceptance criteria - Add acceptance criteria == Communication criteria - does this need an announcement or discussion? - Add communication criteria == 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 ]] //