A carpenter will need to buy tools regularly, a driving instructor will need to buy a new car regularly. Buying your tools–f-the-trade comes with the job. Especially if you’re using RapidWeaver to sell webdesigns to clients.
Depending on your use case, RapidWeaver Classic can be a perfect fit out of the box, or requires a few third-party plugins to get it to that level.
Out of the box, RapidWeaver (Classic) can build a good looking website, containing a blog, contact form, photo gallery and a file sharing/downloads page. The included themes are (mostly) good fits for the average beginner.
If you’re planning to sell your designs to others, then yes - you’re going to need to invest in plugins. That’s because clients always have a wish or two that RapidWeaver can’t do (or the themes you have can’t do). Those wishes can range from “can you shift that button like an inch to the right?)” to “I want my site to look exactly like Apple’s!”.
Stacks is one way to go - coding your own themes is another. Both will require you to invest (either by buying third party plugins or invest in time to code out a new theme). But you can at least get the job done (which can’t be said for Website-as-a-service-providers like Squarespace).
Even on the “free” Wordpress you’ll quickly look at paid-for third party extensions when trying to figure out how to comply with your clients’ wishes. And those plugins often come with a per-domain license, requiring you to repurchase them for every new client.
With Elements, this will be more-or-less the same. Layouts are pretty much covered with Elements judging by the videos, but knowing lcients, they’ll have wishes that will require a purchase from your end. you already mention carts, but I think some kind of database/CSV-integration, a CMS, automated gallery and a good expansive form solution will be among my first third party purchases once I roll out Elements here.
It’s all part of the fun! I don’t mind buying stacks (and elements in the future) if it saves me time and gets the client what they’d like to see. Part of the invoice I send them is to cover the cost of constantly buying tooling. And if it’s a very specific wish that the client has, I might even forward the cost of that specific stack or plugin 100% into their invoice (as I’m notl ikely to ever use it again for another client).
Cheers,
Erwin