Custom themes, plugins, content models and troubleshooting for WordPress.
About this learning path
WordPress runs a large share of the web because editors can manage content without a developer. That only holds when the code underneath is organised: a clear content model, plugins that follow WordPress conventions, and a calm process for when something breaks.
This path starts with modelling content (custom post types, taxonomies and fields), moves on to building plugins that are secure and easy to maintain, and ends with a step-by-step method for fixing the “critical error” screen without guessing.
Who it’s for: Developers who build or maintain WordPress sites for clients, and site owners who want to understand what good WordPress code looks like.
What you’ll learn
When to use a custom post type, a taxonomy or a meta field, and how to expose them to Gutenberg and the REST API
A plugin structure that keeps hooks, admin screens and REST routes separate
Nonces, capability checks, sanitising, escaping and $wpdb->prepare, with examples
How to read debug logs, isolate a faulty plugin or theme with WP-CLI and recover a broken site
A calm, systematic way to fix the WordPress critical error and white screen: recovery mode, debug logs, isolating plugins and themes with WP-CLI, memory limits, corrupted core files and stuck maintenance mode.
A practical blueprint for custom WordPress plugins: file structure, actions and filters, the sanitize–validate–escape rule, nonces and capabilities, safe database queries, REST endpoints and clean uninstalls.
When to use a custom post type, a taxonomy or a meta field, and how to register each properly for the block editor, the REST API and fast queries, with a real-estate listings example.