Blockwright — beta

== Description ==

Blockwright writes a block into your theme and then gets out of the way. You describe the block in a short admin form — name, attributes, whether it renders in PHP or in JavaScript — and it writes block.json, the edit component, the save component, and the registration call into a folder you choose.

The output is code you would have written. There is no runtime dependency, no abstraction layer, and no blockwright_render() anywhere in it. Uninstall the plugin and every block it generated keeps working, because nothing it generated refers back to it.

This is beta because the API for custom controls will change before 1.0. Blocks you generate today will keep working; the form you generate them from will not look the same.

== Screenshots ==

Numbered the way they ship in /assets/. Click any one to see it full width.

01

02

03

04

05

06

== Installation ==

• Install and activate the plugin.
• Go to Tools → Blockwright and describe the block you want.
• Choose a destination folder inside your theme or your own plugin.
• Read the generated files before you ship them. That is the point.

Requires a writable destination folder. It will tell you if it does not have one.

== Frequently asked questions ==

Why is it still beta?

The control API is not settled. Everything else is; the generated output has been stable since 0.7.

Does it modify files it did not create?

Only one: it appends a single register_block_type() call to your theme’s functions file, and it tells you before it does.

Can it generate dynamic blocks?

Yes. Pick PHP rendering and it writes the render callback and the template alongside the editor code.

== Changelog ==