wp-block-development

Standardize WordPress Gutenberg block creation, registration, and testing workflows.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wp-block-development-javiercasares
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-block-development
Source: https://github.com/javiercasares/cloudfest-wporgdownload/tree/main/.claude/skills/wp-block-development
Command: npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wp-block-development-javiercasares

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WordPress Gutenberg block development is complex, requiring consistent metadata handling, registration, API versioning, and build tooling. This Skill consolidates guidance and workflows to reduce setup friction, ensure compatibility, and prevent common pitfalls.

Core Features & Use Cases

  • Comprehensive guidance for block.json usage, apiVersion 3 migration, deprecations, and dynamic rendering.
  • Step-by-step workflows for creating, updating, registering, and testing blocks in plugins/themes/sites.
  • Clear examples and checks to maintain compatibility with WordPress 6.9+ and modern tooling.

Quick Start

Follow the recommended scaffolding flow, register blocks via metadata, ensure apiVersion 3, and configure render mappings and necessary build/test tooling.

Frequently Asked Questions about wp-block-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a WordPress Gutenberg block using block.json metadata?

Migrate WordPress Gutenberg blocks to apiVersion 3 by updating block.json metadata, adjusting render callbacks, and implementing deprecation workflows. This ensures compatibility with WordPress 6.9+ while maintaining existing block structures.

What is the standard workflow for registering a Gutenberg block in a plugin?

Dynamic rendering in Gutenberg blocks uses block.json metadata and PHP render callbacks instead of static save functions. This approach generates content server-side, ensuring block output stays synchronized with WordPress data.

Do I need apiVersion 3 for WordPress block development?

Use register_block_type_from_metadata in PHP to register Gutenberg blocks by pointing to the block.json directory path. This handles asset enqueuing and render mappings automatically based on the metadata defined.

Why does my Gutenberg block throw deprecation errors during updates?

Gutenberg block deprecation errors occur when block.json metadata or save logic changes without proper deprecation workflows. Define deprecated block configurations and update apiVersion 3 settings to maintain rendering compatibility.