I think I could really use this and am considering investing the money (reasonably priced) but am hesitating over whether or not I want to spend the time to figure it all out. The documentation is pretty extensive and pretty well-written, but the PDF file bookmarks don't work, making navigating the docs a real pain. I suggest the developers create live bookmarks in the PDF docs.

I think that sales of this product would increase if they would include a succinct description of exactly how the thing works in practice, both on the website and early in the docs. I had to dig and dig until I finally found a simple explanation on Page 44 of a 61-page manual. You have to embed some HTML FORM code into a page (they supply some examples) and then when you access the "editor" page (PHP, JS, ASP, etc.) it posts the edited data into the page with the FORM. I kept scratching my head and digging through the docs trying to figure out how they control access to the editor,, when I stumbled across this line:

"Please note that you should restrict access to your copies of the editor file (i.e. using your web server‟s access control features or by keeping the file names secret), or any Internet user with access to your website and knowledge of your “editor” file names may be able to update that content on your website."

If they'd mentioned that earlier much would have been clear much sooner. They're probably so close to the product that they think this stuff is self-evident, but to someone like me who's never done forms, it's not.

If they made a trial version easily available then I'm sure everything would become plain also, but they don't.