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

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

テーマレビュー

提供: WordPress Codex 日本語版
2010年9月1日 (水) 06:23時点におけるBono (トーク | 投稿記録)による版 (最新に更新、一部和訳 (継続作業予定。文言の調整を一通り終了後に行ないます))

移動先: 案内検索

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

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

Theme Review

(Last Edited: 2010-09-1)

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

各バージョンの変更点

WordPressの各新バージョンの公開により、テーマ審査工程が更新されます。新たに登録されたテーマの最新WordPress特性・機能対応を確実にするには、WordPress新バージョンの一箇月以降に登録されるテーマは全て、更新後の審査基準に対応していなければなりません。

WordPressバージョン別テーマ審査基準変更点の一覧を参照してください。

テーマ審査工程と範囲

  • 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 to ensure 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.

ガイドライン(指針)

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

コード品質

WordPressテーマの標準的な書き方や最良の方法については、テーマ開発およびWordPressコーディング基準CSSコーディング基準/enサイトのデザインとレイアウトを見直してください。

  • テーマは、通知・警告・エラーがないこと、非推奨(廃止予定の)関数が使われていないことが必須です。以下の手法の一つを用いてテストしてください。
  • 広く認められている最新(現行?)バージョンの(X)HTMLおよびCSSを利用することが必須です。(訳注: 翻訳が間違っているかもしれません。原文 "current recognized version(s) of (X)HTML and CSS")
  • JavaScriptエラーが発生しないことが必須です。
  • 有効なHTMLドキュメント HEAD が必須です。
    • 有効なDOCTYPE宣言
    • <html> タグに language_attributes()/en が入っていること
    • <head> タグ内の正しいXFNプロファイルリンク: <head profile="http://gmpg.org/xfn/11">
    • 正しい content-type メタ宣言: <title> タグの前で <meta http-equiv="Content-Type" content="<?php bloginfo('html_type'); ?>; charset=<?php bloginfo('charset'); ?>" /><code> または <code><meta charset=<?php bloginfo('charset'); ?> 宣言
    • 題名と説明用に <title> 内に bloginfo() が入っていること(必要に応じて)

機能

テーマに以下の本体機能を組み込むことが必須です。

テーマに以下の本体機能を組み込むことが推奨されますが、必須ではありません。しかしながら、組み込む場合にはWordPress本体の実装に対応しなければなりません。

テンプレートタグおよびフック

テーマで使うテンプレートタグおよびフックを適切に実装することが必須です。

次のテンプレートタグおよびフックは、適切な位置に入れることが必須です。

標準テンプレートファイルをテーマに組み込む場合、正しいテンプレートタグで呼び出すことが必須です。

  • ヘッダ: get_header()/en
    • Note: if a Theme uses get_header(), it is required to have a corresponding header.php file.
  • サイドバー: get_sidebar()/en
    • Note: if a Theme uses get_sidebar(), it is required to have a corresponding sidebar.php file.
  • フッタ: get_footer()/en
    • Note: if a Theme uses get_footer(), it is required to have a corresponding footer.php file.
  • コメント: comments_template()/en
    • Note: if a Theme uses comments_template(), it is required to have a corresponding comments.php file.
  • 検索フォーム: get_search_form()/en
  • ログインフォーム: wp_login_form()
  • カスタムテーマテンプレートファイル: get_template_part()
    • Note: include( TEMPLATEPATH . '/file.php' ) should not be used to call Theme template part files, unless absolutely necessary.

サイト情報をテーマに組み込む場合、正しいテンプレートタグで呼び出すことが必須です。
(この一覧は不完全です。全リストは bloginfo() を参照のこと)
(注) この節は草稿中です。 Consider it as such until this notice is removed.

WordPress定義CSSクラス

注: この節は草稿中です。 Consider it as such until this notice is removed.
以下のWordPress定義CSSクラス最新)または同様の要素への対応が必須です。

  • 配置クラス:
    • .aligncenter
    • .alignleft
    • .alignright
  • キャプション関連クラス:
    (画像などの説明文)
    • .wp-caption
    • .wp-caption
    • .wp-caption-text
    • .gallery-caption

共通クラスにも対応すべきです。

  • 投稿クラス:
    • .sticky
  • コメントクラス
    • .bypostauthor

テーマテンプレートファイル

最低限、入れることが必須のもの:

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

入れることが推奨されるもの:

  • 404.php
  • archive.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

任意のもの:

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

登録するテーマには次のような名前のファイルを入れないことが必須です。

  • 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.

ライセンシング(使用許諾)

  • 利用許諾条件
    • テーマ(PHP・HTML・CSS・画像・フォント・アイコンを含む)は100% GPLライセンスまたはGPL互換ライセンスであることが必須です。
    • 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

テーマ名

Note: this section is currently being drafted. Consider it as such until this notice is removed.
Theme Name Guidelines are required for new Themes, and recommended for existing Themes.

  • Themes are not to use WordPress in their name. For example My WordPress Theme, WordPress AwesomeSauce, and AwesomeSauce for WordPress would not be accepted. After all, this is the WordPress Theme repository.
    • Themes are not to use the term Theme in their name, such as: AwesomeSauce Theme. Same reason as above ... it's a Theme repository.
    • Themes may use the WP acronym in the Theme name, such as WP AwesomeSauce.
  • Themes are not to use version-specific, markup-related terms (e.g. HTML5, CSS3, etc.) in their name.
  • Themes are not to use Theme author/developer credit text in their name. For example AwesomeSauce by John Q. Developer (makes for a much better credit link); or, SEO/spam-seeded text, such as: AwesomeSauce by Awesome Free WP Themes (this is just not going to pass).

クレジットリンク

  • 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."

テーマ説明書

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.

テーマ単体テスト

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

テーマの旧式化

  • 一旦登録したら最新に保たなければいけません。
  • Any Theme not updated to the current theme review process as of the most recent release of WordPress may be subject to temporary suspension.

テーマ審査員になるには

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.

資料

役立つCodexリンク集

コード検証リンク集

PHP/WordPress検証ツール

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