A Deep Introduction to WordPress Block Themes

Since its 2018 debut, the WordPress Block Editor (Gutenberg) has revolutionized website creation. While usable with any theme supporting its CSS, Block Themes represent a significant advancement. These themes leverage the Block Editor for complete site construction, shifting the theme's role from content control to design guidance. This approach, known as Full-Site Editing (FSE), empowers users to build entire sites using blocks.

Let's explore this transformative technology.

Table of Contents

• Introduction
• Key Terminology
• Block Editor with Classic Themes
• Understanding Block Themes
• Building Block Themes
• Global Styles and theme.json
• Block Theme Development Strategies
• Real-World Block Theme Examples
• Creating Block Child Themes
• Personal Reflections
• Resources

Introduction

While the Block Editor's evolution is largely visible to users, its underlying development on GitHub is constantly progressing. My own journey involved using both the classic and block editors, even venturing into headless WordPress with Gatsby and Frontity before returning to the core platform.

Initially intrigued by the experimental block-based themes on GitHub, I recently began actively exploring them, even implementing one on a personal project. WordPress 5.9 ("Joséphine") marked a pivotal moment, bringing full-site editing and Block Themes to the forefront. While iterative features existed previously, this release is a game-changer. This article shares my hands-on learning experience and personal observations.

Disclaimer: I'm not a Block Theme expert, but a seasoned WordPress user. My aim isn't to critique WordPress 5.9 but to offer an open-minded learner's perspective based on practical experience with the Block Editor.

Key Terminology

Before delving into Block Themes, let's clarify essential terms:

Block Editor

This refers to the WordPress Editor, aptly named due to its block-based structure. Each element (text, images, videos, etc.) is a block, enabling modular page layouts. This contrasts with the "classic" editor's predefined layout approach. The Block Editor integrates content and layout editing within a single interface.

Block Theme

As defined by WordPress documentation, a Block Theme uses blocks to construct all site templates (headers, footers, sidebars, etc.), extending the Block Editor's reach beyond post content. Unlike classic themes relying on PHP templates, Block Themes utilize block-based HTML templates, styled and arranged via the Site Editor and theme.json.

Site Editor

The Site Editor (often referred to as Full-Site Editing or FSE) is the central tool for creating and managing block-based templates. It allows editing various templates, template parts, and styling options within a cohesive interface. This replaces traditional PHP template-based theme development with a visual, block-based approach.

The official WordPress Glossary provides further definitions.

Block Editor with Classic Themes

The Block Editor works with both classic and Block Themes. The classic editor (via the Classic Editor plugin) remains available, offering backward compatibility. The gradual introduction of the Block Editor, initially via the Gutenberg plugin and later integrated into WordPress Core, paved the way for FSE.

Understanding Block Themes

Experimental Block Themes have been under development since early 2020. The GitHub theme experiment repository showcases various approaches. Twenty Twenty-One was a significant step, integrating block styles and patterns. Many themes now include block editor patterns and styles.

Block Theme File Structure

Block Themes differ significantly from classic themes. While classic themes rely on PHP and JavaScript for markup, Block Themes leverage the core's markup and basic styling. A simple Block Theme might include index.php, style.css, theme.json, templates/index.html, and parts folders for reusable components.

Templates and Template Parts

Templates are groups of blocks, often incorporating reusable "template parts" (e.g., headers, footers). These are assembled to create page layouts.

Building Block Themes

The Site Editor is the primary tool for designing WordPress websites. It replaces the Customizer for many theme customization tasks.

The WordPress Site Editor Interface

The Site Editor, accessed via Appearance → Editor, provides a familiar block-based interface but with expanded capabilities for managing site-wide templates. It features sections for Site, Templates, and Template Parts, enabling global design adjustments. Customizations can be easily cleared using the kebob menu.

Creating Templates and Template Parts

Templates are created and managed within the Site Editor, eliminating the need for manual PHP file creation. The Block Editor Handbook details methods for creating templates and template parts, including manual HTML creation and using the Site Editor's interface.

Global Styles and theme.json

In Block Themes, styling is managed through the theme.json file, offering granular control over styles from various sources. This file allows theme authors to define default styles, manage user customization options, and set editor defaults. It provides a centralized approach to styling, improving maintainability.

Block Theme Development Strategies

Several strategies are emerging for Block Theme development:

Universal Themes

Blockbase, a universal theme from Automattic, serves as a starting point similar to the Underscores theme, providing a foundation for child theme development.

Default Themes (e.g., Twenty Twenty-Two)

Twenty Twenty-Two is an excellent example of a theme designed for FSE, showcasing the capabilities of Block Themes.

Hybrid Themes

Hybrid themes blend traditional and FSE approaches, utilizing theme.json for styling and potentially incorporating block templates.

Community Themes

The WordPress theme directory offers a growing selection of community-created Block Themes, demonstrating diverse approaches.

Real-World Block Theme Examples

Numerous websites are already using Block Themes, showcasing their versatility.

Creating Block Child Themes

Child theming remains relevant for Block Themes, though approaches are still evolving.

Create Blockbase Theme Plugin

Automattic's "Create Blockbase Theme" plugin simplifies child theme creation for Blockbase themes.

Using Alternate theme.json Files

Swapping theme.json files can drastically alter a Block Theme's appearance. Tools are emerging to simplify this process for non-coders.

Personal Reflections

My experience highlights several key aspects:

Addressing Jamstack Criticisms

Block Themes address Jamstack criticisms regarding bloated WordPress themes by offering lightweight, markup-focused structures.

Missing the Customizer

The loss of the Customizer's code injection capabilities requires adapting to the Site Editor's interface.

Simplified Customizations

Customizing Block Themes is significantly easier than with classic themes, even for non-developers.

Lowering Barriers to Entry

Block Themes simplify theme development, focusing more on content and patterns.

Resources

Numerous resources are available for learning more about Block Themes and FSE. This includes official WordPress documentation, tutorials, and blog posts from various sources.

The Site Editor, while still evolving, offers exciting possibilities. I'm actively exploring Block Themes and look forward to future developments. Share your experiences and feedback!

The above is the detailed content of A Deep Introduction to WordPress Block Themes. For more information, please follow other related articles on the PHP Chinese website!