• 赤色のリンクは、まだ日本語Codexに存在しないページ・画像です。英語版と併せてご覧ください。(詳細

このWikiはいつでも誰でも編集できます

「テーマレビュー」の版間の差分

提供: WordPress Codex 日本語版
移動先: 案内検索
(原文英語版にリンク)
(リンク調整、ガイドテンプレ挿入、冒頭翻訳)
1行目: 1行目:
== Theme Review ==
+
{{テーマ・テンプレートガイド}}
 +
{{NeedTrans}}
 +
{{Rename|T}}
 +
 
 +
== Theme Review <!-- Theme Review -->==
 
<small>(Last Edited: '''{{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY}}''')</small>
 
<small>(Last Edited: '''{{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY}}''')</small>
  
 +
<!--
 
Anyone can [http://wordpress.org/extend/themes/upload/ submit] a GPL or compatible licensed WordPress Theme to the [http://wordpress.org/extend/themes/ WordPress Theme Directory]. Before new Themes are displayed publicly, they are reviewed by members of the WordPress community. This page describes the process, scope, and guidelines for Theme Reviewers in evaluation of submitted Themes. Note that this page is new as of June 2010, and that the process may change as it is still evolving.
 
Anyone can [http://wordpress.org/extend/themes/upload/ submit] a GPL or compatible licensed WordPress Theme to the [http://wordpress.org/extend/themes/ WordPress Theme Directory]. Before new Themes are displayed publicly, they are reviewed by members of the WordPress community. This page describes the process, scope, and guidelines for Theme Reviewers in evaluation of submitted Themes. Note that this page is new as of June 2010, and that the process may change as it is still evolving.
 +
-->
 +
[http://wordpress.org/extend/themes/ WordPressテーマディレクトリ]には、誰でもGPLまたは互換ライセンスのWordPressテーマを登録できます。新しいテーマは、公開する前にWordPressコミュニティのメンバーによって点検されます。このページでは、登録されたテーマの評価の過程と範囲、テーマ審査員向けガイドライン(指針)について説明します。
  
== Version Specific Changes ==
+
== Version Specific Changes <span id="Version_Specific_Changes"></span>==
  
 
Upon the release of each new version of WordPress, the Theme review process will be updated. To ensure newly submitted themes support current WordPress features and functionality, all Themes submitted one month after a new WordPress version must support the updated review criteria.
 
Upon the release of each new version of WordPress, the Theme review process will be updated. To ensure newly submitted themes support current WordPress features and functionality, all Themes submitted one month after a new WordPress version must support the updated review criteria.
  
See the list of [[Theme_Review/Version_Specific_Changes|WordPress version-specific theme review criteria changes]].
+
See the list of [[Theme Review/Version Specific Changes|WordPress version-specific theme review criteria changes]].
  
== The Theme Review Process and Scope ==
+
== The Theme Review Process and Scope <span id="The_Theme_Review_Process_and_Scope"></span>==
  
 
* The Theme directory is a repository of GPL (or compatible) licensed WordPress Themes. The review process, by community members, ensures Themes conform to modern web standards, WordPress standards, and are, in general, of high quality.
 
* The Theme directory is a repository of GPL (or compatible) licensed WordPress Themes. The review process, by community members, ensures Themes conform to modern web standards, WordPress standards, and are, in general, of high quality.
26行目: 33行目:
 
If you have any questions or suggestions about the process, don't hesitate to [http://wordpress.org/extend/themes/contact/ contact us]. Thank you for your contributions!
 
If you have any questions or suggestions about the process, don't hesitate to [http://wordpress.org/extend/themes/contact/ contact us]. Thank you for your contributions!
  
== Responding to a Review ==
+
== Responding to a Review <span id="Responding_to_a_Review"></span>==
 
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small>
 
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small>
  
42行目: 49行目:
 
* Guidelines are updated following a major WordPress version release  
 
* Guidelines are updated following a major WordPress version release  
  
=== Code Quality ===
+
=== Code Quality <span id="Code_Quality"></span>===
  
Review [[Theme Development]], [[WordPress Coding Standards]], [[CSS Coding Standards]], and [[Site Design and Layout]] for WordPress Theme code standards and best practices. Try to test your Theme [[CSS_Fixing_Browser_Bugs|across browsers]] to catch at least a few of the [[CSS_Troubleshooting|problems]] the users of the Theme may find later.
+
Review [[Theme Development]], [[WordPress Coding Standards]], [[CSS Coding Standards]]/[[:en:CSS Coding Standards|en]], and [[Site Design and Layout]] for WordPress Theme code standards and best practices. Try to test your Theme [[CSS Fixing Browser Bugs|across browsers]]/[[:en:CSS Fixing Browser Bugs|en]] to catch at least a few of the [[CSS Troubleshooting|problems]]/[[:en:CSS Troubleshooting|en]] the users of the Theme may find later.
  
 
* Themes are '''required''' not to have any notices, warnings, errors; or use of deprecated functions. Test using one of the following methods:
 
* Themes are '''required''' not to have any notices, warnings, errors; or use of deprecated functions. Test using one of the following methods:
60行目: 67行目:
 
** <nowiki><title></nowiki> includes <tt>bloginfo()</tt> for title and description, as appropriate
 
** <nowiki><title></nowiki> includes <tt>bloginfo()</tt> for title and description, as appropriate
  
=== Functionality ===
+
=== Functionality <span id="Functionality"></span>===
  
 
Theme is '''required''' to incorporate the following WordPress core functionality:
 
Theme is '''required''' to incorporate the following WordPress core functionality:
 
* Automatic Feed Links:
 
* Automatic Feed Links:
** <tt>[[Function_Reference/add_theme_support#Feed_Links|add_theme_support('automatic-feed-links’)]]</tt>
+
** <tt>[[関数リファレンス/add_theme_support#Feed_Links|add_theme_support('automatic-feed-links’)]]</tt>/[[:en:Function Reference/add_theme_support#Feed_Links|en]]
 
* Widgets:
 
* Widgets:
** <tt>[[Function_Reference/dynamic_sidebar|dynamic_sidebar()]]</tt>
+
** <tt>[[関数リファレンス/dynamic_sidebar|dynamic_sidebar()]]</tt>
** <tt>[[Function_Reference/register_sidebar|register_sidebar()]]</tt>
+
** <tt>[[関数リファレンス/register_sidebar|register_sidebar()]]</tt>
 
** <tt>add_action(widgets_init)</tt>, <tt>register_widget()</tt> (see [[Widgets API]]) – (if Theme uses custom widgets)  
 
** <tt>add_action(widgets_init)</tt>, <tt>register_widget()</tt> (see [[Widgets API]]) – (if Theme uses custom widgets)  
 
* Comments:  
 
* Comments:  
** <tt>[[Function_Reference/wp_list_comments|wp_list_comments()]]</tt>  
+
** <tt>[[テンプレートタグ/wp_list_comments|wp_list_comments()]]</tt>  
** <tt>[[Template_Tags/comment_class|comment_class()]]</tt> – (if using callback for [[Function_Reference/wp_list_comments|wp_list_comments()]])  
+
** <tt>[[テンプレートタグ/comment_class|comment_class()]]</tt>/[[:en:Template Tags/comment_class|en]] – (if using callback for [[テンプレートタグ/wp_list_comments|wp_list_comments()]])  
** <tt>[[Function_Reference/comment_form|comment_form()]]</tt>
+
** <tt>[[テンプレートタグ/comment_form|comment_form()]]</tt>
 
** <tt>[[Migrating_Plugins_and_Themes_to_2.7/Enhanced_Comment_Display#Javascript_Comment_Functionality|wp_enqueue_script( 'comment-reply' )]]</tt> in HTML document head <br /><small>'''(This criterion is a draft for review. Consider it as such until this notice is removed)'''</small>
 
** <tt>[[Migrating_Plugins_and_Themes_to_2.7/Enhanced_Comment_Display#Javascript_Comment_Functionality|wp_enqueue_script( 'comment-reply' )]]</tt> in HTML document head <br /><small>'''(This criterion is a draft for review. Consider it as such until this notice is removed)'''</small>
  
 
Theme is '''recommended''' to incorporate the following WordPress core functionality, but is ''not required'' to do so. However, if incorporated, functionality must support the core WordPress implementation:
 
Theme is '''recommended''' to incorporate the following WordPress core functionality, but is ''not required'' to do so. However, if incorporated, functionality must support the core WordPress implementation:
 
* Navigation Menus:
 
* Navigation Menus:
** <tt>[[Function_Reference/wp_nav_menu|wp_nav_menu()]]</tt>
+
** <tt>[[テンプレートタグ/wp_nav_menu|wp_nav_menu()]]</tt>
** <tt>[[Function_Reference/register_nav_menu|register_nav_menu()]]</tt> or <tt>[[Function_Reference/register_nav_menus|register_nav_menus()]]</tt> in ''functions.php''
+
** <tt>[[関数リファレンス/register_nav_menu|register_nav_menu()]]</tt>/[[:en:Function_Reference/register_nav_menu|en]] or <tt>[[関数リファレンス/register_nav_menus|register_nav_menus()]]</tt>/[[:en:Function_Reference/register_nav_menus|en]] in ''functions.php''
** The following functions may only be used for navigation menus as a callback to <tt>wp_nav_menu()</tt>, as part of a <tt>has_nav_menu()</tt> conditional, or similar:  <tt>[[Function_Reference/wp_list_pages|wp_list_pages]]</tt>, <tt>[[Template_Tags/wp_list_categories|wp_list_categories]]</tt>, <tt>[[Function_Reference/wp_page_menu|wp_page_menu]]</tt>, etc.
+
** The following functions may only be used for navigation menus as a callback to <tt>wp_nav_menu()</tt>, as part of a <tt>has_nav_menu()</tt> conditional, or similar:  <tt>[[テンプレートタグ/wp_list_pages|wp_list_pages]]</tt>, <tt>[[テンプレートタグ/wp_list_categories|wp_list_categories]]</tt>, <tt>[[テンプレートタグ/wp_page_menu|wp_page_menu]]</tt>, etc.
 
* Post Thumbnails:  
 
* Post Thumbnails:  
** <tt>[[Function_Reference/the_post_thumbnail|the_post_thumbnail()]]</tt>
+
** <tt>[[テンプレートタグ/the_post_thumbnail|the_post_thumbnail()]]</tt>
** <tt>[[Function_Reference/add_theme_support#Post_Thumbnails|add_theme_support('post-thumbnails’)]]</tt> in ''functions.php''
+
** <tt>[[Function_Reference/add_theme_support#Post_Thumbnails|add_theme_support('post-thumbnails’)]]</tt>/[[:en:Function_Reference/add_theme_support#Post_Thumbnails|en]] in ''functions.php''
 
* Custom Header:  
 
* Custom Header:  
** <tt>[[Function_Reference/add_custom_image_header|add_custom_image_header()]]</tt>
+
** <tt>[[Function_Reference/add_custom_image_header|add_custom_image_header()]]</tt>/[[:en:Function_Reference/add_custom_image_header|en]]
 
* Custom Background:  
 
* Custom Background:  
** <tt>[[Function_Reference/add_custom_background|add_custom_background()]]</tt>
+
** <tt>[[Function_Reference/add_custom_background|add_custom_background()]]</tt>/[[:en:Function_Reference/add_custom_background|en]]
 
* Visual Editor CSS:
 
* Visual Editor CSS:
** <tt>[[Function_Reference/add_editor_style|add_editor_style())]]</tt>
+
** <tt>[[Function_Reference/add_editor_style|add_editor_style())]]</tt>/[[:en:Function_Reference/add_editor_style|en]]
 
** ''editor-style.css'' file
 
** ''editor-style.css'' file
  
=== Template Tags and Hooks ===
+
=== Template Tags and Hooks <span id="Template_Tags_and_Hooks"></span>===
  
 
All template tags and hooks used in a Theme are '''required''' to be implemented properly.
 
All template tags and hooks used in a Theme are '''required''' to be implemented properly.
  
 
The following template tags and hooks are '''required''' to be included where appropriate:
 
The following template tags and hooks are '''required''' to be included where appropriate:
* <tt>[[Function_Reference/wp_head|wp_head()]]</tt> – (immediately before <nowiki></head></nowiki>)
+
* <tt>[[関数リファレンス/wp_head|wp_head()]]</tt>/[[:en:Function_Reference/wp_head|en]] – (immediately before <nowiki></head></nowiki>)
* <tt>[[Template_Tags/body_class|body_class()]]</tt> – (inside <nowiki><body></nowiki> tag)
+
* <tt>[[テンプレートタグ/body_class|body_class()]]</tt> – (inside <nowiki><body></nowiki> tag)
 
* <tt>$content_width</tt>
 
* <tt>$content_width</tt>
* <tt>[[Template_Tags/post_class|post_class()]]</tt>
+
* <tt>[[テンプレートタグ/post_class|post_class()]]</tt>/[[:en:Template_Tags/post_class|en]]
* <tt>[[Function_Reference/wp_link_pages|wp_link_pages()]]</tt>
+
* <tt>[[テンプレートタグ/wp_link_pages|wp_link_pages()]]</tt>
* <tt>[[Function_Reference/paginate_comments_links|paginate_comments_links()]]</tt>, or <tt>[[Function_Reference/previous_comments_link|previous_comments_link()]]</tt>/<tt>[[Function_Reference/next_comments_link|next_comments_link()]]</tt>
+
* <tt>[[テンプレートタグ/paginate_comments_links|paginate_comments_links()]]</tt>/[[:en:Function_Reference/paginate_comments_links|en]], or <tt>[[テンプレートタグ/previous_comments_link|previous_comments_link()]]</tt>/[[:en:Function_Reference/previous_comments_link|en]]/<tt>[[テンプレートタグ/next_comments_link|next_comments_link()]]</tt>/[[:en:Function_Reference/next_comments_link|en]]
* <tt>[[Function_Reference/wp_footer|wp_footer()]]</tt> – (immediately before <nowiki></body></nowiki>)
+
* <tt>[[関数リファレンス/wp_footer|wp_footer()]]</tt>/[[:en:Function_Reference/wp_footer|en]] – (immediately before <nowiki></body></nowiki>)
  
 
Standard template files, if incorporated into the Theme, are '''required''' to be called using the correct template tag:
 
Standard template files, if incorporated into the Theme, are '''required''' to be called using the correct template tag:
* Header: <tt>[[Function_Reference/get_header|get_header()]]</tt>
+
* Header: <tt>[[関数リファレンス/get_header|get_header()]]</tt>/[[:en:Function_Reference/get_header|en]]
* Sidebar: <tt>[[Function_Reference/get_sidebar|get_sidebar()]]</tt>
+
* Sidebar: <tt>[[関数リファレンス/get_sidebar|get_sidebar()]]</tt>/[[:en:Function_Reference/get_sidebar|en]]
* Footer: <tt>[[Function_Reference/get_footer|get_footer()]]</tt>
+
* Footer: <tt>[[関数リファレンス/get_footer|get_footer()]]</tt>/[[:en:Function_Reference/get_footer|en]]
* Comments: <tt>[[Function_Reference/comments_template|comments_template()]]</tt>
+
* Comments: <tt>[[関数リファレンス/comments_template|comments_template()]]</tt>/[[:en:Function_Reference/comments_template|en]]
* Search Form: <tt>[[Function_Reference/get_search_form|get_search_form()]]</tt>
+
* Search Form: <tt>[[関数リファレンス/get_search_form|get_search_form()]]</tt>/[[:en:Function_Reference/get_search_form|en]]
* Login Form: <tt>[[Function_Reference/wp_login_form|wp_login_form()]]</tt>
+
* Login Form: <tt>[[テンプレートタグ/wp_login_form|wp_login_form()]]</tt>
* Custom Theme template files: <tt>[[Function_Reference/get_template_part|get_template_part()]]</tt>
+
* Custom Theme template files: <tt>[[関数リファレンス/get_template_part|get_template_part()]]</tt>
 
* ''Note: <code>include( TEMPLATEPATH . '/file.php' )</code> should not be used to call Theme template part files, unless absolutely necessary.''
 
* ''Note: <code>include( TEMPLATEPATH . '/file.php' )</code> should not be used to call Theme template part files, unless absolutely necessary.''
  
 
Site information, if incorporated into the Theme, is '''required''' to be called using the correct template tag:<br />
 
Site information, if incorporated into the Theme, is '''required''' to be called using the correct template tag:<br />
<small>(This list is not exhaustive. Refer to <tt>[[Function_Reference/bloginfo|bloginfo()]]</tt> for the full list)</small><br />
+
<small>(This list is not exhaustive. Refer to <tt>[[テンプレートタグ/bloginfo|bloginfo()]]</tt> for the full list)</small><br />
 
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small>
 
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small>
* Home URL: <tt>[[Function_Reference/bloginfo|bloginfo( 'url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/home_url|home_url()]]</tt>''
+
* Home URL: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[テンプレートタグ/home_url|home_url()]]</tt>''
* WordPress URL: <tt>[[Function_Reference/bloginfo|bloginfo( 'wpurl' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/site_url|site_url()]]</tt>''
+
* WordPress URL: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'wpurl' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[テンプレートタグ/site_url|site_url()]]</tt>''
* Site Title: <tt>[[Function_Reference/bloginfo|bloginfo( 'name' )]]</tt>
+
* Site Title: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'name' )]]</tt>
* Site Description: <tt>[[Function_Reference/bloginfo|bloginfo( 'description' )]]</tt>
+
* Site Description: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'description' )]]</tt>
* Style Sheet Directory URL: <tt>[[Function_Reference/bloginfo|bloginfo( 'stylesheet_directory' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_stylesheet_directory|get_stylesheet_directory()]]</tt>''
+
* Style Sheet Directory URL: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'stylesheet_directory' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_stylesheet_directory|get_stylesheet_directory()]]</tt>''/[[:en:Function_Reference/get_stylesheet_directory|en]]
* Style Sheet URL: <tt>[[Function_Reference/bloginfo|bloginfo( 'stylesheet_url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_stylesheet_uri|get_stylesheet_uri()]]</tt>''
+
* Style Sheet URL: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'stylesheet_url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_stylesheet_uri|get_stylesheet_uri()]]</tt>''/[[:en:Function_Reference/get_stylesheet_uri|en]]
* Parent Theme Directory URL: <tt>[[Function_Reference/bloginfo|bloginfo( 'template_directory' )]]</tt> or <tt>[[Function_Reference/bloginfo|bloginfo( 'template_url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_template_directory|get_template_directory()]]</tt>''
+
* Parent Theme Directory URL: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'template_directory' )]]</tt> or <tt>[[テンプレートタグ/bloginfo|bloginfo( 'template_url' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_template_directory|get_template_directory()]]</tt>''/[[:en:Function_Reference/get_template_directory|en]]
* Parent Theme Name: <tt>[[Function_Reference/get_template|get_template()]]</tt>
+
* Parent Theme Name: <tt>[[Function_Reference/get_template|get_template()]]</tt>/[[:en:Function_Reference/get_template|en]]
* Character Set: <tt>[[Function_Reference/bloginfo|bloginfo( 'charset' )]]</tt>
+
* Character Set: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'charset' )]]</tt>
* HTML type: <tt>[[Function_Reference/bloginfo|bloginfo( 'html_type' )]]</tt>
+
* HTML type: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'html_type' )]]</tt>
* Language: <tt>[[Function_Reference/bloginfo|bloginfo( 'language' )]]</tt> (en-US) or <tt>[[Function_Reference/get_template|get_locale()]]</tt> (en_US)
+
* Language: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'language' )]]</tt> (en-US) or <tt>[[Function_Reference/get_locale|get_locale()]]</tt>/[[:en:Function_Reference/get_locale|en]] (en_US)
* Text Direction: <tt>[[Function_Reference/bloginfo|bloginfo( 'text_direction' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/is_rtl|is_rtl()]]</tt> <small>for conditional statements</small>''
+
* Text Direction: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'text_direction' )]]</tt><br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/is_rtl|is_rtl()]]</tt>/[[:en:Function_Reference/is_rtl|en]] <small>for conditional statements</small>''
* WordPress Version: <tt>[[Function_Reference/bloginfo|bloginfo( 'version' )]]</tt>
+
* WordPress Version: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'version' )]]</tt>
* Feed Links: <tt>[[Function_Reference/bloginfo|bloginfo( 'feed_url' )]]</tt> (where <tt>feed_url</tt> is <tt>rss_url</tt>, <tt>rss2_url</tt>, <tt>atom_url</tt>)<br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[Function_Reference/get_feed_link|get_feed_link( 'feed' )]] (where <tt>feed</tt> is <tt>rss</tt>, <tt>rss2</tt>, <tt>atom</tt>)''
+
* Feed Links: <tt>[[テンプレートタグ/bloginfo|bloginfo( 'feed_url' )]]</tt> (where <tt>feed_url</tt> is <tt>rss_url</tt>, <tt>rss2_url</tt>, <tt>atom_url</tt>)<br /><small>''Note: Themes are '''recommended''' to use</small> <tt>[[テンプレートタグ/get_feed_link|get_feed_link( 'feed' )]]/[[:en:Function_Reference/get_feed_link|en]] (where <tt>feed</tt> is <tt>rss</tt>, <tt>rss2</tt>, <tt>atom</tt>)''
 +
 
 +
