orbit-gutenberg-devlisted

# 🪐 orbit-gutenberg-dev — Block development audit The reviewer for "is this block plugin set up the way modern WP expects?" Read every block.json + render.php + edit.js, audit against the current Block Editor Handbook. --- ## Quick start ```bash claude "/orbit-gutenberg-dev Audit ~/plugins/my-plugin's blocks for current best practices." ``` Output: `reports/gutenberg-dev-<timestamp>.md`. --- ## What it checks (whitepaper intent) ### 1. apiVersion is current (3 as of WP 6.5+) **Why:** apiVersion 3 lets blocks use `viewScriptModule` for native ES modules and the Interactivity API. apiVersion 2 still works but is legacy. apiVersion 1 throws warnings in WP 6.5+. ```json { "apiVersion": 3, "name": "my-plugin/example" } ``` **Source:** [Block API Versions](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/) ### 2. Server-side render preferred over JS save() **Why:** Server-side render (`render: "file:./render.php"`) ships less JS, allows dynamic content, and survives content migrations. The old approach (defining `save()` in JS) freezes content into the post and breaks if you change the markup. ```json { "render": "file:./render.php" } ``` ```php // render.php <div <?php echo get_block_wrapper_attributes(); ?>> <?php echo esc_html( $attributes['title'] ?? '' ); ?> </div> ``` **Source:** [Dynamic blocks](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/#render) ### 3. block.json `suppo