I get that it's the community's responsibility to build the product and supporting information. I really do…
However, if this product is supposed to be able to do real work for real companies to make (and not lose) real money then something's gotta change. Small enterprises can't be bothered with gizmo-products that are labyrinthine in their structure and take the same support effort as one of those multiple spinning plate acts in the old circus. Managing an Alfresco community server for real must be a labor of love and those folks must be constantly on call mopping up the "blood on the floor".
My original question was born of the desire to have a basic, out-of-the-box, generic install that could quickly support at least a meaningful demo/evaluation. If a small business IT guy can't get a single, coherent "how do I get this on a machine and use it", he/she will just click uninstall and move down the Google results list to the letter "B"… It's very simple. Example - Invites don't work unless arcane smtp lines are not hand-edited inside obscure properties files deep in the structure. Finding out about that, and how to fix it, was like unraveling a devilishly complex puzzle or riddle.
Now I love the promise that Alfresco has. I am still leaning heavily towards it as a solution for our small company. However, it would have to be as a hosted solution and, while there are many out there, I really do wonder if I will get a nasty shock when the ISPs guy can't keep it working for lack of timely info.
Perception is everything, people. These days risk is a 4 letter word in more than one sense, and my original appeal is asking for it to be reduced.