Wordpress Theme GuidelinesWorldpress Theme Guidelines
Handbook for topic developers
Ambassadors from all over the globe are willing to help you develop your theme. Be sure to read the topic validation guidelines before you upload a topic. When you have a question about these guidelines, you can post it in the #themereview in Slack. Please test your design with these example files before you upload it for verification.
If you are willing to post your topic for consideration, please post your topic in your forum under Topics > Post. For more information about the topic validation procedure, visit the Theme review team website. Whether your design is accepted or awaiting verification when you download a design upgrade, just increment the release within style.css and download themename.zip again, just as you would for a new design.
As your release increases, the queuing location of your design DOES NOT move (if you are still awaiting review).
topic evaluation team
Topics that have 3 or more different problems can be concluded as not authorized. Topic writers can, however, re-submit the topic once they have resolved the issue. Together with these tests, you should also run the theme through the Theme-Check Plugin. When the topic has the day "barrier-free", then it must fulfil these demands.
If you have a DOCTYPE statement that is effective, enclose language_attributes. Offer a clear and unambiguous preferred for everything that the theme specifies in the common name space, plus choices, features, global variable, constant, post-meta, etc. The exception are the positions of the topic's navigation menus and the side bar identifiers. To change the contents, do not use harsh encodings. Topic tag styles. bss and descriptions must correspond to what the theme actually does in terms of function and appearance.
Do not use more than 3 subj topic tags (see: Theme Tags List). Correctly use templates labels and action/filter hook. Insert comment. Php (via comments_template())). Topics should not delete, conceal or otherwise prevent the administration panel from being displayed. Topic settings should not be bogus user-defined mail type and should store non-trivial credentials.
Trial contents can be used to show the users how the settings work. Instead of placeholders, use startup contents, available contents, or install directives. Explain any functions, template, options and/or constraints (e.g. menus) you may have. Texts for all topics should be translated. Insert a textdomain into style.css.
Only use one, unambiguous theme snail - because the theme snail will appear in style.css. Every declaration of copyrights on the frontend should indicate the copyrights of the users and not the copyrights of the topic authors. Topic name may not be used: Subordinate topics should not contain the name of the superordinate topic unless the topics have the same auteur.
Store the settings in a unique group. You can use the function edit_theme_options to define the user's authorization to modify settings instead of relying on a specific function (e.g. "Administrator") or another function (e.g. "edit_themes", "manage_options"). Topics must not contain plug-ins. Topics may not need plug-ins to work. Topics can contain library such as optional framework (these must meet the requirements).
It should be an appropriate illustration of how the topic might look like. As an option, the above image can show plug-ins, preferences and template support. Screen shots may only show text that does not suggest or describe any topic characteristics, functions or stats. Text that does not describe your topic, your business, your services, or your product.
Perform a collect only " Opt-in " session of users and have a topic item turned off by setting it to Off by preference. URL abbreviations are not used in the design. The topic URI is optionally available. When the URI is a demonstration site, the contents must be the topic itself and not test files.
Authors' URI is optionally available. When using it is necessary to refer to a page or website about the writer, the writer theme store or the website of the writer project/development. Subjects can have a unique subline credits hyperlink limited to the theme URI or authors' URI specified in style.css. The topics should not be "intrusive" up-selling.
Incorporate all scripting and resource it uses instead of using hotlinks. When used in the theme, default artwork must be invoked by their corresponding function: headers. php script (via get_header()). footers. php script (via get_footer()). side _bar. php script in ( via get_sidebar()). seekform. php script in ( via get_search_form()). seekform. php script in (). When you use the appropriate style sheets, your design should contain the following: wp_head() - (just before ). body_class() - (inside tag).
In addition to the articles you need, you should also consider the articles you recommend. Suggested elements are there to ensure that your topic is the best it can be, and good suggestions that are accepted as best practices.