Submission Guidelines

• Themes will be tested against the WordPress Unit Test data to ensure that all necessary components are styled properly.
• Posts must be displayed correctly with no apparent visual problems.
• All expected components, such as title, body, comments, comment form, post meta, etc., must be rendered correctly.
• Posts must be displayed in the correct order.
• Page navigation must work correctly.
• The search results page must work properly, with results displayed appropriately. If there are no results the user must be informed of this.
• Sticky posts must be styled and displayed appropriately.
• The Read More link must work properly (linking to the <!–more–> tag location).
• If the theme supports post formats, each type must be displayed appropriately in index/archive views.
• Lack of content, such as body text, must not adversely impact the layout.
• Themes must include both the Tag and the Category taxonomies in some manner.
• Floats must be cleared properly for the floated element, that is, thumbnail images.
• Content overflow issues must be addressed. For example, a title with a long non-breaking string must not break the layout.

Licenses:

• Make sure you have the correct licenses for any assets you have included in your item. This includes assets that are in your Item Preview only; you will still need a commercial license for preview assets.
• For these assets, you will need to ensure you have a commercial redistribution license (the rights to re-sell that asset).
• Check if any of the assets you have used require attribution

Developer Licenses:

• In case of owning a developer license for a specific theme or plugin required from Template and installed, please ensure this is mentioned clear on the assets provided together with the Template.

• Check that your item does not contain any malware or viruses.
• We take security very seriously, and may need to take action such as removing items or accounts and contacting affected customers if viruses or malicious software is found in your item.

Every item in InstaWP requires a basic documentation file to help customers use your item. This should include:

• Concise instructions on installation, customization and use
• General instructions or further information
• Details and links to assets used that you need to credit
• The documentation should be written in English and formatted as a .pdf or HTML document.
• You may create a screencast or flash instructions in addition to, but not instead of, text instructions.

• You won’t need to enter the title until you upload your item, but there are important rules to think about.
• Your title is the first thing a potential buyer sees, so it’s important to be informative, concise and professional. Include the most relevant information only; a title made up of vague advertising buzzwords is less effective than one that is clear and descriptive.
• You must specify in your title the theme that the template is based on.
• Unique item titles that are easy to remember are more effective in creating a brand. For newly published Items, you must include your brand name at the beginning of your item title.
• For example, “Gutena” is the brand name and, “Gutena | A Block Theme Built for Speed and Functionality” is the full title.

• Select the most appropriate category that accurately represents your product’s purpose or functionality.
• Avoid selecting misleading categories that do not accurately reflect your product’s attributes.

• Include high-quality images or screenshots showcasing your product’s user interface, design, or key features.
• Use clear and visually appealing images that accurately represent the actual appearance of your product.
• Maximum 5MB file size.
• Must be in the PNG, JPG, format.
• Recommended images size in a 4:3 aspect ratio.

• Write a comprehensive and concise product description that highlights its key features, benefits, and use cases.
• Include any relevant documentation or user guides to assist users in understanding and utilizing your product effectively.
• Clearly specify any requirements or dependencies for proper installation, configuration, or usage.

• Ensure that your product submission adheres to all applicable laws, regulations, and copyright restrictions.
• Do not infringe upon the intellectual property rights of others, including trademarks, logos, or copyrighted material.
• Clearly state any licenses, permissions, or usage rights associated with your product, if applicable.

• Provide information on how users can seek support or assistance regarding your product.
• Specify if your product includes ongoing updates, bug fixes, or additional features in the future.
• Include contact details in your documentation where users can reach out for any queries or issues.