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

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

テーマレビュー

提供: WordPress Codex 日本語版
2010年8月30日 (月) 06:43時点におけるBono (トーク | 投稿記録)による版 (リンク調整、ガイドテンプレ挿入、冒頭翻訳)

移動先: 案内、 検索

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

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

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 （最新版との差分）

「http://wpdocs.osdn.jp/wiki/index.php?title=テーマレビュー&oldid=4112」から取得