Launchpad: "first_post_published" task links to first post if you have one

[renancarvalho]

Fixes Automattic/wp-calypso#94086

Proposed changes:

Some flows allow the user to start writing before they reach the Launchpad, if that is the case, users can have a Draft post when they arrive at the Launchpad. As reported in Automattic/wp-calypso#94086, the user can find themselves in an onboarding flow loop: they draft a first post, head back to the launchpad, click "write your first post", draft a new post, head back to the launchpad, etc. etc.
The user should be more successful completing the task if they don't end up in a loop.

This PR adds checks on the Launchpad API and to return the correct task URL:

• Links to either an existing draft or an empty editor
• Links to either wp-admin or Calypso editors depending on flow and site options
• Returns different copy depending on whether an existing draft exists.

This PR works in concert with Automattic/wp-calypso#94259 which updates the client logic so that it respects the URL returned by the server. That's why extra logic for start-writing and design-first flows have been added to the server, because it replicates logic that used to be present in Calypso.

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

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

No

Testing instructions:

The same testing instructions as the Calypso PR Automattic/wp-calypso#94259 replicated below for convenience.

Extra things to test for this PR are to using logging or some other mechanism to confirm the caching in the new wpcom_launchpad_get_latest_draft_id function works as expected.

* Add the Jetpack changes to your sandbox * Sandbox `public-api` * Run `bin/jetpack-downloader test jetpack-mu-wpcom-plugin feat/launchpad_draft_post` * See PCYsg-Osp-p2 for more details * Build Calypso changes locally * Test `write` flow with a draft post * Create new site using `/start` * When asked about goals choose **Write & Publish** * Continue on flow and choose **Draft your first post: Start writing** button * Confirm the suggested writing ideas modal appears when the editor loads * This is controlled by the `new_prompt=true` query param * Save your post as draft but *do not publish* * Preview the draft in a new tab * In the new tab click **Next steps** * You are taken to launchpad, at this point you'll need to change the page domain back to `calypso.localhost:3000` * Confirm the **Continue to write your first post** button links back to the editor * It should re-open your existing post * It should use the Calypso editor * There is no `new_prompt` modal when the editor loads * Now test in `wp-admin` mode * Jump straight to `/settings/general/{{ site slug }}` and change the admin interface to **classic** * Click **My Home** in the sidebar to get redirected to the launchpad (confirm your still looking at `calypso.localhost:3000`) * Confirm the **Continue to write your first post** button links back to the editor * It should re-open your existing post * It should use the`wp-admin` editor * There is no `new_prompt` modal when the editor loads * Test `write` flow with no draft post in Calypso site * Create new site using `/start` * When asked about goals choose **Write & Publish** * Continue on flow and choose **Draft your first post: Start writing** button * Confirm the suggested writing ideas modal appears when the editor loads * This is controlled by the `new_prompt=true` query param * *do not save a draft*, leave the editor with the (W) button * You are taken to launchpad, at this point you'll need to change the page domain back to `calypso.localhost:3000` * Confirm the **Write your first post** button links back to the editor * It opens a blank editor * It should use the Calypso editor * This is a `new_prompt` modal when the editor loads (they might have accidentally dropped out of the flow earlier so I think it's reasonable to show it to them here) * Now test in `wp-admin` mode * Jump straight to `/settings/general/{{ site slug }}` and change the admin interface to **classic** * Click **My Home** in the sidebar to get redirected to the launchpad (confirm your still looking at `calypso.localhost:3000`) * Confirm the **Continue to write your first post** button links back to the editor * It should open a blank editor * It should use the`wp-admin` editor * There is a `new_prompt` modal when the editor loads * Test `start-writing` or `design-first` flow * Create a new site using `/setup/start-writing` * You are eventually taken to the launchpad * Confirm the **Write your first post** button links to the editor * It should open a blank editor * It should use the `wp-admin` editor (remember these flows are special cased to use `wp-admin`) * There is no `new_prompt` modal * An `origin` query param has been added * Save and preview a draft post * In the new tab click **Next steps** * Back in the launchpad (confirm you're on `calypso.localhost:3000`) check the **Continue to write your first post** button * It should open the existing draft * It should use the `wp-admin` editor (remember these flows are special cased to use `wp-admin`) * There is no `new_prompt` modal * An `origin` query param has been added

[github-actions]

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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions]

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 feat/launchpad_draft_post branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

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

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin feat/launchpad_draft_post
  

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

[arthur791004]

Tested and it works as expected. I can the copy of the task changes to "Continue to write your first post" and it links to my draft correctly