WordPress straddles the line between design and development, and the honest answer is it requires both—just in different ratios depending on what you're building. If you're customizing an existing theme with a page builder like Elementor or Divi, adjusting colours, fonts, and layouts, that's primarily web design work. You're making visual and UX decisions without writing much code. If you're building a custom theme from scratch, writing PHP templates, hooking into WordPress actions and filters, optimizing database queries, or developing custom plugins, that's full-stack web development. Most real-world WordPress projects fall somewhere in the middle. You need design skills to make the site look good and convert visitors, and you need development skills to ensure it loads in under two seconds, handles 10,000 monthly visitors without crashing, and ranks well in search. At Ottawa SEO, we've seen countless sites that look beautiful but tank in Core Web Vitals because nobody optimized image delivery or minimized render-blocking scripts—that's a development problem. Conversely, we've seen technically solid sites that convert poorly because the designer didn't understand hierarchy, whitespace, or mobile UX. The terminology matters when hiring. A WordPress designer typically works in the Customizer, page builders, and maybe light CSS tweaks. A WordPress developer writes custom PHP, handles REST API integrations, builds WooCommerce extensions, or migrates complex data structures. If you're running an agency site or a basic service business, you can often get by with a strong designer and a pre-built theme. If you're building a membership platform, a custom booking system, or a high-traffic content hub, you need a developer who understands caching layers, CDN configuration, and server-side optimization. WordPress's strength is that it lets non-developers do design work, but its flexibility means serious projects still need code. Don't assume a page builder replaces development—it just shifts where the complexity lives.