jetpack Blocks: introduce new pattern to demonstrate some of our blocks

Fixes #35539

Proposed changes:

This commit introduces 3 things:

A new directory and loading mechanism allowing us to add more patterns in the future.
A new Pattern category, "Jetpack".
A first pattern of a group of 3 Jetpack blocks: a sharing buttons block, a Like Block, and a Related Posts block.

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

N/A

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

No

Testing instructions:

[!NOTE] This is better tested on a site where you have some published posts already, so related posts can appear.

Go to Appearance > Themes and activate a block-based theme like Twenty Twenty Four.
Go to Appearance > Site Editor > Templates > Single Posts
Add a pattern below the post content
- Select the new pattern from the new "Jetpack" category.

Feb 23 '24 15:02 jeherve

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/pattern-one branch.
To test on Simple, run the following command on your sandbox:
```
bin/jetpack-downloader test jetpack add/pattern-one
```

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

Feb 23 '24 15:02 github-actions[bot]

Thank you for your PR!

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

:white_check_mark: Include a description of your PR changes.
:white_check_mark: Add a "[Status]" label (In Progress, Needs Team Review, ...).
:white_check_mark: Add testing instructions.
:white_check_mark: Specify whether this PR includes any changes to data or privacy.
:white_check_mark: 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 :robot:

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.

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

WordPress.com Simple releases happen daily.
WoA releases happen weekly.
Releases to self-hosted sites happen monthly. The next release is scheduled for March 5, 2024 (scheduled code freeze on March 4, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Feb 23 '24 15:02 github-actions[bot]

@keoshi I'd like to have your input on this. I think such a pattern would make sense as a way to demonstrate and introduce some of our blocks. I had thought of adding the Subscribe block to that first pattern, but ended up limiting it to sharing+like+related posts for now.

What's your take on this? How should that first pattern look like? How would you design it?

Thank you!

Feb 23 '24 15:02 jeherve

Thanks for the ping, @jeherve and sorry for the delay (was at the Design meetup).

I can't express how much I love this. Offering pre-packaged patterns that surface the best features that Jetpack has to offer is, I think, one of the best ways we can surface the value of the product. Love it.

As for the design, I would perhaps align the titles to make sure they are flush at the top. Really like the combo of Share + Like and it creates a neat group. For the Related posts, the links feels a bit further apart from each other than they should, but it's a minor thing.

One of the things we talked about at the meetup was to have a monthly challenge where each designer would create a couple of blocks to our ever-growing selection. Maybe we can use that to double down on the strategy you kickstarted here!

Mar 04 '24 17:03 keoshi

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.

Jun 04 '24 00:06 github-actions[bot]

This PR has been automatically closed as it has not been updated in some time. If you want to resume work on the PR, feel free to restore the branch and reopen the PR.

Jul 05 '24 00:07 github-actions[bot]