My experience is that you need a healthy understanding of how to fix files and code to really get out of the WA extensions doing what they're marketed to do and that you want. That's generalizing and I'm admittedly not the higher end of experience troubleshooting or figuring out which files are supposed to be modified to make the outputs work right. But I'm not a newbie either. I own most of the WA extensions (that's another story) and in my singular view of the world they are not the 'out-of-the-box' experience as the marketing suggests. More like an out of body experience in which I've spent many hours trying to figure out what went wrong. The documentation has improved, but it's still in many respects hopelessly out of touch with the beginner to intermediate level. Far too much is left to the imagination rather than stepping one through using and troubleshooting the products, outputs, and associated files. The latter is what I really want out of documentation and should be the bulk of it: which files are doing what in the outputs and here is the one you want to modify or customize to accomplish A... or B... or C etc. And if this happens instead of what you expected, here are some things to try to correct. Forums are fine, but the documentation needs to be the first line of reference. Then again, if you are pretty darn savvy with troubleshooting files and code. WA does make many products that aren't available in the same form for web design anywhere else. If you're on the high end of skills the products may just be a godsend saving you time by creating a lot of outputs in a few steps. They just haven't saved me that kind of time, which is probably a failing of both of us.
