I’ve been building websites for years, mostly with custom code using JavaScript, HTML, and CSS. A while back, I made a site with Squarespace because a client wanted it, and I figured it would be a good learning experience.
Now, I have a new client asking for a WordPress site. I assumed it would be similar—drag and drop with a little custom CSS and JavaScript when needed. The client got hosting on SiteGround and gave me access, but I feel like I’m hitting a wall.
It seems like everything in WordPress is tied to plugins, and a lot of the good ones aren’t free. I tried Elementor, but many features are locked behind a paywall. Is this just how WordPress works? Do developers usually expect to pay for a bunch of plugins?
Also, I signed up for an account on WordPress.com and used their editor, which reminded me of Squarespace. Is that version not the same as what I’m using on SiteGround? I’m kind of lost and could use some advice.
If you want to avoid writing code, you’ll probably end up paying. There’s a plugin for almost everything, but a lot of them keep their best features behind a paywall.
If you are, then no. I build custom WordPress sites using the built-in block editor, and I don’t use a single plugin… but that means writing a lot of code (HTML, CSS, JS, React, PHP).
Lennon said: @Finnian
Wait, how did you build a plugin without writing code? Or did I misunderstand your comment?
Haha, I knew someone would say that! Of course, I used code. My question was more about whether every feature needs to be a separate plugin or if there’s another approach. I just wanted to understand the best way to integrate new features.
@Finnian
You don’t have to make everything a plugin. Usually, you start with a theme and then add features either as separate plugins or within the theme itself.
Someone mentioned that you can do a lot with the block editor while still writing custom code. It depends on what you’re building.
By the way, don’t edit WordPress core files or theme files directly unless it’s your own custom theme. Updates will wipe out your changes. Instead, use hooks and filters to modify things the right way.
Nyx said: @Lennon
Do you know of any good tutorials for learning WordPress coding?
There are plenty of tutorials out there. If you’re new to coding, it helps to start with basic PHP before diving into WordPress. Python is a good beginner-friendly language if PHP feels overwhelming.
If you already know PHP, the official WordPress Developer Handbook is a great resource. Just be ready to Google things along the way.
I pay for a few plugins and one theme. That’s it. I’ve built over 100 sites with less than 10 plugins. The only time that number goes up is when WooCommerce gets involved. That’s when you start paying for everything.
Nyx said: @Brook
What kind of plugins do you end up using with WooCommerce?
Stuff like subscriptions, memberships, shipment tracking, advanced coupons, product bundles, and product add-ons. There’s always something extra to pay for.
WordPress is super flexible. You can build anything—blogs, stores, membership sites, whatever. But if you want to fully customize things, you’ll need to know PHP and JavaScript.
Some plugins are great and save you time, but too many can slow your site down. I once had to fix a site that was crawling because of a poorly coded plugin.
At some point, you’ll probably get comfortable enough to build things yourself instead of relying on plugins. It takes time, though, especially if you start using WooCommerce. That makes things way more complicated.
Good developers weigh the cost of buying vs. building. Some plugins are totally worth paying for, like ACF and Search and Filter Pro.
As for your question about WordPress.com vs. SiteGround’s version, I’m guessing SiteGround has the classic editor enabled instead of the block editor. That’s pretty common.
If this is a paid project, the client should cover plugin costs, not you.
If you underestimated the work and need plugins to meet expectations, just be upfront about it. Explain that you tried everything you could with free tools, but some features require paid options. Better to have that conversation early than waste time struggling.
Being honest about these things builds trust, and clients respect that.
I once had a client who needed a simple ‘Accept Terms’ checkbox in WooCommerce. There was a plugin for it, but it cost $25. I could’ve built it myself, but my hourly rate would’ve made it way more expensive.
That’s how I decide whether to use plugins or write custom code—if a plugin saves enough time and is well-maintained, I’ll just use it.
WordPress told me I needed a business plan to install plugins. Someone suggested moving to DreamHost so I wouldn’t have to pay extra just to use plugins. Thinking about making the switch.