Context Navigation

Changes between Initial Version and Version 1 of Ticket #61040, comment 71

-              initial
+              v1
 >The problem PD aims to solve is that when a plugin has a dependency on another, users are left to their devices which leads to inconsistent user experiences and potential for site breakage by deactivating plugins that are relied upon
 Is an onboarding / configuration / getting started / welcome "next step" needed in Core? Is it known yet that the majority of users identify a pain point of the auto-redirect/auto-load of these experiences?
+Is an onboarding / configuration / getting started / welcome "next step" needed in Core? Is it known yet that the identify a pain point of the auto-redirect/auto-load of these experiences?
 Much was learned from the hard removal which led to 6.5.4.
 …
 I suggest repurposing this ticket to:
 . First, understand the impacts and find out if the majority of users identify the "redirect after activation" as a pain point for them.
+. First, understand the impacts and to find out if the majority of users identify the "redirect after activation" as a pain point for them. (Using the [https://wordpress.org/about/philosophy/ "Design for the majority" philosophy].)
 . If users say yes, then form a problem statement and scope, and then update this ticket's description and title to reflect it. A problem statement and scope will help to guide the ideation through the development cycle.