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

 > Activated one plugin: Redirect them
 > Activated many plugins: Display an admin notice
 > Activated via WP-CLI: Nothing? Perhaps show the URL to finish
 configuration at
 > Activated remotely: Return the URL

 One issue is that on `Plugins > Add New`, there was no way to allow a user
 to activate multiple plugins if a redirect occurred. Differentiating "one
 plugin" from "many plugins" on `Plugins > Add New` requires preventing the
 redirect takeover.

 Note that by "multiple plugins", I refer to the following two scenarios:
 1. Clicking the `Activate` button in multiple plugin cards.
 2. Clicking `Activate` within the modals for each of a plugin's
 dependencies, then the `Activate` button in the dependent plugin's card.

 I've seen in some places that there's a belief that users don't install
 multiple plugins from this screen (I'm not attributing this to you
 though), which is not quite correct. It's common for a user to have
 installed an addon for say, WooCommerce, then activate it, only to receive
 a notice to go back to `Plugins > Add New` to install and activate
 WooCommerce. This is one of the scenarios that the Plugin Dependencies
 feature targeted, and so the concept of installing/activating multiple
 plugins from this screen, while not new, is more apparent now.

 The previous flow as detailed above was both frustrating and confusing to
 users (I've witnessed this a lot with clients and received emails asking
 for clarification). Even though things are different now without the
 redirect, I'm confident that we're all going to produce a more balanced
 result that will cover more use cases in a way that's straightforward for
 users.

 Regarding WP-CLI based installation/activation: This may be done as part
 of a one-click setup where the user can select a list of plugins. These
 can also often be installed and activated on existing site, depending on
 the tool used, and can use WP-CLI. I think if a configuration URL is
 provided, we should consider how we might serve this information to users
 who haven't yet loaded the WordPress admin since activation. This may be a
 single admin notice on `Plugins > Installed plugins`, or something else.
 This would likely need to some further thought and discussion, but should
 be kept in mind as we look at the various activation methods.

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