Not by a great deal though. If I want to put some info into the FAQ section it's as easy as writing this reply, plus the inherent overhead of writing the information and making screenshots. Since the Wiki won't be the manual, and vice versa, I see very little advantage to a Wiki versus what we already have in the forums. There would be some small advantages to using a Wiki instead of the forums for FAQs, but there are also disadvantages. (Having to look in two places. Not being able to promote threads to FAQs.) Doesn't seem worth the effort to me.
We can't do much about having to use Word unless someone comes up with a better way to generate the PDF, HTML-Help and HTML versions of the manual.
I don't think Wikipedia is an appropriate place for in-depth help and how-to articles on software. I'm fairly sure the Wikipedia admins would object to us using it for that.
Who is someone anyway? I'm against the idea to be honest (because I think the forums already serve the purpose and I think it is bad to increase the number of places people have to look to find information) so I'm not going to do it. I'm guessing Steve feels the same. GPSoftware themselves have enough work as it is keeping the main manual up-to-date. Not many of the other people who know Opus well enough to feel confident writing guides are in the habit of regularly writing FAQs or tutorials. The problem isn't that we don't have a place to write them, it's that writing them competes for our time with lots of other things (many of them other Opus-related things).
Since when has that not been accepted? I would say that simply using Opus does not have a steep learning curve, because the basic actions behave much like Explorer does. I, and I think everyone else, would agree that configuring and tweaking Opus does have a steep learning curve compared to most apps because Opus has a lot of options and most other apps have barely any at all.
Maybe people using Opus have to accept that it has a lot of options and they will not remember or understand all of them the moment they start using the program but will, like any other complex piece of software (e.g. Word or Photoshop) get better at using the program, and discover more aspects of the program, as a natural part of using it over time.
I still don't know where you get that impression from. I also don't know of anyone who could be called an Opus acolyte who isn't also present company in this thread or, at least, this forum. This forum which exists purely for the purpose of helping other people get more out of Opus.
The bottom line is that nobody is going to pick up a program like Opus and understand every aspect of it over night, no matter how good the documentation and acolytes are. To get the most out of it takes some time/effort on the user's part. Better tutorials may reduce that time but they will never reduce it to zero (and a lot of people don't even find the tutorials).
I have a bunch of ideas for further tutorials, when I get time, but they're not going to appear out of thin air. Someone has to write them. Feel free to make a list of things that could do with FAQs or tutorials, or which need improving in the manual, and me or someone else may incorporate that list into our plans.
Feel free to write some guides yourself, as well! But note that the only people who have written any tutorials/FAQs so far are complaining about lack of time, not lack of a Wiki.