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

 The biggest issue I'm seeing is that we're yet to reach a common agreement
 on the following:

 1. Beginner users DO install multiple plugins every time they install an
 addon before they have its dependency, whether that's WooCommerce, Yoast
 SEO, Gravity Forms, or any other highly extended plugin.

 We have all likely worked with a lot of users of various demographics, yet
 there is disagreement amongst us. This should serve as a reminder that we
 should avoid extrapolating our personal experiences to represent
 percentages of users who do X or Y.

 We need data, which should be gained by #outreach, and should avoid a tone
 of "do you want this, or just want it to go back to before?", as that
 approach risks people opting for negatives just because they've learned to
 deal with them.

 2. Whether or not it's confusing to add a Configure/Get Started button to
 the flow.

 This button would be in the same place as the Activate button they just
 clicked, which is in the same place as the Install Now button they clicked
 previously. It's an extra click, but being in the same place as the
 previous buttons means it's much less likely that a user won't find it.

 This not only adds back user control over what happens next, but also
 ensures that dependencies can be installed and activated before their
 dependents (note: dependencies are not "nice-to-haves". They are
 prerequisites much like WP/PHP versions). Furthermore, it provides a
 consistent entrypoint for plugin and theme authors via a filter that can
 also be used by the admin redesign for a future Gutenberg-based plugin
 management screen.

 -----

 I'd ask that rather than pushing for a revert, which has a wider impact
 than forced redirects, that we instead get data from a project-led
 outreach program so that we can build on what we have for users and for
 the project's future plans for these administration areas.

 The outreach should be mindful of context: WordPress Core is and isn't
 like other software, such as Install + Activate being different steps, we
 don't bypass user consent and control by bulk installing/activating
 dependencies, we must be transparent by ensuring they can view details of
 a dependency before they consider installing and activating it, and the
 dependencies often appear within the same directory as their dependents
 (except for non-dotorg hosted plugins).

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