Wordpress Block Editor Fse

This gets Claude up to speed on WordPress's Full Site Editing approach, where everything from headers to footers lives as blocks instead of PHP templates. The skill covers the core pieces: theme.json for design tokens, HTML templates, reusable template parts, and the Site Editor interface. It's built for modern block themes that shipped production-ready in WP 6.2. You'll want this if you're building new WordPress sites or guiding clients who need to customize layouts without touching code. Skip it if your projects rely heavily on traditional PHP templating or your team hasn't bought into the block paradigm yet. The guidance on when FSE fits versus when it doesn't is refreshingly honest.

skills.sh installs: 474
GitHub stars: 79
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bobmatnyc/claude-mpm-skills --skill wordpress-block-editor-fse --agent claude-code

Installs into .claude/skills of the current project.

Files

WordPress Block Editor & Full Site Editing

Overview

Full Site Editing (FSE) is production-ready (since WP 6.2) and treats everything as blocks—headers, footers, templates, not just content. Block themes use HTML templates + theme.json instead of PHP files + style.css.

Key Components:

theme.json: Centralized colors, typography, spacing, layout
HTML Templates: Block-based files (index.html, single.html)
Template Parts: Reusable components (header.html, footer.html)
Block Patterns: Pre-designed block layouts
Site Editor: Visual template customization

When to Use: ✅ New themes, consistent design systems, non-technical user customization ❌ Complex server logic, team unfamiliar with blocks, heavy PHP dependencies

Full Site Editing Architecture

Block Themes vs Classic Themes

Block Themes	Classic Themes
HTML files with blocks	PHP files with template tags
theme.json + CSS	functions.php + style.css
Site Editor (visual)	Customizer (settings)
User edits templates	Limited customization