WordPress work rarely begins with a blank install. It begins with somebody else's site, thirty-eight plugins deep, and a message at 22:40 saying the homepage went white after an automatic update. The person who built it is unreachable, the host says the site is fine, and the client has a launch tomorrow. Everything useful you learn in this trade gets learned against that background, and the roadmap below is arranged around it rather than around the fantasy of starting from an empty folder.
The site you inherit is the real brief
A WordPress developer is the person who makes a WordPress site do something it does not do out of the box, and then keeps it doing that thing while the platform, the plugins, and the host all change underneath it. That covers theme work, custom blocks, plugin development, WooCommerce, migrations, performance, and security. It also covers the least glamorous part of the job, which is deciding which of the thirty-eight plugins can be removed.
The platform's share of the web is the reason the work exists, and it is also the reason the price floor is low. Anyone can install WordPress in ten minutes, so clients reasonably ask why they should pay someone. The answer has to be technical and specific: your site loads in four seconds on a phone, mine loads in one. Your checkout fails for logged-out customers, mine has been tested against that case. Your last update took the site down for six hours, mine ran on staging first. That answer is the entire commercial argument, and it is built from the four areas below.
There are three shapes of paid work, and they behave differently. A new build is a project with a beginning and an end, and it is the shape beginners chase. A rescue is a fixed-fee repair with a clear before and after, and it is the fastest way to earn trust with a business that already has a problem. Maintenance is a monthly arrangement that covers updates, backups, monitoring, and small changes, and it is the only one of the three that produces predictable income. Most working developers end up with a mix, weighted toward the third.
The technical surface is wider than the title suggests. You will touch PHP daily, but also CSS for theme.json and block styles, JavaScript for editor interactions, SQL when a query is slow, and a bit of server work when a host's cache fights your plugin. None of those need to be deep at the start. All of them need to be good enough that you can read an error message and form a hypothesis.
The job is not clicking a page builder into place and calling it development. Page builders are legitimate tools that ship real sites, and a developer who refuses to use one loses work. But a build where every layout decision lives inside a builder's shortcodes, and every custom behaviour lives in a snippet plugin, is a site that nobody can maintain, including you six months later. The value you add is structure that survives the next person.
One more thing belongs in the definition because beginners underestimate it. WordPress is a publishing system with a database at its centre, and most of the failures that look like "the site is broken" are data problems. A redirect loop caused by a stale option. A menu that points at a post ID that no longer exists. A serialised array corrupted by a careless search and replace. The developer who can read the database and the logs fixes those in twenty minutes. The developer who only knows the admin screens reinstalls and hopes.
The clients are not interchangeable either, and treating them the same is how developers end up resentful. A small business owner wants a site that brings phone calls and will judge you on whether the form works. A marketing team wants speed of editing and will judge you on how fast a landing page ships. An agency wants a subcontractor who does not create support tickets and will judge you on predictability. Each type needs a different proposal, a different update policy, and a different definition of done. Learning to hear which one is in front of you is worth more than another plugin tutorial.
The competences a broken site exposes
The work splits across four areas, and each one is exposed by a different kind of failure. Layout fails on a phone. Design fails in a handover. Search fails three months after launch. Checkout fails on a Tuesday.
Web Development
This is the core. PHP, the template hierarchy, hooks, custom post types and taxonomies, the REST API, and enough of the block editor to build something a client can edit without breaking. The template hierarchy is not trivia. Knowing that WordPress looks for front-page.php before page.php, and single-post-type.php before single.php, is what lets you change one page without forking a theme. Hooks are the other half: an action fires, a filter transforms, and priority decides the order. Almost every customisation you will be asked for is one of those two things.
The catalog holds 36 live resources in this category, with 30 free and 6 paid. DiscoveryVIP Interactive Guides (FREE) is a large free set of hands-on WordPress walkthroughs, useful when you need to see a specific admin screen explained. HTML For Everyone: Real World Coding in HTML5 (FREE) fills the gap most WordPress developers have, which is the document model underneath the theme. Responsive Web Design Certification (freeCodeCamp) (FREE) covers layout and CSS with enough depth to stop fighting the editor.
For tooling, Beginner VS Code (FREE) is a short, practical start on the editor you will live in, and Google Developers Codelabs (FREE) has guided exercises that make API responses legible. Full Stack Web Development Tutorial Course (YouTube) (FREE) is a long free sequence if you want the surrounding picture, and The Complete Front End Web Development Course (PAID) is the structured paid alternative for someone who wants a single ordered path.
One paid item belongs here for a specific reason. Build a Full Website using WordPress (Coursera GP) (PAID) is a guided project format, which suits a learner who needs a deadline and a graded result more than another video series. It will not teach you plugin development. It will get a first site finished.
Accessibility sits inside this area because WordPress ships with the tools for it and most builds ignore them. Heading order, form labels, focus styles, colour contrast, keyboard navigation in a menu, and alt text that describes the image rather than the product. A theme that fails these checks excludes customers from a business's site, and an increasing number of clients have a legal reason to care. Audit one site properly, note every failure, and fix them in your own theme first. That audit is also a sellable service, and it is the cheapest proof of competence you can produce in an afternoon.
UI/UX Design
On many projects the WordPress developer is the only design decision-maker. There is no designer handing over a file, and the client's taste arrives as a reference to a competitor's site. You need working judgment about spacing, type scale, contrast, hierarchy, and form layout, not because you are becoming a designer but because the alternative is a site that looks like a theme with the colours changed.
This area has 30 live entries, 20 free and 10 paid. Figma Learn (Help Center) (FREE) and Figma Resource Library (FREE) teach the tool clients increasingly expect you to read, and Penpot (FREE) is a free open-source alternative if a licence is out of reach. Checklist Design (FREE) and Laws of UX (FREE) are short references that answer the "why does this feel wrong" question quickly.
For the rules that actually show up in a WordPress build, Material Design 3 (FREE) and Apple Human Interface Guidelines (FREE) are the two most systematic public design documents, useful for spacing, hierarchy, and how components behave under pressure. Growth.Design Case Studies (FREE) shows the reasoning behind real product screens.
Paid design material earns its place when the gap is craft rather than theory. Refactoring UI (PAID) is the single most concentrated source of practical interface decisions, and Learn UI Design (PAID) is a structured version of the same skill for people who want a course rather than a book. Figma (PAID) is a working subscription once clients are paying for files.
SEO & Content Marketing
A WordPress site is usually a business's main search asset, and the developer configures the parts that decide whether search traffic arrives: permalink structure, headings, canonical tags, schema, sitemaps, redirects, and page speed. You do not need to run an SEO campaign. You do need to know which of the site's problems are technical and which are content, because clients will ask you to fix both and only one of them is yours.
The catalog lists 30 resources here, 27 free and 3 paid. Google Search Central Documentation (FREE) is the primary source and the only one that should settle an argument, and Google SEO Starter Guide (FREE) is the short version worth reading first. Yoast SEO Blog (FREE) and Rank Math Blog (FREE) cover the two plugins you will configure most often, and reading both is useful because they disagree about details.
Moz Beginner's Guide to SEO (FREE) and Search Engine Land's Guide to SEO (FREE) give you the vocabulary to hold a conversation with an SEO specialist without bluffing, and Ahrefs Blog (FREE) is strong on the mechanics of links, redirects, and migrations. For local businesses, Whitespark Local SEO Guides (FREE) is the most concrete free material on service pages and location data.
E-commerce & Dropshipping
WooCommerce is where WordPress work pays best, and it is also where it breaks most expensively. A store involves tax rules, shipping zones, payment webhooks, stock reservations, email deliverability, and a checkout flow that has to work for a first-time visitor on a slow phone. Every one of those is a place where a plugin conflict becomes lost revenue rather than an ugly page.
You will find 30 live resources in this area, 24 free and 6 paid. WooCommerce Documentation (FREE) is the authoritative source for hooks, templates, and store settings, and it is worth reading end to end once even if you never build a store immediately. Practical Ecommerce (FREE) covers the operating side, from fulfilment to returns, which is what store owners actually want to talk about. Printful Academy (FREE) explains print on demand and fulfilment from inside the process.
Ahrefs Ecommerce SEO Guide (FREE) covers category and product page structure, which is where most WooCommerce stores lose traffic. Create Your E-commerce Store with Shopify (Coursera GP) (FREE) is a useful comparison even for a WordPress developer, because knowing what the hosted alternative does well makes your WooCommerce recommendation more credible.
Learning in the sequence the work arrives
The stages below follow the order in which real work forces the knowledge on you. Each has a done test you can check without asking anyone's opinion.
Stage one: get PHP and the loop under your fingers. Install WordPress locally, activate a child theme, and edit one template by hand. Write a loop. Break it on purpose and read the error. Learn where functions.php sits and why a child theme is not optional. HTML For Everyone: Real World Coding in HTML5 (FREE) covers the markup half, and Beginner VS Code (FREE) sets up the editor with PHP linting. Done means a child theme with one custom page template that survives a parent theme update.
Stage two: learn hooks, custom post types, and the database. This is the stage that separates developers from tinkerers. Register a custom post type and a taxonomy. Add fields and store them properly. Use the hooks that fire around save, and understand why you escape on output rather than on input. Write one small plugin, not a snippet, so the code has a home. Done means a plugin that registers a post type, outputs it through a template, and passes a security review of its own output escaping.
Stage three: build a block, not just a page. The editor is where WordPress development has moved, and a developer who cannot build a custom block is limited to themes other people made. Learn block.json, register_block_type, attributes, and a render callback. Learn theme.json well enough to control spacing, colour, and typography globally. Build one block a client would actually use: a testimonial, a pricing table, a call to action with a form. Done means a custom block that an editor can insert, configure, and preview without touching code.
Stage four: make a WooCommerce store work end to end. Install WooCommerce on a staging copy and configure a product, tax, shipping, and a sandbox payment gateway. Place an order as a guest on a phone-sized viewport. Confirm the order email arrives. Refund it. Then read the template structure and override one template in your theme. WooCommerce Documentation (FREE) is the reference throughout. Done means a test order that completes, emails, and refunds, with one custom template in your own theme.
Stage five: performance, security, and hosting. Measure a site before you optimise it, because otherwise you cannot tell what worked. Learn page caching, object caching, image sizes, and what a host's cache does to a logged-in user. Learn the security basics that cover most real incidents: updates, least privilege, file permissions, and a login policy. Done means a site that passes a reasonable performance check on mobile, with staging, offsite backups, and a written update policy.
Stage six: rescue and maintain. Take a broken site and fix it without a rebuild. That means reading logs, disabling plugins in a controlled order, checking PHP versions, and using WP-CLI rather than the admin UI for bulk operations. Then write the maintenance agreement that keeps the site healthy: what gets updated and when, what happens if an update breaks something, and how fast you respond. Done means one rescue completed with a written post-mortem and one client on a maintenance plan.
The sequence matters for a practical reason. A developer who learns page builders first spends years unable to debug. A developer who learns PHP and hooks first finds that every builder becomes a convenience rather than a cage. And a developer who reaches WooCommerce with hooks already understood can fix a checkout instead of reinstalling it.
Licences, hosting, and what the free shelf covers
WordPress itself is free, and most of the knowledge is free too. The catalog's free material in these four areas covers the full path above, including the WooCommerce documentation, the search documentation, and several complete design references. A learner with no budget can go from the template hierarchy to a working store without paying for instruction.
What costs money in this trade is rarely the learning. It is the delivery stack: premium plugins with annual licences, a host that can handle cached traffic, a staging environment, a backup service, and design tools. Budget for those before you take a client, and price them into the project rather than absorbing them.
Paid learning is worth it in three situations. When you need graded structure, Build a Full Website using WordPress (Coursera GP) (PAID) or The Complete Front End Web Development Course (PAID) gives you a sequence with deadlines. When design craft is the visible weakness, Refactoring UI (PAID) is a better use of money than another plugin. When a client expects a design file in a specific tool, Figma (PAID) is a cost of doing business rather than a course.
Time expectations, honestly. A developer with some HTML and CSS can ship a simple theme-based site in four to six weeks of part-time study. Becoming useful at plugin development and WooCommerce usually takes six to nine months of steady part-time work, and the last stretch is not knowledge, it is reps against real breakage. The first paid project usually arrives before you feel ready, often from someone whose site is already broken. Take it, price it as a rescue rather than a build, and document what you did.
The income shape matters more than the hourly rate. A single build is a spike. Five maintenance clients at a modest monthly fee produce a floor under your income that lets you refuse bad projects. Most developers who last in this trade build the floor first and the projects second.
Quote rescues differently from builds. A build is priced against a scope you wrote, so the risk is yours if you underestimated it. A rescue is priced against a diagnosis, so the honest structure is a small paid audit first, then a fixed price for the repair with a defined end state, and a clear statement that new problems found inside the repair are quoted separately. That structure sounds bureaucratic to a client in a panic, until you explain that the alternative is an open-ended bill. Most prefer the fixed number.
Debugging is the job, not the interruption
The first habit that separates a working developer from a frustrated one is reproducing the fault in a controlled place. A staging copy with the same plugins, the same PHP version, and the same data. A large share of WordPress bugs are environment differences: a PHP version on the host, a caching layer, a missing extension. If you cannot reproduce it, you cannot fix it, and guessing at fixes on a live site is how small problems become outages.
The second is disabling before rewriting. A white screen is usually a plugin or theme conflict, and the fastest path is a controlled bisect: rename the plugins directory, restore half, test, narrow. Do it on staging, log what you did, and put the site into a maintenance mode that says something honest rather than a blank page.
The third is reading the database when the admin lies. Options, post meta, and user meta are where stale state hides. A menu pointing at a deleted post, a redirect rule that no longer applies, a serialised value corrupted by a text editor. Learn to look at the tables, and learn why a naive search and replace on serialised data destroys a site.
The fourth is keeping a change log from day one. Every plugin added, every setting changed, every snippet installed. When something breaks three weeks later, the log is the difference between a twenty-minute fix and a lost weekend. Clients also trust a developer who can say exactly what changed and when.
The fifth is testing the update before trusting it. Minor security releases can be applied quickly on a site with tested backups. Major version jumps get a staging run and a rollback plan. The update policy should be written down and agreed with the client, because "we update everything immediately" and "we never update" are both ways to lose a site.
Where the next site comes from
Go deeper in the areas this roadmap rests on: Web Development for the layer under the theme, UI/UX Design for the judgment clients expect you to supply, SEO & Content Marketing for the traffic side, and E-commerce & Dropshipping for the work that pays best.
Compare the neighbouring roles before you narrow your positioning. Web Designer sits on the same border with more design weight, Full-Stack Developer is the coded route out of the CMS, and Shopify Store Owner is the buyer you will meet most often. The full index is at Browse by profession.
One concrete next action: take a site you can access, run it through a mobile performance check, and write a one-page report naming three causes and three fixes with an order of work. Send it to the owner without a pitch. That report is the most persuasive portfolio piece this trade has, and it takes an afternoon.
FAQ
Do I need to learn PHP, or can I stay in the block editor?
You need enough PHP to read and modify a theme and to write a small plugin, and you need it more, not less, as the editor takes over. Custom blocks have server-side render callbacks in PHP. WooCommerce templates are PHP. Every serious debugging session ends up in a PHP error log. The good news is that the depth required is modest: functions, arrays, conditionals, and the WordPress APIs around them. That is a few weeks of deliberate practice, not a computer science degree.
Should I use page builders like Elementor or Divi?
Learn one, and learn its failure modes. Page builders win projects because clients can edit layouts themselves, and refusing them on principle costs you work. The failure mode is a site where structure lives in shortcodes and every change requires the builder's interface. Use a builder for marketing pages and keep the parts that need to last, such as templates, checkout, and custom post types, in code you control.
Is WooCommerce worth specialising in?
It is the most reliable way to raise your rate inside WordPress work, because store owners measure your work in orders rather than in aesthetics. It also raises the stakes: a broken checkout is lost revenue, and clients hold you responsible for payment flows. Specialise after you can build a theme and a plugin, not before, and learn the tax and shipping edge cases before you quote a store.
How do I compete with clients doing it themselves?
Do not compete on installation. Compete on the things a first-time builder cannot do: performance measured on a real phone, an update policy that survives a year, a checkout tested against edge cases, accessibility, and a handover that lets the client's staff work without fear. Offer a small paid audit as an entry point. It is a low-risk purchase, and it produces a list of problems that justifies the repair work.
What should my update and backup policy look like?
Backups run daily, stored off the server, and restored at least once so you know the restore works. Core and security releases applied within days, after a staging test. Major version updates on a schedule with a rollback plan. Plugins reviewed quarterly and removed when unused. The policy should be one page, agreed in writing, and included in the maintenance fee. Clients accept limits they can read, and they resent surprises.
What kind of first paid job should I look for?
Look for a rescue, not a build. A slow site, a broken form, a hack cleanup, a migration that stalled, a store with a checkout error. The scope is bounded, the problem is visible, and the client has already decided to spend money. A successful rescue produces a reference and usually a maintenance arrangement, which is a better start than a six-week build for a client who is still deciding what they want.
SkillCache Editors · Updated November 13, 2026
