Docs: Add error message guidance.

[jasmussen]

What?

Related to #81123 but also Defensive Data Design. Adds Storybook docs on how to write good error messages.

This is a first draft, I expect improvements in the future.

Testing Instructions

npm run storybook:dev

Use of AI Tools

Yes.

[ramonjd]

just left some non-blocking observations... thanks!

[ramonjd]

docs/contributors/documentation/copy-guide.md already has a section titled "Error Messaging". Is story book separate or should it be canonical?

If the preference is to link off to the official GB docs, then I think there's scope to give principles 1–5 a hair cut then add the link off to docs/contributors/documentation/copy-guide.md

What do you think?

[jasmussen]

Good question. Storybook is contextual to the design system in a way that those more formal docs are not, and more easy to maintain. I'd prefer keeping most of it here. For now I'll add a link.

[github-actions]

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.

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

Co-authored-by: jasmussen <joen@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>

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

[jasmussen]

Thanks for all the feedback, agree with all of it. Just connecting a dot to a comment here: #81195 (comment)

[jasmussen]

Solid feedback, addressed all of it.

[ramonjd]

LGTM

Thanks for the changes. I just pushed a small commit that escapes curly braces, the power of which took down the storybook build!! 💣

[jasmussen]

Thanks for the help here!