Multi-part learning paths
Curated sequences — work through them in order, end with a complete project.
A developer's field guide to WordPress 7.1 — client-side media processing, Abilities API upgrades, the always-iframed editor, SVG Icon API, global styles, and a compatibility checklist.
A complete developer's guide to WordPress 7.0 — native AI, the modernized dashboard, new blocks and design tools, the new developer APIs, and every breaking change you need to fix.
Learn how to build custom blocks, extend the editor, and create powerful WordPress experiences with Gutenberg.
Practical, hands-on tutorials to help you learn by doing. New tutorials added regularly.
Step by
step.
Looking for depth?
Guides are single-page deep dives on one topic each — reference + explanation combined. Start with The WordPress Abilities API.
A WordPress 7.1 compatibility checklist: iframed editor, client-side media hooks, Abilities public flag, jQuery UI 1.14.2, plus features that did not ship (React 19, collaboration).
WordPress 7.1 field guide for developers: client-side media, Abilities API, always-iframed editor, SVG Icon API, global styles, and what to test before users upgrade.
WordPress 7.1 upgrades the Abilities API: a unified public flag, wp_get_abilities() filtering, execution lifecycle hooks, JSON Schema for clients, and typed REST input.
WordPress 7.1 processes images in the browser with wasm-vips — compression, thumbnails, HEIC, AVIF, GIF-to-video — plus REST sideload, finalize, and plugin hook compatibility.
WordPress 7.1 always iframes the post editor, adds background.gradient and min-width block supports, expands DataViews, and keeps the admin toolbar in the editor.
WordPress 7.1 expands Global Styles (responsive variations, viewports, text-shadow, pseudo states), ships a public SVG Icon API, and adds Design System theming tokens.
A step-by-step compatibility process for shipping a WordPress 7.0-ready release — set up a test site, audit your blocks, fix the breaking changes, and ship with confidence.
WordPress 7.0 enforces the iframed editor, broadens contentOnly mode, and drops PHP 7.3. Here are the breaking changes block and plugin developers must fix before users upgrade.
The headline feature of WordPress 7.0 is native AI in Core. Here is what the WP AI Client, the Abilities API, and the Connectors system actually mean for plugin developers.
WordPress 7.0 overhauls wp-admin — a new Modern color scheme, view transitions, a command palette, a dedicated font library, and visual revisions. A tour of every dashboard change.
WordPress 7.0 adds block-level custom CSS, new Headings and Breadcrumbs blocks, a Gallery lightbox, and expanded dimensions controls. A tour of the new design tools.
PHP-only block registration, the Interactivity API's new watch() function, DataViews and DataForms, Block Bindings iterations — the new developer APIs in WordPress 7.0.
Master the attribute system — types, sources, defaults, and how block data round-trips between the editor, the database, and the front-end.
Register reusable block compositions — landing-page hero, feature grid, FAQ section — that users insert as a complete unit.
Package your block as a proper WordPress plugin — file structure, asset enqueueing, server-side render callbacks, plugin metadata.
Use JavaScript hooks (editor.BlockEdit, blocks.registerBlockType, blocks.getSaveContent.extraProps) to extend core blocks without forking them.
Add visual styles (boxed / filled / outlined) and block variations (Tip / Warning / Error as inserter shortcuts) — without forking the block.
Replace the scaffolded placeholder with a real custom Callout block — editable title, body, and a type selector — using registerBlockType + edit/save.
Add a settings sidebar to your block — ToggleControl, SelectControl, ColorPalette, PanelBody — so users configure attributes without typing into the block.
Let users nest other blocks inside yours — InnerBlocks, allowedBlocks, template — to build container blocks like cards, columns, and panels.
Understand WordPress's block editor architecture — what blocks are, how the editor differs from the classic one, and why everything is a block now.
Install Node.js, scaffold your first block plugin with @wordpress/create-block, and connect it to a local WordPress install — in 30 minutes.
Ship your plugin to WordPress.org — readme.txt format, screenshots, the wp.org submission review process, and post-launch maintenance.
Use @wordpress/scripts test, React DevTools, and block validation to catch issues before they hit production — including the dreaded yellow validation warning.
From `git init` to a live URL on a custom domain in under 30 minutes. Covers Pages config, custom domains, and the most common build errors.
Build a production-ready Astro frontend that consumes a WordPress backend via REST. Includes auth, ISR-like caching, and deploy-to-Cloudflare config.
No tutorials match. Clear the filters to see them all.
Practical tips, tutorials and resources. No spam.