You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ryanwelcher After you're recent stream on creating a custom @wordpress/create-block template for integrating Tailwind CSS into blocks I'd like to explore contributing to this package (and also Gutenberg in general).
However, as I'm not that experienced with GitHub the whole process of contributing from opening an issue to submitting a PR is a little intimidating. e.g. Setting up tests etc.
Perhaps this would make an interesting topic for a stream to run through the process from start to finish.
A good example to focus on would be adding support for dev dependencies in package.json via a custom template. Right now (as you know) we can only use npmDependencies which is a little restrictive.
Another idea for extending the create-block package is to be able to specify a block name. Right now the block name is just based on the plugin slug name. Being able to specify a block name that's different to the plugin name would be very useful.
The text was updated successfully, but these errors were encountered:
@ryanwelcher After you're recent stream on creating a custom
@wordpress/create-block
template for integrating Tailwind CSS into blocks I'd like to explore contributing to this package (and also Gutenberg in general).However, as I'm not that experienced with GitHub the whole process of contributing from opening an issue to submitting a PR is a little intimidating. e.g. Setting up tests etc.
Perhaps this would make an interesting topic for a stream to run through the process from start to finish.
A good example to focus on would be adding support for dev dependencies in
package.json
via a custom template. Right now (as you know) we can only usenpmDependencies
which is a little restrictive.Another idea for extending the create-block package is to be able to specify a block name. Right now the block name is just based on the plugin slug name. Being able to specify a block name that's different to the plugin name would be very useful.
The text was updated successfully, but these errors were encountered: