My theme got rejected, need help

raptour said
Dear Mark, I just rejectred your file again. Reason: I don’t like the cut of your janky argyle socks. You’re wearing your shoes on the wrong feet. <3 “Jarel”

lol

well sorry but i don wear socks nor shoes, i walk bear footed (i hope that i said it correct ;))

Hey guys, funny thread.

The depth of documentation depends on how many pages, features and options your item offers. The more it offers, the more you should cover in the documentation. It doesn’t have to be a book but it needs to be more in-depth than listing the item’s CSS files or the very, very basic HTML structure of one page or section.

@ Mark – Your admin template is pure awesome. It’s a pleasure to come across items like that when reviewing. However, with an item that in-depth, the documentation needs to be relatively matching. I look forward to approving your new template.

i walk bear footed (i hope that i said it correct ;))

Sure you did…

any documentation examples about, or is it expected to purchase a similar theme (in terms of feature set) to get a baseline?

7twelve said
any documentation examples about, or is it expected to purchase a similar theme (in terms of feature set) to get a baseline?

Purchasing a similar item is probably the best way to determine the baseline. Themeforest also offers a help doc template in HTML here: http://blog.themeforest.net/site-news/building-better-template-documentation/

7twelve said
any documentation examples about, or is it expected to purchase a similar theme (in terms of feature set) to get a baseline?

Please use our documentation template: http://enva.to/TFHelp

You can use a more creative design if you’d like but that template outlines the sections you should cover. Also, authors are expected to provide more information than just replacing the minimal examples in the documentation template. The template is just a starting point.

thanks much, will have a look still a few days away from my first submission, but want to get a solid grasp on the expectation

freshface said
Purchasing a similar item is probably the best way to determine the baseline.

I’d try to stay away from the idea of determining a baseline off other items. Template documentation is pretty simple really. Document the features, options, basic code layout, resources and credits.

You aren’t teaching buyers how to use HTML , CSS or JavaScript but instead providing some explanation as to how you’ve built the template, how to use odd or custom features, etc.

jremick said
@ Mark – Your admin template is pure awesome. It’s a pleasure to come across items like that when reviewing. However, with an item that in-depth, the documentation needs to be relatively matching. I look forward to approving your new template.

I totally agree whit you, i was thinking that my theme would be rejected because of the documents….......and dammmmm i was right lol

jremick said
@ Mark – Your admin template is pure awesome. It’s a pleasure to come across items like that when reviewing. However, with an item that in-depth, the documentation needs to be relatively matching. I look forward to approving your new template.

Thanks by the way!!

ps the theme is already uploaded so get to work