=== WordPress-Defined CSS Classes <span id="WordPress-Defined_CSS_Classes"></span>===
  
=== WordPress-Defined CSS Classes ===
+
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small><br />Themes are '''required''' to support the following [[CSS#WordPress_Generated_Classes|WordPress-defined CSS classes]]/[[:en:CSS#WordPress_Generated_Classes|en]], or similar elements:
<small>'''Note: this section is currently being drafted. Consider it as such until this notice is removed.'''</small><br />Themes are '''required''' to support the following [[CSS#WordPress_Generated_Classes|WordPress-defined CSS classes]], or similar elements:
+
 
* Alignment Classes:
 
* Alignment Classes:
 
** <tt>.aligncenter, div.aligncenter</tt>
 
** <tt>.aligncenter, div.aligncenter</tt>
149行目: 157行目:
 
** <tt>.bypostauthor</tt>
 
** <tt>.bypostauthor</tt>
  
=== Theme Template Files ===
+
=== Theme Template Files <span id="Theme_Template_Files"></span>===
  
 
Theme is '''required''' to include, at a minimum:
 
Theme is '''required''' to include, at a minimum:
185行目: 193行目:
 
<small>Note: The reason to avoid this template naming convention for publicly released Themes is to avoid surprising users that create a page with the "-foobar" slug and expect the default template. See [[Template_Hierarchy#Page_display]].</small>
 
<small>Note: The reason to avoid this template naming convention for publicly released Themes is to avoid surprising users that create a page with the "-foobar" slug and expect the default template. See [[Template_Hierarchy#Page_display]].</small>
  
=== Licensing ===
+
=== Licensing <span id="Licensing"></span>===
  
 
* License:
 
* License:
238行目: 246行目:
 
** [http://www.iconfinder.com/search/?q=iconset:oxygen Oxygen] (GPL)
 
** [http://www.iconfinder.com/search/?q=iconset:oxygen Oxygen] (GPL)
  
=== Theme Documentation ===
+
=== Theme Documentation <span id="Theme_Documentation"></span>===
  
 
Please be clear about the following in your Theme documentation (a README file included with your Theme helps many users over any potential stumbling blocks):
 
Please be clear about the following in your Theme documentation (a README file included with your Theme helps many users over any potential stumbling blocks):
245行目: 253行目:
 
# Adhere to the naming conventions of the standard Theme hierarchy.
 
# Adhere to the naming conventions of the standard Theme hierarchy.
 
# Indicate deficiencies in your Themes, if any.
 
# Indicate deficiencies in your Themes, if any.
# Clearly reference any special modifications in [[Commenting_Code|comments]] within the template and stylesheet files. Add comments to modifications, template sections, and CSS styles, especially those which cross template files.  
+
# Clearly reference any special modifications in [[Commenting Code|comments]]/[[:en:Commenting_Code|en]] within the template and stylesheet files. Add comments to modifications, template sections, and CSS styles, especially those which cross template files.  
 
# If you have any special requirements, which may include custom Rewrite Rules, or the use of some additional, special templates, images or files, please explicitly state the steps of action a user should take to get your Theme working.
 
# If you have any special requirements, which may include custom Rewrite Rules, or the use of some additional, special templates, images or files, please explicitly state the steps of action a user should take to get your Theme working.
 
# Provide contact information (website or email), if possible, for support information and questions.
 
# Provide contact information (website or email), if possible, for support information and questions.
  
=== Credit links ===
+
=== Credit links <span id="Credit_links"></span>===
 
* Themes may '''optionally''' designate Author URI and Theme URI in style.css.  
 
* Themes may '''optionally''' designate Author URI and Theme URI in style.css.  
 
** Theme URI, if used, is '''required''' to link to a page specifically related to the Theme.  
 
** Theme URI, if used, is '''required''' to link to a page specifically related to the Theme.  
261行目: 269行目:
 
* Since Themes are GPL (or compatible), Theme authors are prohibited from requiring that these links be kept by Theme users. An appropriate way to ask for Theme users to keep a link to the author's website is as follows: "It is completely optional, but if you like the Theme I would appreciate it if you keep the credit link at the bottom."
 
* Since Themes are GPL (or compatible), Theme authors are prohibited from requiring that these links be kept by Theme users. An appropriate way to ask for Theme users to keep a link to the author's website is as follows: "It is completely optional, but if you like the Theme I would appreciate it if you keep the credit link at the bottom."
  
=== Theme Unit Tests ===
+
=== Theme Unit Tests <span id="Theme_Unit_Tests"></span>===
  
 
The Theme must meet all the requirements of the [[Theme Unit Test]].
 
The Theme must meet all the requirements of the [[Theme Unit Test]].
  
== Theme Obsolescence ==
+
== Theme Obsolescence <span id="Theme_Obsolescence"></span>==
  
 
* Themes must be kept current once submitted.
 
* Themes must be kept current once submitted.
 
* Any Theme not updated to the current theme review process as of the most recent release of WordPress may be subject to temporary suspension.
 
* Any Theme not updated to the current theme review process as of the most recent release of WordPress may be subject to temporary suspension.
  
== How To Become a Theme Reviewer ==
+
== How To Become a Theme Reviewer <span id="How_To_Become_a_Theme_Reviewer"></span>==
  
 
Are you interested in joining the Theme Reviewers team? Great! The team is open to anyone who wants to help out, and the process is simple:
 
Are you interested in joining the Theme Reviewers team? Great! The team is open to anyone who wants to help out, and the process is simple:
283行目: 291行目:
 
# Set the “resolve as” option to “suggest-approval” for inclusion in the Theme directory; or, “not-accepted” if the Theme does not meet the necessary review criteria and standards.
 
# Set the “resolve as” option to “suggest-approval” for inclusion in the Theme directory; or, “not-accepted” if the Theme does not meet the necessary review criteria and standards.
  
== Resources ==
+
== Resources <span id="Resources"></span>==
  
=== Helpful Codex Links ===
+
=== Helpful Codex Links <span id="Helpful_Codex_Links"></span>===
  
 
* [[Theme Development]]
 
* [[Theme Development]]
291行目: 299行目:
 
* [[Theme Unit Test]]
 
* [[Theme Unit Test]]
 
* [[WordPress Coding Standards]]
 
* [[WordPress Coding Standards]]
* [[CSS Coding Standards]]
+
* [[CSS Coding Standards]] /[[:en:CSS Coding Standards|en]]
 
* [[Site Design and Layout]]
 
* [[Site Design and Layout]]
* [[CSS Fixing Browser_Bugs]]
+
* [[CSS Fixing Browser_Bugs]] /[[:en:CSS Fixing Browser_Bugs|en]]
* [[CSS Troubleshooting]]
+
* [[CSS Troubleshooting]] /[[:en:CSS Troubleshooting|en]]
  
=== Code Validation Links ===
+
=== Code Validation Links <span id="Code_Validation_Links"></span>===
  
 
* [http://validator.w3.org/unicorn/ W3C XHTML+CSS Validator (Unicorn)]
 
* [http://validator.w3.org/unicorn/ W3C XHTML+CSS Validator (Unicorn)]
302行目: 310行目:
 
* [http://jigsaw.w3.org/css-validator/ W3C CSS Validator]
 
* [http://jigsaw.w3.org/css-validator/ W3C CSS Validator]
  
=== PHP/WordPress Validation Tools ===
+
=== PHP/WordPress Validation Tools <span id="PHP.2FWordPress_Validation_Tools"></span>===
  
 
* [http://www.wordpress.org/extend/plugins/log-deprecated-notices/ Log Deprecated Notices plugin] (Logs notices of deprecated WordPress functions found in Themes/Plugins)
 
* [http://www.wordpress.org/extend/plugins/log-deprecated-notices/ Log Deprecated Notices plugin] (Logs notices of deprecated WordPress functions found in Themes/Plugins)

2010年8月30日 (月) 06:43時点における版

このページ「テーマレビュー」は未翻訳です。和訳や日本語情報を加筆してくださる協力者を求めています

ページ名検討中: このページ名「テーマレビュー」について改名が提案されています。ご意見をお寄せください。

Theme Review

(Last Edited: 2010-08-30)

WordPressテーマディレクトリには、誰でもGPLまたは互換ライセンスのWordPressテーマを登録できます。新しいテーマは、公開する前にWordPressコミュニティのメンバーによって点検されます。このページでは、登録されたテーマの評価の過程と範囲、テーマ審査員向けガイドライン(指針)について説明します。

Version Specific Changes

Upon the release of each new version of WordPress, the Theme review process will be updated. To ensure newly submitted themes support current WordPress features and functionality, all Themes submitted one month after a new WordPress version must support the updated review criteria.

See the list of WordPress version-specific theme review criteria changes.

The Theme Review Process and Scope

  • The Theme directory is a repository of GPL (or compatible) licensed WordPress Themes. The review process, by community members, ensures Themes conform to modern web standards, WordPress standards, and are, in general, of high quality.
  • Once a Theme author is ready to release a Theme to the public, they can upload it to the directory system. Be sure your Theme meets the Guidelines below, and test your theme with the Theme Unit Test before you upload your Theme.
  • Submitted Themes are automatically checked to make sure they meet a few basic requirements.
  • Theme authors receive an automated e-mail message, indicating that their Theme files have been received.
  • Submitted Themes are assigned a ticket in the Theme Review Trac system, and entered into a review queue.
  • Theme reviewers test Themes, using the method described below.
  • While the goal of the design review is to ensure that Themes are functional and meet standards much of the review will surround technical issues. Themes will be checked for other factors, such as ensuring that all standards are met to a satisfactory standard, and that designs are logical, and user-friendly.
  • Theme reviewers will provide feedback to Theme authors in a timely manner; and, Theme authors will have the opportunity to revise their Themes at any time.
  • Theme reviewers will either approve Themes or contact Theme authors with feedback and/or questions.
  • Theme authors can submit any changes via the upload page they used when they initially uploaded the Theme, either before or after a Theme has been approved.
  • If a Theme is not initially approved, Theme authors can rework the Theme and resubmit it.

If you have any questions or suggestions about the process, don't hesitate to contact us. Thank you for your contributions!

Responding to a Review

Note: this section is currently being drafted. Consider it as such until this notice is removed.

A theme will be held for approval until items listed as Required are addressed. Once these issues have been resolved, please re-submit your Theme using the uploader tool, a new Trac ticket will be generated. Also note, re-submitted Themes are given priority over newly submitted Themes to help speed up the process and insure timely updates are available to end-users.

Theme developer questions, comments, and feedback are always welcome ... and encouraged!
Please use one of the following methods:

  • Leave a comment on the appropriate Trac ticket(s) related to the theme;
  • Email the theme-reviewers email list (you may need to join first); or,
  • Use the #wp-themes channel on irc.freenode.net where you can find the Theme Review team.

Guidelines

  • Themes must meet guidelines current as of the time of Theme submission
  • Guidelines are updated following a major WordPress version release

Code Quality

Review Theme Development, WordPress Coding Standards, CSS Coding Standards/en, and Site Design and Layout for WordPress Theme code standards and best practices. Try to test your Theme across browsers/en to catch at least a few of the problems/en the users of the Theme may find later.

  • Themes are required not to have any notices, warnings, errors; or use of deprecated functions. Test using one of the following methods:
  • Themes are required to utilize current recognized version(s) of (X)HTML and CSS. Test using one of the following methods:
  • Themes are required to generate no JavaScript errors
  • Themes are required to have a valid HTML document HEAD:
    • Valid DOCTYPE declaration
    • <html> tag includes language_attributes()
    • Correct XFN profile link in <head> tag: <head profile="http://gmpg.org/xfn/11">
    • Correct content-type meta declaration: <meta http-equiv="Content-Type" content="<?php bloginfo('html_type'); ?>; charset=<?php bloginfo('charset'); ?>" /> OR <meta charset=<?php bloginfo('charset'); ?> declared before <title>
    • <title> includes bloginfo() for title and description, as appropriate

Functionality

Theme is required to incorporate the following WordPress core functionality:

Theme is recommended to incorporate the following WordPress core functionality, but is not required to do so. However, if incorporated, functionality must support the core WordPress implementation:

Template Tags and Hooks

All template tags and hooks used in a Theme are required to be implemented properly.

The following template tags and hooks are required to be included where appropriate:

Standard template files, if incorporated into the Theme, are required to be called using the correct template tag:

Site information, if incorporated into the Theme, is required to be called using the correct template tag:
(This list is not exhaustive. Refer to bloginfo() for the full list)
Note: this section is currently being drafted. Consider it as such until this notice is removed.

WordPress-Defined CSS Classes

Note: this section is currently being drafted. Consider it as such until this notice is removed.
Themes are required to support the following WordPress-defined CSS classes/en, or similar elements:

  • Alignment Classes:
    • .aligncenter, div.aligncenter
    • .alignleft
    • .alignright
  • Caption Related Classes:
    • .wp-caption
    • .wp-caption img
    • p.wp-caption-text

Themes should also support these common classes:

  • Post Classes:
    • .sticky
  • Comment Classes:
    • .bypostauthor

Theme Template Files

Theme is required to include, at a minimum:

  • index.php
  • screenshot.png (this should be a "reasonable facsimile" of the Theme after it is initially activated with default options)
  • style.css

Theme is recommended to include:

  • 404.php
  • archive.php
  • comments.php
  • footer.php
  • header.php
  • page.php
  • search.php
  • sidebar.php (or appropriate variations such as: sidebar-left.php; sidebar-right.php; sidebar-footer.php; etc.)
  • single.php

Theme may optionally include:

  • attachment.php
  • author.php
  • category.php
  • date.php
  • editor-style.css
  • image.php
  • tag.php

Submitted theme are required not to include files named like the following:

  • page-foobar.php
  • category-foobar.php
  • tag-foobar.php
  • taxonomy-foobar.php

Note: The reason to avoid this template naming convention for publicly released Themes is to avoid surprising users that create a page with the "-foobar" slug and expect the default template. See Template_Hierarchy#Page_display.

Licensing

  • License:
    • Themes, including all PHP, HTML, CSS, images, fonts, and icons, are required to be 100% GPL-licensed, or use a GPL-compatible license.
    • Themes are required to declare their license explicitly, using one of the following methods:
      • Adding License and License URI header slugs to style.css
      • Including a license.txt file with the Theme
    • Use this formatting for license information as in this example:
License: GNU General Public License v2.0
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Theme Documentation

Please be clear about the following in your Theme documentation (a README file included with your Theme helps many users over any potential stumbling blocks):

  1. Indicate precisely what your Theme and template files will achieve.
  2. Adhere to the naming conventions of the standard Theme hierarchy.
  3. Indicate deficiencies in your Themes, if any.
  4. Clearly reference any special modifications in comments/en within the template and stylesheet files. Add comments to modifications, template sections, and CSS styles, especially those which cross template files.
  5. If you have any special requirements, which may include custom Rewrite Rules, or the use of some additional, special templates, images or files, please explicitly state the steps of action a user should take to get your Theme working.
  6. Provide contact information (website or email), if possible, for support information and questions.

Credit links

  • Themes may optionally designate Author URI and Theme URI in style.css.
    • Theme URI, if used, is required to link to a page specifically related to the Theme.
    • Author URI, if used, is required to link to an author's personal web site or project/development website.
    • Themes are recommended to provide at least one of these two links, in order to ensure Theme users have a point of contact for the Theme developer.
  • Themes may optionally include a public-facing credit link in the Theme footer.
    • If used, Themes are required to include no more than one such footer credit link.
    • Footer credit link, if used, is required to use either Theme URI or Author URI.
    • Any exception to these requirements must be approved by the Theme Review team.
  • In all cases, credit link anchor text and title are required to be accurate, appropriate with respect to the linked site. SEO-seeded anchor text and titles will subject Themes to automatic rejection.
  • Since Themes are GPL (or compatible), Theme authors are prohibited from requiring that these links be kept by Theme users. An appropriate way to ask for Theme users to keep a link to the author's website is as follows: "It is completely optional, but if you like the Theme I would appreciate it if you keep the credit link at the bottom."

Theme Unit Tests

The Theme must meet all the requirements of the Theme Unit Test.

Theme Obsolescence

  • Themes must be kept current once submitted.
  • Any Theme not updated to the current theme review process as of the most recent release of WordPress may be subject to temporary suspension.

How To Become a Theme Reviewer

Are you interested in joining the Theme Reviewers team? Great! The team is open to anyone who wants to help out, and the process is simple:

  1. Join the Theme Reviewers mail list.
  2. Setup a WordPress test environment, and import the Theme Unit Test data. Be sure to set WP_DEBUG to 'true' in wp-config.
  3. Install the Log Deprecated Notices plugin on your WordPress test environment.
  4. Pick the oldest unclaimed Theme from the Theme Review Trac Queue; and, "reassign to" your Trac username
  5. Using the SVN link in the Trac ticket, download the Theme files, and install/activate the Theme on your WordPress test environment.
  6. Review the Theme per the process, ensuring the Theme meets the criteria as well as the Theme Development standards.
  7. Attach your Theme review notes as a comment on the ticket.
  8. Set the “resolve as” option to “suggest-approval” for inclusion in the Theme directory; or, “not-accepted” if the Theme does not meet the necessary review criteria and standards.

Resources

Helpful Codex Links

Code Validation Links

PHP/WordPress Validation Tools

最新英語版: WordPress Codex » Theme Review最新版との差分