Add clarification about importing css/scss files

[colorful-tones]

What?

Additional clarification in Block Editor Handbook / How-to Guides / Blocks / Use styles and stylesheets to remind folks that they will need to import './editor.scss' in their edit.js, etc.

I've forgotten and missed this rather obvious detail a few times. Also, I requested clarification on this yesterday, which inspired the follow up PR: #54491 (comment)

Why?

Trying to empower folks to understand and use standard approaches.

How?

Clarification in documentation

Preview changes here: https://github.com/WordPress/gutenberg/pull/61252/files#diff-5fa0fb78d92f47c4d5770f668b186c3c3ea593e5fdb2d2b2a8ce3d2f2c775c03

[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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @ALJ.

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: ALJ.

Co-authored-by: colorful-tones <[email protected]>
Co-authored-by: fabiankaegy <[email protected]>
Co-authored-by: juanmaguitar <[email protected]>
Co-authored-by: luminuu <[email protected]>

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

[luminuu]

Here's the issue that @juanmaguitar added based on my feedback in Slack recently, covering this topic: #61092

[juanmaguitar]

@colorful-tones there seems to be an issue with some tests that shouldn't be affected by this PR.
could you run the tests again to check if this unblocks the merge of this PR?

[colorful-tones]

It has been a while and already struggling with how to contribute to docs. We really need to improve docs for new contributors and even existing! I can't remember what I had for lunch yesterday, and unless you're contributing docs every day then you're really gonna struggle.

Steps so far:

• Looking here: https://developer.wordpress.org/block-editor/contributors/documentation/ ... nothing on the npm commands necessary to run tests or update docs after making changes. 😢
• My next stop: package.json to try and reverse-engineer what one might want to try and do. 🤞

[colorful-tones]

Guess I was overthinking it. (hint: I always do 😉 ).

[juanmaguitar]

Thanks @colorful-tones!

could you run the tests again to check if this unblocks the merge of this PR?

I should have clarified that I meant the tests are launched automatically on each PR as part of the Continuous Integration processes.
Sometimes tests fail in PR, and most of the time the issue is solved by running the tests again, which can be done from PR GitHub UI without any code changes.

PS: I see you already successfully managed that, but I wanted to leave this explanation here for further reference.