Things I’ve heard recently:
- How do you learn WordPress? In what order should I learn things?
- Learning WordPress is easy, there are so many resources.
- Why can’t these senior React front-end devs understand WordPress?
WordPress is versatile and open, as in open-source, and also as in jump in where you want and go as far as you’d like.
When we say “learn WordPress”, that can mean many things:
- Learn to write a post/page?
- Learn to manage a site?
- Learn to create a child theme?
- Learn to customize with plugin overrides or using plugins to achieve customization?
- Learn to make a theme from scratch?
- Learn to make a plugin?
- Learn to make a block?
- Learn to use APIs for a decoupled approach?
When we think about building a website, there are skillsets around
- Development (with code)
- Quality Assurance
- Front end
- Back end
- Full stack
At 41% of the internet and growing, there really is a lot to learn. Where you start, and what your own outcomes are can vary. We progress from being a website visitor to using the software and some of us even go on to write code that makes the software. There are so many skills to acquire in that journey.
My favorite myth to dispel is that teaching or learning is easy. Like a final release, things should be free of bugs and intuitively work well. Behind the scenes, a great deal of work happens to provide the user or student with a cohesive learning experience. Likewise, without a roadmap or guidance on what to learn next, you can get lost in a sea of resources.
I’ve had the honor of teaching WordPress in a development bootcamp environment this past year with a focus on front-end development. While getting a good look around at the bootcamp and non-WordPress (or even non-CMS) web developer ecosystem, I frequently encountered roadmaps to learning. Think of the map as a syllabus handed to students, sharing where we are starting and what our goals will include. Yet there are few maps that incorporate WordPress or PHP into the web developer’s learning.
Let’s help folks get started at any point on their journey, and discover any gaps in learning, and provide suggestions on what could be learned next.
This map will hopefully help shape the content on https://Learn.WordPress.org and could be implemented in a more visually organized way of navigating lesson plans, courses, and workshops.
Roughly, here is what I have found. The image may be a bit small, so check https://whimsical.com/embed/EG8T9S7zddbSVhnm85MmDf.
I am attempting to get these details and sequences out of my head and into something presentable for others. I welcome feedback, collaboration, and input on these.
Certainly far more can be included into this roadmap that encompasses more details. However, I wanted to pause here to avoid overwhelming folks with too many specifics.
I have incorporated @chanthaboune WordPress Contributor Team Structure and @mapk’s Care and influence: a theory about the WordPress community into the overview.
Leave your feedback below
- Employers, what do you look for in new-hires?
- Experienced developers, what do you wish you had more guidance around? What is new or emerging that should be included?
- Aspiring developers, what have you discovered so far?
This content was originally published here.