WordPress & Gutenberg FAQ

Yes. 4WP Bundle exposes 4wp/v1 REST endpoints; MCP Abilities connects AI agents to WordPress via the Abilities API — both with public source on GitHub.

Yes, under GPL v2+. Fork, adapt, and ship — respect the license and attribution. Many patterns (block wrappers, REST controllers, inventory tables) are reusable starting points for commercial work.

Yes — block.json, InnerBlocks, block variations, Interactivity API, block bindings, Query Loop extensions, and editor sidebar plugins appear across the suite (FAQ, Advanced Code, QL Blocks, SEO Helper, MCP Abilities).

Study plugin singles under /plugin/, clone repos, and follow guides on hooks, blocks, inner blocks, Interactivity API, and block bindings. Each plugin is a case study — not a toy demo.

Content is anchored in shipped plugins — real settings screens, edge cases, release history, and SEO/GSC workflows. You learn from code that runs in production, not isolated snippets.

Yes. These plugins power 4wp.dev and client projects. Expect Composer autoloading, namespaced PHP, block.json blocks, PHPUnit where applicable, and documented architecture in the Development section.

SOLID principles, OOP, MVC, Domain-Driven Design, and software design methodologies — mapped to WordPress plugin structure with examples from the 4WP codebase in Architectures.

Production-grade patterns for Gutenberg blocks, plugin architecture (SOLID, REST API, settings screens), SEO workflows, MCP abilities, and real release pipelines — all from maintained open-source code you can read and fork.

Typically PHP 8.0+ and WordPress 6.0+. Check each plugin header on GitHub or the plugin page for exact minimums before adopting patterns in your stack.