Update steps on what do to when you have theme and plugin boilerplate in the same project

[mbmjertan]

Describe your bug

We should write down / update the steps required for ensuring that no collisions happen when you have a theme and plugin boilerplate set up on the same project.

This includes:

• setting up features you need for the plugin from the boilerplate (e.g. Blocks)
• making changes to Enqueue classes so scripts and styles get enqueued properly
• adding the library config to webpack config
• changing the block namespace
• changing the block category in Blocks.php
• removing changeEditorColorPalette and add_theme_support
• making changes to filterBlocksContent
• changing the CSS variable output selector
• ensuring no classname collisions happen

There already is some documentation on this in the FAQ in Docs, but it's out of date.

Steps to Reproduce

/

Expected behavior

/

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in this repo.

Yes

Please confirm that you have searched in our documentation and couldn't find the answer.

Yes

Please confirm that your bug occurs with all plugins uninstalled and with the default WordPress theme active.

Yes