Thanks for convincing me to take my mods elsewhere.
If that’s the case, you should NOT have started your post with insulting reviewers. Ask your question and leave it at that. When you start insulting people you will get this kind of reaction.
Constructive note – there’s nothing we can do to help you. You will have to wait for a response from support.
I believe the older plugins may have a more out-dated documentation that may possibly need smartening up.
I can see why they asked for the documentation to be improved though. Black text, white background, may get the point over but isn’t very attractive or easy to navigate.
I imagine they pointed you towards the Documentor 2.0? Which is so easy to use you could of easily whacked out another documentation and be selling already. To say your documentation is far superior is an over-exaggeration. As already mentioned continuity is an issue and they will want as many submitted files to have a similar style, they couldn’t enforce this rule before the Documentor was made.
When I got my first SR for documentation I was over the moon, meant I was getting somewhere. I appreciated the fact they told me what I needed to do to get a submission accepted.
To come and insult Envato for enforcing such rules is absurd. Seeing as Envato is one of the biggest networks of its kind, if not the biggest, you need Envato a lot more than you may realise.
Being a new author myself (despite registering in 2011, I created my first item for sale in August 2013, submitted in September 2013), I completely understand where you’re coming from. Just like you and sniperatic, and (I’m sure) so many other people, I had my item (WordPress plugin in my case) soft rejected for reasons of documentation. And again, just like sniperatic, I was over the moon when this happened! Why so? Well, I expected to get a hard reject with a message that my submission was poor/not up to CodeCanyon standards/useless/etc, basically I expected everything and anything but a soft reject. Yes, submitting an item for the first time, I was pretty nervous about it, and not very self-confident. It seems this is not the case with you, but IMHO you may need to try and be a bit more realistic about your expectations.
Now, I won’t hide it, for me getting the mail that “Your uploaded item X needs improvement” was both a pleasant surprise (for reasons mentioned above) and a bit of a shock, especially when I, just as you state you have done, spent the better part of a day putting together what I thought to be a most extensive documentation. The reason the reviewer considered my documentation needed more work? I had missed to point out several things which are obvious to me, but would have proven (most likely) too difficult for users. Of course, right after receiving the mail I was in a similar mood to you right now, so I forced myself to leave the computer for a while. After letting my emotions cool down, I sat down and went through the documentation trying to see it from the perspective of a buyer who expects that reading the documentation would be like someone taking him/her for the hand and guiding him thought the process of installation/customization/whatever. In fact, that’s a very good approach to writing documentation in general if you ask me.
Here is some piece of advice from me as an author to you as a fellow author:
1. Simplify the overly-technical parts of the documentation, especially install and customization processes. Try to get rid of some of the more complicated terms and replace them with words that sound more human while making sure the tone/wording remains suitable for a guide.
2. Nobody wants to read useless stuff. Avoid going into too much detail on topics that don’t need it. (You don’t seem to need this advice, but you may find pt.3 useful).
3. Don’t be too “straight-to-the-point” either (as it seems you have been, judging by what I saw as your documentation). You may not realize it, but it sometimes feels a bit rude, as if you were forced to write a documentation against your will and you just whipped something up.
4. Finally, and I can’t stress this enough – use a lot of images. Take screenshots of the more important parts of the main processes involved in using your item and accompany them with a descriptive text. Again, no need to spend too much time describing what each and every little thing does. If buyers have questions, they can e-mail you or post a comment on the item page, and believe me when I say, they will.
5. (OK, seems like pt.4 won’t be the final point after all) Try to switch from a .PDF documentation to an .HTML one. This will allow you to make the documentation a bit more interactive, something which .PDF doesn’t make possible.
Just one more advice. By all means, include a friendly paragraph that says “Thank you for purchasing my item” in your own words. Make it sound as if you really are happy that they found your item useful for their project. Being genuinely happy for (and friendly to) your buyers is a definite plus, and it can be felt in the way you respond to their comments, for example.
In the end, let me say one more thing. It wasn’t very nice of you coming to the forums and insulting reviewers for something you could have fixed easily. I do hope you understand that it didn’t make you look more professional. I would like to add what I think is a very fitting quote from Tywin Lannister, a “A Song of Ice and Fire” character – “And any man who must say ‘I am the king’ is no true king at all.” I don’t want you to feel offended in any way, but you do need to realize you didn’t make a very good first impression.
Hopefully the things I pointed out as advice would help you get your items approved. Looking forward to seeing them on the front page!
P.S. Sorry for a soooo very long post, but I needed to mention a lot of things.
Just going to throw this out there, but your documentation does suck.
Just submitted my first plugin ever and I too wonder if the reviewer may have had a rough day at work and decides to be picky, you know.. kinda reminds me of when I was at University.
I was intrigued by how your documentation was written up so you could justify your attitude and anger, therefore, I took at look at it. Taking into account the fact that you mentioned that you had X number of years in writing documentation and/or selling products, I must say that I am not at all impressed.
1. The minute I read the name of your file “house_brand_module_install.pdf” I expected clear and concise installation steps, however I ended up trying to read the first half page which didn’t make sense to me at all.
2. “What it does” section does not really explain “what your module does” and you deviate from topic straight away by trying to give a restaurant example, no one has time to try and make logic out of this.
This could be more appropriate:
Description: The House Brand Module extends the functionality of the OpenCart branding feature by allowing you to promote your own in-house products.
3. Do not list features in an installation document, users just want to know how to install it, the already know the features this is why they bought your module in the first place.
4. The only installation steps I see are 1-5
The fact is that I’m reviewing your documentation from a client’s point of view and I think the Envato reviewer is correct in asking you to rewrite the whole documentation.
We are all here to help each other as Authors, hope you do well next time
Good luck on your item Plugarized!