Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

My Jetpack: replace Creator card with Newsletter #38418

Open
wants to merge 11 commits into
base: trunk
Choose a base branch
from

Conversation

IanRamosC
Copy link
Contributor

@IanRamosC IanRamosC commented Jul 19, 2024

More context: p1HpG7-sYs-p2

Proposed changes:

  • This PR adds a new card for Newsletter and replaces Creator with it. The CTA in the card links to the Newsletter settings page

Not connected:

image

User connected with settings off:

image

User connected with settings on:

image

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

p1HpG7-sYs-p2

Does this pull request change what data or activity we track or use?

No

Testing instructions:

  • Spin up a JN site with Jetpack Beta pointing to this branch
  • Go to My Jetpack and confirm that you see "Newsletter" instead of "Creator"
  • The button in the card will always link to the settings page on the Newsletter menu
    • If the user is not connected to Jetpack, that will redirect to the User connection screen
    • If the user is connected, you'll see the Newsletter section on the Settings page.
  • After turning the settings on, if you go back to My Jetpack, you'll see the card marked as Active

Copy link
Contributor

github-actions bot commented Jul 19, 2024

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the add/newsletter-card branch.

  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack add/newsletter-card
    

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

Copy link
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

@IanRamosC IanRamosC force-pushed the add/newsletter-card branch from f31d695 to 0896c03 Compare July 19, 2024 02:31
@IanRamosC IanRamosC self-assigned this Jul 21, 2024
@IanRamosC IanRamosC changed the title Add/newsletter card My Jetpack: replace Creator card with Newsletter Jul 21, 2024
@IanRamosC IanRamosC marked this pull request as ready for review July 21, 2024 14:55
@crisbusquets crisbusquets self-assigned this Jul 22, 2024
Copy link
Contributor

@CodeyGuyDylan CodeyGuyDylan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested mostly well, I left a few comments that i think are important enough to address or talk about before merging 😄

label: __( 'View', 'jetpack-my-jetpack' ),
onClick: () => {},
},
[ PRODUCT_STATUSES.MODULE_DISABLED ]: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this PR we've gone towards allowing the user to "Activate" the module/plugin from My Jetpack if at all possible. Could we possibly continue that trend here? Would the activate function work here or is there a reason we need to have the user do it from the settings page?

type DisplayItemType = Record<
// We don't have a card for Security or Extras, and scan is displayed as protect.
Exclude< JetpackModule, 'extras' | 'scan' | 'security' >,
Exclude< JetpackModule, ExcludedModules >,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvements with the excludes, thanks!

@@ -0,0 +1,36 @@
import { __ } from '@wordpress/i18n';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is a brand new file, what do you think about converting it to TypeScript since we are heading that direction in My Jetpack?

if ( Products::STATUS_MODULE_DISABLED === $status && ! Initializer::is_registered() ) {
// If the site has never been connected before, show the "Learn more" CTA.
// It should point to the settings page where the user can manage Newsletter
$status = Products::STATUS_NEEDS_PURCHASE_OR_FREE;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This status has been replaced with STATUS_NEEDS_ACTIVATION in the PR I linked to in a previous comment FYI, you might want to rebase and update that so there are no issues with an undefined constant 😄

@crisbusquets
Copy link
Contributor

Just a note that we also need to update the emails we send when the user upgrades:

Screenshot 2024-08-07 at 18 27 16

Should I create a new issue for this, @IanRamosC ?

@pkuliga
Copy link
Contributor

pkuliga commented Sep 4, 2024

Hi @IanRamosC, I just came across this and I'm wondering, what is the status of this work?

Are we giving up on it or still want to move it forward?

@crisbusquets
Copy link
Contributor

Paused until Nov.
Context: p1726211355297409-slack-C02LK1W8T4Z.

Copy link
Contributor

This PR has been marked as stale. This happened because:

  • It has been inactive for the past 3 months.
  • It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, etc.

If this PR is still useful, please do a [trunk merge or rebase](https://github.com/Automattic/jetpack/blob/trunk/docs/git-workflow.md#keeping-your-branch-up-to-date) and otherwise make sure it's up to date and has clear testing instructions. You may also want to ping possible reviewers in case they've forgotten about it. Please close this PR if you think it's not valid anymore — if you do, please add a brief explanation.

If the PR is not updated (or at least commented on) in another month, it will be automatically closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants