Product Quality and Functionality Issues
Use of inline CSS style is prohibited.
CSS file is poorly documented. Divide a CSS file into logical blocks, title them, and add a table of contents.
CSS specificity. You need to enhance CSS specificity and avoid “!important”.
Make sure the CSS file is well documented with a proper table of contents.
The source files CSS and JS should be included in the product archive. The end-users should have the opportunity to customize the code of the template, so the code could be readable and editable.
Minification and obfuscation can be applied to the product demo, but in the product archive the source files are required. The end-users should be given an opportunity to edit the code in accordance with their needs.
Use local files for jQuery instead of CDN.
The template should be built with valid HTML. Follow this link to check Markup Validation Service – https://validator.w3.org/
Make sure that the code is properly formatted and is easy to read.
The code should be correctly indented and that it’s consistent with the use of spaces or tabs for indentation of the code. We do not give preference to any, but we need the author to pick one and use it for all the code.
Scripts and styles should not be hardcoded anywhere in your theme.
Please make sure your theme doesn’t raise any errors or warnings in the console.
The localization file should be in English.
Translate all strings within the PHP variable and escape where needed.
The template’s functionality can be established within the template’s source files or can be applied as plugins. Both cases are acceptable, but should be described in the product documentation.
Best coding practices:
Using HTTPS (SSL) for the product Live Demo is strongly recommended.
Please add a good Demo Importer (One Click Demo Import or All-in-One WP Migration), that will guarantee a complete design coincidence with your Demo (all blocks, sliders, menus, shortcodes etc.). And pay attention that the template must look exactly the same as the demo theme.
Please make sure that Contact form is working and include necessary scripts/files to send out emails. Otherwise, the product’s demo is misleading and customers can request a refund due to the lack of functionality.
Do not use ‘target=”_blank”‘ links in your Live Demo (Shopify Splash Page is an exception).
The usage of third-party plugins, modules and extensions is welcomed, but it should be included to the product archive and described in the documentation.
If the author includes the third-party software to the product, the author is supposed to guarantee the compatibility of the product and third-party software.
If the author has no appropriate license to use the third-party software and yet includes it to the product archive, the author will be responsible for copyright infringement in case of escalations.
PSD version of the product is not mandatory for website, CMS and E-Commerce products.
Please make sure to declare cross-browser compatibility in the product description and documentation.
The template layout must be responsive and consistent with any screen resolution.
10 Things to Note for Developing Responsive Websites
Responsive Website Coding: Cheat Sheet
Please use the latest version of the software (engine, plugins, modules etc.,) and update your product regularly to keep it fit current versions. Otherwise, the template can be declined or removed from sale as an outdated product.