wordpress-block-editor-fse

To build a WordPress block theme, define global styles using theme.json and structure site layouts with HTML templates instead of traditional PHP files. This enables Full Site Editing capabilities, allowing visual customization of headers, footers, and templates directly within the Site Editor.

Creating custom Gutenberg blocks involves defining block metadata in block.json and handling rendering through either server-side PHP or client-side React. This approach ensures blocks are reusable and properly integrated with the WordPress Block Editor.

React is required for client-side rendering of custom blocks in Full Site Editing, but server-side rendering can be handled entirely with PHP. The Skill supports both approaches, allowing developers to choose based on their block's interactivity requirements.

Yes, you can use @wordpress/scripts and wp-env to establish development workflows for block themes. These tools provide the build processes and local environment configuration needed to develop and test custom blocks and Full Site Editing features efficiently.

Full Site Editing replaces traditional PHP template files with HTML templates and theme.json configuration for design tokens. This shift enables a component-based development approach, allowing users to visually edit theme-wide elements like headers and footers using blocks.

While theme.json provides comprehensive control over global styles and design tokens, complex dynamic styling logic still requires custom CSS or PHP. It standardizes color, typography, and spacing configurations but does not replace all conditional formatting scenarios.