Writing prompts: move block to production and use for answering prompts

[creativecoder]

Proposed changes:

• Moves writing prompt block to production
• Uses block when starting a new post using and ?answer_prompt={prompt_id} query param

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

PT: pe7F0s-uo-p2

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

No.

Testing instructions:

• Ensure your test site is connected to WP.com
• Enable experimental blocks (define( 'JETPACK_EXPERIMENTAL_BLOCKS', true );)
• Sandbox public-api and apply these changes to your wpcom sandbox with bin/jetpack-downloader test jetpack update/answer-prompt-w-block (if not, the block header and footer will be empy, but is works, otherwise)
• Start a new post answering a specific prompt id, like /wp-admin/post-new.php?answer_prompt=1810
• You should see a prompt inserted into the post content
• The tags dailyprompt and dailyprompt-{prompt_id} should be added to the post
• The post meta _jetpack_blogging_prompt_key should be added to the post, with the prompt id

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack update/answer-prompt-w-block

to get started. More details: p9dueE-5Nn-p2

[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.
  
• ⚠️ All commits were linted before commit.
  
• ✅ 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 (other than "Required review") 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 you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

---

Jetpack plugin:

• Next scheduled release: April 4, 2023.
• Scheduled code freeze: March 28, 2023.

[jeherve]

Would we consider making it a production block, so self-hosted sites can use it too? It seems like a useful block!

[creativecoder]

I'm open to that--I don't see why it can't be a production block assuming we can get the appropriate jetpack.com doc pages set up.

[jeherve]

I think that's something Quill can help us with. I created 1200427382410585-as-1204188078771387/f to open a request with the team.

[creativecoder]

I believe this PR is ready to go, but I want to get the remaining Writing Prompt block PRs merged before this one:

• Writing prompts block: load prompts when user not connected to WP.com #29432
• Writing prompt block: add spacing support #29501

[samiff]

Sandbox public-api and apply these changes to your wpcom sandbox with bin/jetpack-downloader test jetpack update/answer-prompt-w-block (if not, the block header and footer will be empy, but is works, otherwise)

Could just be config on my end, but I wasn't able to get the the header/footer to display correctly on my local dev site. Looked good on my test wpcom site though.

When no explicit promptId is supplied, does it just grab an ID specified server side?

[creativecoder]

Could just be config on my end, but I wasn't able to get the the header/footer to display correctly on my local dev site.

That's probably caused by the changes from https://github.com/Automattic/jetpack/pull/29450/files not being available for whatever reason (not applied to sandbox, API not using sandbox, etc).

When no explicit promptId is supplied, does it just grab an ID specified server side?

Correct, it gets the prompt specified for the day (we currently have a unique prompt for every day of the year).

Addressed.

[creativecoder]

I rebased this to get the TeamCity build to pass--will need another approval.