👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jasmussen! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

I swear I've seen you before around these parts!

As an alternative to having a top-level "Deprecated" folder, what about having "Deprecated" folders nested into related pacakge folder?

Ie. "Components" > "Deprecated"

Ie. "Components" > "Deprecated"

I like that better, actually. I'll take a look.

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @[email protected].

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: [email protected].

Co-authored-by: mirka <[email protected]>
Co-authored-by: ciampo <[email protected]>
Co-authored-by: jasmussen <[email protected]>
Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: jameskoster <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: 0 B

Total Size: 6.89 MB

_{compressed-size-action}

Flaky tests detected in 99ee379.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/22957721915
📝 Reported issues:

• [Flaky Test] Custom Completer: should allow newlines after multiple option completions #48535 in /test/e2e/specs/editor/various/autocomplete-and-mentions.spec.js
• [Flaky Test] Custom Completer: should allow option selection via click event #76262 in /test/e2e/specs/editor/various/autocomplete-and-mentions.spec.js
• [Flaky Test] User Mention: should allow newlines after multiple mention completions #48537 in /test/e2e/specs/editor/various/autocomplete-and-mentions.spec.js

@jasmussen, you can't seem to escape the "First-time Contributor" label 😄

P.S. I like the new label.

you can't seem to escape the "First-time Contributor" label 😄

Indeed. Part of this is perhaps a recent laptop switch. The most recent thing I've tried is disconnecting and reconnecting GH to WP.org, we'll see if the label is gone on new PRs. For now I'll live with the curse.

P.S. I like the new label.

Thanks. Do you prefer a single top level deprecated one? Or subfolders like Marco proposed?

I personally like the single top-level, as it's easy to scan what's deprecated. But subfolders give it a better structure.

I guess the final decision depends on how we want to structure the Storybook.

I feel like it's worth making a decision on in this PR, so I'd love thoughts by @ciampo before we land this, because either way, permalinks will change, which is something we should ideally minimise. I don't feel strongly, but if I had to choose, I'd prefer the subfolders idea rather than the top level folder, mostly to focus on what you should use rather than what you shouldn't.

+1 to subfolders. It's probably helpful to understand which package the component was deprecated from, and a top level 'Deprecated' item feels too prominent.

Fantastic, thanks so much! I'll also merge this one when the checks pass.