WordPress has an active economy and a great community. You will often hear the phrase “WordPress community” to include both. It can be argued how it has made WordPress a huge success over the last decade and a half.
But finding your niche can be difficult and you shouldn’t expect it to happen quickly. So this begs the question: Where to start WordPress development?
When I first started working in WordPress, it was not in an official capacity. as i mentioned in previous post, it was all about making minor changes to the site I was blogging on while I was in college.
Even after that, despite taking some courses in PHP, MySQL and general front-end technologies of the time, I was not progressing in my career. Instead, I focused more on .NET for a few years and did a lot of server-side work (with a fair amount of front-end work).
When I was not on the clock, however, I was using WordPress to blog about my experience working in the field of software development. But as I started using more tools in web application development, such as Ruby on Rails, PHP, and MySQL, I also started looking at how WordPress could be used a lot Same things I was doing with these techniques.
Even so, it took me years to finally make enough money to move into the WordPress economy.
Looking back, and considering where WordPress is now, what advice would I give myself if I were just starting out. What advice would I give to those who are just starting out?
Get started with WordPress Development
First and foremost, I have a mindset that the WordPress that exists today is not the same as the WordPress that existed when I started.
I was working mainly with PHP, MySQL, HTML, CSS and jQuery. Later came preprocessors like Low And mother-in-law And if you search back and forth in the archives of this blog, you will find posts about it.
That said, it doesn’t mean that getting started in WordPress is all that different, either. At that point, we had a set of technology to use, we had to learn how it all worked together, and then we had to make sure it wasn’t put together like a weekend project, but There was a similar level of quality to the work we were aiming for in our day-to-day tasks.
I don’t think I personally achieved it later, but it did eventually.
Anyway, although WordPress includes a different set of technologies (hence why I say it’s a different project than it was when I started), it’s no different in the context of someone who is just starting out. That is, you still have to master some techniques and learn how to make them all work together.
don’t start with a niche
And this is where the first piece of advice I’ll share with anyone just getting started with WordPress today is:
WordPress has always been a great software with a lot of areas you can work in.
Sure, you can also add in other areas of the entire community through a variety of efforts, but if you’re a developer and you’re comfortable experimenting with different types of technology, don’t try to pigeonhole the economy. Don’t put yourself in a specific place.
You don’t know where you can find the area to which you really contribute the most.
See everything and create something
To truly understand the scope of what you can do with WordPress, it has helped me to think about it in several different segments.
- The backend is database, PHP, and compliant with the set of technologies that allow the backend to be a file system and community with third-party APIs.
- The frontend also consists of Editor, React and other similar components.
A complete set of APIs are available for both the frontend and backend, each of which are available through developer handbook. In addition, there are Many Number of blogs and tutorials and screencasts available that will help you figure out where you want to start.
But here’s the thing: although I think it’s more important that you start somewhere you think you’ll have an impact; It is important to try to relax in other areas outside your comfort zone.
Let’s say you are comfortable working with frontend technologies, but you might not be comfortable with React and the various components that come with it.
Conversely, let’s say you’re someone who’s comfortable writing PHP, but you’re not sure how to get information to and from a database and make it available to the rest of the application.
Maybe it’s a good idea to try writing a plugin that allows you to read and write post metadata and work with meta boxes in the editor. It tells you about PHP, databases, some APIs, and also allows you to see how it all fits together.
What you already know
Obviously, these are two very general and very broad examples of what you can do. The point though is that each of these can slowly take you to other areas.
If you try something new without knowing Anything About that, it’s going to be extremely challenging. But if you start with something you know and can ease into what you don’t, it’s going to feel a lot less intimidating and a lot less difficult.
For me, I started working on simple template tweaks and plugins mainly because I was comfortable with PHP. This prompted me to search for documentation and become familiar with how to read and write data against a database using the available APIs, then to learn how to safely query a database using direct queries. went near, then went out in my learning http api, ns File System API, and then incorporating other libraries into your work.
No, it didn’t happen quickly (and there are some for whom it happens more quickly than others. I’m not that person. ). But it happened over time.
And yes, I’ve worked with some frontend techniques as well, but that stuff is for another post. But if your job is like moving to a city you’re familiar with, move to an area you know, then start taking other roads in parts of town you’ve never been to.
You can find not only an area you enjoy visiting, but an area you may like more than where you came from.
what comes next?
A lot can come ahead. It depends who you ask. But, for me, it was a two-way process:
- I started working with others who appreciated the strength (and vice versa),
- And I started sharing everything I was learning, no matter how much other information was available.
But I will talk about it in the next post.