One way to build new gutenberg blocks is with log1x/acf-composer
But how would you organize your setup if you dont want to use ACF fields. Rather create new attributes in js like you do with @wordpress/create-block . I still want to use blade files.
Radicle includes an example of using a native block that’s rendered with Blade, and also an example of how to use an existing core block rendered with Blade
The WordPress core JS packages are meant to be used with a webpack build system — Sage v11 and Radicle v2 use Vite instead of webpack
1 Like
Ok thanks. Will check it out.
I see there are some recommended WordPress plugins in Radicle? These are not must have? We try to use as few plugins as possible.
Where sits logic for dynamic block, in composer file?
Are there any resources (or perhaps you could give some pointers?) about how to build native blocks in the sage 11 theme without radicle?
The only must use plugin in Radicle is an Acorn booter
It doesn’t come with a dynamic block, but yes you could use a view composer to pass data.
There’s a lot of resources for building native WordPress blocks. If you would like to see an example specific for the Roots ecosystem then consider purchasing Radicle.
2 posts were split to a new topic: Radicle modal block content and Yoast SEO