[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 kevinwhoffman):

 [https://make.wordpress.org/core/2024/05/03/roadmap-to-6-6/ WordPress 6.6]
 is set to be released on July 16, 2024.

 While I appreciate all of the rich conversation, I am also wary of this
 ticket becoming so large in scope that we cannot provide a solution in 6.6
 that addresses the usability regression introduced in 6.5 for plugins that
 require onboarding, a change that led others to call for a reversion.

 In an effort to avoid a reversion and deliver a better solution in 6.6,
 I've split out the various opportunities discussed so far in this ticket,
 stack ranked them according to user need and reach, and recommend pursuing
 them further in separate tickets across successive releases.

 **1. Immediate Need (6.6): Answering the Question, "What do I do next?"
 After Plugin Activation

 If teleporting users via redirect is no longer a suitable solution, then
 we ought to provide a clearly marked bridge for users to navigate from
 activation to onboarding themselves. By keeping the scope small and
 positioning a solution like the "Open" link as a progressive enhancement,
 we can avoid reverting Plugin Dependencies altogether and provide a
 solution that is even better than redirects in time for 6.6.

 **2a. Iterative Improvement (6.6 or later): Plugin Dependencies Workflow**

 I appreciate that @alanfuller highlighted a few pain points, some of which
 @costdev clarified are already being addressed. As @afragen said in
 [https://wordpress.slack.com/archives/CULBN711P/p1715796668735969 Slack],
 the Plugin Dependencies feature has a long history that should be
 understood before making further changes. Because of that history, I
 recommend that improvements to the Plugin Dependencies workflow happen
 outside of this ticket. We should be mindful of how dependencies affect
 activation and onboarding, but in order to address Item 1 quickly, we are
 better off treating the plugin dependency workflow as a detour ''on the
 way'' to activation that doesn't necessarily restrict what happens
 ''after'' activation.

 **2b. Nice-to-Have (6.7): Combine "Install and Activate" into one step on
 the Add Plugins screen.**

 This would be a small victory that reduces time to value and the steps
 necessary to activate a plugin, but it does not necessarily need to be
 coupled with Item 1. We still need to clarify how we are going to maintain
 the ability to "Install Only" if "Install and Activate" becomes the new
 default, which is likely to lead to debate. Therefore it is better
 approached as a separate issue in order to ensure Item 1 can be done in
 time for the 6.6 release.

 **3. Someday: A full-fledged onboarding framework**

 Some have rightly called out that adding an "Open" link or combining
 "Install and Activate" does not constitute a framework, to which I say
 maybe the scope of this ticket was too broad to begin with. This ticket
 was born out of discussion in #60992 specifically around the transition
 from plugin activation to onboarding. Item 1 addresses that need and
 should be our immediate focus for 6.6. Work towards a more complete
 onboarding framework should happen in concert with the
 [https://make.wordpress.org/core/2023/07/12/admin-design/ Admin Design]
 effort and should not be considered a blocker to Item 1.

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