[HOLD] feat: default segments

[dkoo]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Starts the "reasonable defaults" part of the roadmap. Allows site admins to generate a set of default segments with a button click. If they've already been created and edited, clicking the button will restore the default segments to the default configuration.

The reason for requiring some kind of user action (in this case a button click) is to accommodate sites that may have been up and running with Campaigns for a while now—we don't want to automatically generate new segments which may conflict with existing segments that are running live prompts.

Closes #673.

How to test the changes in this Pull Request:

Before testing, make sure your Newspack Plugin is running Automattic/newspack-plugin#1524.

1. On a fresh or existing site, visit Newspack > Campaigns > Segments. Confirm there's a new button at the bottom of the segments list:

2. Click the button. Confirm you see a modal with a bit of explanation of what you're doing (@aschweigert: could use your help with reviewing/updating this copy):

3. Click "OK". Confirm that a set of default segments (with prefix "[Newspack]") is generated. If you already had existing segments on the site, confirm that the default segments are generated with lower priority than the existing segments.
4. Edit some of the default segment names and settings, and reshuffle the priority. Delete at least one default segment.
5. Click "Reset default segments" and click "OK". Confirm that:

• All existing segments retain their sorted priority
• The default segment(s) you edited are now reverted to their original names and settings
• The default segment(s) you deleted are restored

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[adekbadek]

The reason for requiring some kind of user action (in this case a button click) is to accommodate sites that may have been up and running with Campaigns for a while now—we don't want to automatically generate new segments which may conflict with existing segments that are running live prompts.

What if there are no segments on the site – should defaults be set up then? This would be a surprise in the "Campaigns" tab, but there would be no disruption to the existing campaigns setup. WDYT @dkoo @aschweigert ?

[dkoo]

What if there are no segments on the site – should defaults be set up then? This would be a surprise in the "Campaigns" tab, but there would be no disruption to the existing campaigns setup. WDYT @dkoo @aschweigert ?

I can get behind this. Maybe if there are no segments AND no active prompts? This would avoid creating confusion for sites that may have active prompts running for "everyone" and don't intend to use the segmentation features.

EDIT: further, we could trigger the auto-generation when you navigate to the Campaigns wizard, this way we could show a short message explaining what happened. And if a site admin never visits Campaigns, we don't need to run the extra functions.

[dkoo]

@adekbadek I pushed some changes to address your feedback. I think the auto-generation we're discussing can probably live in the main plugin if we trigger it upon rendering the Campaigns wizard.

[adekbadek]

Nit: there are extra leading spaces in the segments names:

Suggested change

	'name' => __( ' Other Readers', 'newspack-popups' ),
	'name' => __( 'Other Readers', 'newspack-popups' ),

[dkoo]

Oops, fixed in 86337ae.

[adekbadek]

Maybe if there are no segments AND no active prompts? This would avoid creating confusion for sites that may have active prompts running for "everyone" and don't intend to use the segmentation features.

Adding the default segments won't disrupt their prompt delivery in any way, and I think the user should be encouraged to make use of segmentation. So I'd say the defaults should be created if there are no segments, regardless of whether there are prompts.

we could trigger the auto-generation when you navigate to the Campaigns wizard, this way we could show a short message explaining what happened. And if a site admin never visits Campaigns, we don't need to run the extra functions.

Seems to me it'd be simpler to create the default segments on WP initialisation, without the extra API call. But it's not a strong opinion.

[dkoo]

a315d73 implements the auto-generation if the site doesn't have any segments.

[dkoo]

Note to @thomasguillot: after some discussion we've decided we'd like to build this out into a more guided onboarding/wizard experience to guide users toward one of several sets of default segments, based on their input. @aschweigert will work on a suggested flow for this, but let's hold these changes until we can flesh that out a bit more.

[adekbadek]

Approving in the current state – as noted above it's likely to change, though.

[dkoo]

After some internal discussion we're going to be moving in a different direction for this. I'm going to close this for now—we can reopen if we change our minds about wanting to release it as an interim step.