The following guidelines describe the requirements for ready to upload themes and templates. Failure to follow the guidelines will result in rejection or the need for re-submission after fixes are applied.
Requirements for HTML templates:
- Item must use the latest stable version of Bootstrap. Item cannot use work-in-progress or release candidate versions.
- Item must follow Bootstrap’s conventions for fundamental HTML elements and use the grid system.
- Item must not include pages based on Bootstrap’s example templates without sufficient modification.
- Files and directories must be treated as case-sensitive.
- Item must store styles and scripts in files separate from the Bootstrap assets.
- HTML must be valid HTML5 as determined by the W3C Markup Validation Service.
- Markup, styles, and scripts must not be obfuscated or encrypted.
- Item should make use of CSS pre-processors (LESS, SASS).
- Item must not include third-party plugins and components without sufficient modification to their appearance.
- Design must display high aesthetic quality, visual appeal, unique and should be attractive.
- Item cannot contain violent imagery, overly-sexualized imagery, nudity, racial slurs, hate speech, or otherwise inappropriate/offensive language.
Requirements for WordPress Themes:
- Themes must not contain unused code fragments (example: commented out code).
- In any way, themes must not hide or obfuscate code.
- Prefixes must follow the generally recommended standard described here.
- Don’t prefix or suffix 3rd-party styles/scripts.
- Themes are not allowed to use wp_ prefix.
- Prefixes must not start with a hyphen or underscore.
- When referring and including files, you must not use hard-coded URIs.
- WordPress helper functions should be used where possible.
- You must not combine 3rd-party libraries and scripts.
- Enqueue fonts using wp_enqueue_style() .
- If use Google Fonts, see this to learn the standard practices.
- Follow the standard WordPress and PHP coding practices.
- Follow the standard WordPress and HTML coding practices.
- Follow the standard WordPress and CSS coding practices.
- Follow WordPress internationalization standards if your theme offers multilingual features.
- Overall, you must follow standard WordPress theme development practices.
Name and Description Guidelines
Nymper encourages the authors to follow some best practices while naming a theme and writing its descriptions. The item name and description writing guidelines are as follows.
- Make it Clear: Your item name and description must make it clear what it is developed for. Minimum 10 and maximum 100 alphanumeric characters including ‘-‘, ‘,’ and ‘/’ are allowed in titles. Describe the item in a way that the buyer can easily understand whether the template will meet their needs.
- Good Title: The item name should be relevant, brief and professional. It will obviously create a good impression about your theme in the potential buyer’s mind. For example, “NewEdge – Modern HTML News/Magazine Template”.
- Proper Capitalization: Follow proper capitalization rules. Here are some examples.
- Best practice:“Template Title” – Use the capital form for the first letter of each word. You may use lowercase for words like “and”, “or”, “to”, “an” and so on if these are after the first word of the title.
- Wrong practice: “template title”: – Do not lowercase all the letters. It doesn’t go with a title.
- Follow industry standards: Use abbreviations, brand names etc. in native forms. Example – HTML, Bootstrap, CSS, AngularJS, jQuery.
- Avoid Over Promotion: Do not use self-opinions like “the best template”, “the only template” etc.
- Full Disclosure: Fully disclose the relevant facts about the item. If you use something in the demo which is not actually provided with the theme package, mention it in the documentation and description.
Hope this article provides sufficient information and explanation about our standard naming and description writing practices. If you have a question, please contact us.