To Reviewers and GraphicRiver Staff in General (about rejecting emails)

Hello everyone,

First of all I have to state that I’m a novice user.

This thread is about the statement emails sent to users by reviewers in general.

I appreciate the concern for the new quality standarts on GraphicRiver (yes I have read the thread about it) and agree with it in all respect. The thing is that I’m still not exactly sure about the main reasons items get rejected. Because rejecting emails aren’t explanatory enough! The Item Discussion forum points out that many new users, like me, have the same problem. I believe more specific feedback could be a very big help and time saver for all of us users & reviewers! In my opinion the standard statement emails of GraphicRiver are just confusing.

In my case my reviewer (I would like to note that reviewers are very helpful, I’m not blaming them) mentioned that my item has some well done design concepts, however it does not meet the current and very stringent quality guidelines. This sentence calls forth that the concept of, in my case, naive hand-drawn emoticons is acceptable (like many other naive and/or hand-drawn top selling items on GraphicRiver), which means that the designs we sent doesn’t have to be highly detailed as long as we create them ourselves! So according to this statement, my item isn’t insufficient. Or are they just trying to be polite? So I guess there must be a problem with the vectors, maybe a missing node, a non-edited node or maybe too many nodes that makes the item uneditable for the customers? Or maybe there is another mistake I have made? Maybe I uploaded it again under the wrong category (like my previous item) ? In my opinion the category section is also a tricky and confusing part for novice users. The reason for this is, many relevent items are diversly categorized, (like the sub categories under Graphic and Vector are alike) and yes I know that they are not the same. But what if I create my main design with help of a vector based program and also want to add a high dpi/pixel .psd version with smart objects, blend effects and many well organized layers or maybe 3D renders to the end product to make it also interresting to another group of potential customers? Let’s say I designed a character in a vector based program, saved it in required file extensions, then I edited it in photoshop and saved it in .psd .png for customers who are not familiar to vectors, then produced 3D models of the character so I’ll have a wider range of potential customers … which is the appropriate category for the main file now? Is it Vectors \ Characters, Graphics \ Illustrations \ Characters or Graphics \ 3d-renders??? My main point is, from now on if you could specify the reasons for rejection like pointing to the exact problem, users like me will not bother reviewers with question emails (which will save you time from answering them) or won’t get discouraged/frustrated and stop joining the community or even designing.

Please take this thread into consideration because I believe many novice users have the same issues.

Post a Preview

There is a lot of good perceptions what you wrote here. But why with an “alt” ?

dekurvajo said
There is a lot of good perceptions what you wrote here. But why with an “alt” ?

“alt” ? What “alt” ?

tolgaucagi said

dekurvajo said
There is a lot of good perceptions what you wrote here. But why with an “alt” ?

“alt” ? What “alt” ?

He means posted with your alternate account

We shouldn’t ignore what he’s saying. I think reviewers should have some more premade e-mail templates to send. Just some variety for the most common mistakes, a reasonable work for an important improve: users will upload less stuff.

In the comment box type “If you reject this item, please tell me what should be improved.”

As far as I remember, I always get a specific reply if I type this.

About 9 months ago, having this issue in mind, several community authors contributed towards the creation of a Visual Rejection Guide, which aimed to help fellow authors better understand their rejections, on a technical/visual level.

I have no idea if authors are aware of this available wiki resource, but if that’s the case, maybe, with the help of additional authors and reviewers, we can improve it, to the point where many can benefit and learn from it.

I know it’s not the perfect solution to the whole rejection feedback issue, but it can be extremely helpful.

Dzinc said
About 9 months ago, having this issue in mind, several community authors contributed towards the creation of a Visual Rejection Guide, which aimed to help fellow authors better understand their rejections, on a technical/visual level.

I have no idea if authors are aware of this available wiki resource, but if that’s the case, maybe, with the help of additional authors and reviewers, we can improve it, to the point where many can benefit and learn from it.

I know it’s not the perfect solution to the whole rejection feedback issue, but it can be extremely helpful.

This guide def. needs to be updated. Not for my sake, but for the newer authors sake. I understand rejections pretty well, but many times I see threads started because there isn’t enough data to help them understand what needs to be fixed. A newer document would def. help these guys & gals out a lot with their unanswered questions.

Right now the document it’s very lackluster with very small preview images that do not provide enough information. Seems like it was poorly put together. I believe that if there were more time spent on this document, it could resolve more problems regarding rejections, but as it stands right now, it really needs more refinements and the quality of the document is just not up to par with industry standards. Especially considering rejections are very subjective, and this document only gives a few pointers.

I did however create a very useful thread in the item discussions forum that goes into full detail about how to handle rejections and how to proceed into getting your files approved. I believe this thread could have been overlooked and perhaps maybe it could be a sticky thread.