Before submitting your first template to WPBay, consider the following factors, which frequently contribute to rejected submissions. Please note that this list should only be used only as a guideline.

Documentation

Every template on WPBay should include documentation to make the installation process as simple as possible for the purchaser. While you don’t have to teach the reader how to code, you should absolutely discuss any unique aspects of your template, which require further explanation.

Typography

• Line-Height – Generally, a line-height of 1.3-1.6em (depending on font size and usage) is most appropriate. While this isn’t set in stone, make sure that you have a specific reason to choose beyond this range.
• Visual Hierarchy – We recommend that designers research this topic and spend time refining your skills in this area. It will dramatically help your template aesthetics.
• Text Alignment – Though we don’t generally reject templates specifically for text alignment, if it seriously contributes to poor aesthetics, we will. Justified alignment on the web should be used appropriately, though it’s unfortunately often misused.

Validation

There is no reason your template should have unnecessary validation errors, unless you happen to be working within the confines of a particular CMS or framework which limits your control over the code output. HTML5 and CSS3 “errors” will not count against your template, so feel free to progressively enhance as much as you wish! With all that said, ALWAYS validate before submitting.

Lacking Code Quality

• Poor List Mark-up – A list of links should be written with the link elements, not a series of anchor tags. This is called semantics, and is essential to your upload. A general rule of thumb is: if you would describe a particular section of your mark-up as a list of links, images, advertisements, etc., then you should appropriately use a “ul,” “ol,” or “dl.”
• List Separators – Do not separate links with the ”|” character. This is bad form, and should instead be accomplished with CSS.
• Browser Testing – Have you tested your design in IE6 (optional), IE7, IE8, Firefox, Safari, Chrome, and Opera? While we do allow for alternative displays for older browsers – think simplified layout for IE6 users – your design must not break in any of these. If they do, your item will be rejected, with a request from the reviewer to make the necessary updates.