With special thanks to Melapress!
<a href="https://roadmap.sh/wordpress" target="_blank" rel="noopener nofollow">https://roadmap.sh/wordpress</a>

Community driven learning paths, articles, projects and guides for developers to grow in their career.

roadmap.sh

A new learning roadmap for WordPress has been released on roadmap.sh, providing a structured path for developers to learn WordPress development. The roadmap was created with support from Melapress.

NEW ROADMAP: WordPress

What is really missing on this roadmap is a mention of bad practices, quality control, benchmarking, and resource budgeting.

I see Felipe’s point <a href="https://app.daily.dev/felipepitol" data-mention-id="2RBbmrWgf" data-mention-username="felipepitol" translate="no">@felipepitol</a> about this being a ‘map of the territory,’ but I think Jaro <a href="https://app.daily.dev/wpspeeddoctor" data-mention-id="PSHEaQRJMuWifIZvzar8w" data-mention-username="wpspeeddoctor" translate="no">@wpspeeddoctor</a> is onto something crucial about Architectural Strategy.
The roadmap lists Headless, FSE, and Classic as destination points, but it misses the Decision Matrix connecting them. A junior dev might learn Headless WP because it’s on the map, without understanding that for 90% of clients, it’s arguably the wrong choice.
Also, seeing Accessibility buried at the very bottom with ‘Multisite’ feels outdated. In 2025, a11y isn’t a post-launch checklist item; it should be foundational, right up there with HTML/CSS.
If we added a ‘Common Anti-Patterns’ node (e.g., DB bloat from autoloaded options, dependency hell), this would go from a ‘List of Features’ to a ‘Guide for Survival’.