What are the one (or 2) most important things you have learned or can give as advice for a new submitter?
I am just about ready to submit my first theme to theme forest and I want to make sure I am buttoned up. The last thing I want to do is forget some thing silly.
What’s some insight you have?
Thanks! Tim
- Most Wanted Bounty Winner
- Sold between 250 000 and 1 000 000 dollars
- Has been a member for 5-6 years
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Won a Competition
- Bought between 100 and 499 items
- Exclusive Author
- Referred between 200 and 499 users
Prepare yourself for at least a soft rejection.. 
Are these soft rejections usually referencing HTML/CSS/JS or the way things look?
How do they assess code?
The review process

Really helpful, thanks guys!
Nice post aleluja 
One thing I’ve learned is to never underestimate the time it will take to test your theme and to write your documentation.
I use to think I could clean up, test, write the docs and create the preview images all in one day and was always left disappointed when I wasn’t able to achieve it in that time frame.
Now Ive started to set out 2 days to test and clean and 1-2 days to write the documentation and create the preview images.
- Sold between 100 000 and 250 000 dollars
- Author had a File in an Envato Bundle
- Has been a member for 4-5 years
- Author had a Free File of the Month
- Won a Competition
- Author was Featured
- Item was Featured
- Bought between 10 and 49 items
Validate your markup, test every page in every supported browser with script console open, make sure there are no js error, test on real mobile hardware if possible.
this would help avoiding technical rejections but the issue could be design related, in that case, don’t over-react and follow the suggestions in the rejection mail.
when everything else fails, try the alternate review process:

aleluja said
The review process![]()
love it!
bitfade said
Validate your markup, test every page in every supported browser with script console open, make sure there are no js error, test on real mobile hardware if possible.this would help avoiding technical rejections but the issue could be design related, in that case, don’t over-react and follow the suggestions in the rejection mail.
when everything else fails, try the alternate review process:
![]()
+1 , you can be sure that those sites like RESPONSINATOR could be very misleading.
You may or may not get soft rejected (if you make it that far) and told to run it through the developer plugin and include a license.txt file, etc. It’s annoying, especially when you already do these things but they’re just making sure you don’t release any shoddy code.
