[wp-trac] [WordPress Trac] #61040: Provide a framework for plugin onboarding experiences

[WordPress Trac]

#61040: Provide a framework for plugin onboarding experiences
-------------------------+------------------------------
 Reporter:  jorbin       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  administration
-------------------------+------------------------------

Comment (by hellofromTonya):

 I think it's too early to know if a "framework" is needed or not. I'm
 offering a new approach to consider how to move this ticket forward to
 resolution. Allow me to explain.

 The current workflow solves the Plugins Dependency (PD)'s the problem
 statement, as noted from #61319:
 >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?

 Much was learned from the hard removal which led to 6.5.4.

 The #61319's Problem Statements are a great starting point for considering
 if Core should provide the means for the user's next step after
 activation:
 >Plugin companies and their users (which are also this project's users)
 are significantly impacted.
 >
 >It's unknown if the majority of users want or do not want auto-redirect.
 >
 >It's now known that impacted plugin's users do want this ability. The
 size of their user bases is data to suggest the significance of the
 impact.
 >
 >A new onboarding framework needs the benefits of major release cycle to
 understand the impacts, form a scope, do experiments, and then move
 through the product | enhancement stages.

 I suggest repurposing this ticket to:
 1. First, understand the impacts and find out if the majority of users
 identify the "redirect after activation" as a pain point for them.
 2. 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.

 It's too late in 6.6 to land code changes, but it's not too late to start
 working on the above. If changes are needed, starting now could help those
 to land in 6.7.

 What do you all think of this plan and suggestions?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61040#comment:71>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform