Recommended

Comments

Themes are recommended to support comments, including nested comments and comment navigation.
If comments are not supported, the team recommends that this is documented as a limitation, in the theme readme file.

Top ↑

Theme support

The following theme support is recommended for classic themes

  • add_theme_support( "custom-header", $args )
  • add_theme_support( "custom-background", $args )
  • add_theme_support( "custom-logo", $args )
  • add_theme_support( "html5", $args )
  • add_theme_support( "responsive-embeds" )
  • add_theme_support( "align-wide" )
  • add_theme_support( "wp-block-styles" )
  • add_theme_support( "post-thumbnails" )

Read more about theme support.

Top ↑

Editor style

For a good user experience, it is recommended to include an editor style and that the editors and the front match.

Top ↑

Block patterns and block styles

Themes are recommended to include block patterns and custom block styles.

Top ↑

Post navigation

Themes are recommended to support post navigation using either:

Top ↑

For classic themes, WordPress outputs the following CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes that themes are recommended to style:

  • .sticky
  • .bypostauthor
  • .alignleft
  • .alignright
  • .aligncenter
  • .wp-caption
  • .wp-caption-text
  • .gallery-caption
  • .screen-reader-text

Top ↑

Avatars

Include support for the standard avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. functions, get_avatar() or wp_list_comments()

Top ↑

Post formats

If post formats are included, it is recommended to style these in a way that distinguishes them from standard post and page content.

Top ↑

Widget areas and widgets

Classic themes are recommended to support widgets.

Sidebars need to be registered in a custom function hooked to the widgets_init action. See: register_sidebar().


Top ↑

Favicons and Site Icons should not be included

Themes are recommended to not include their own favicon or site icon.
Favicons are handled by the Site Icon setting in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. since WordPress version 4.3.

Top ↑

WP_title should not be used

wp_title() was historically used for the document <title> tag and was never intended for other purposes.
Use add_theme_support( "title-tag" ) instead.

Top ↑

Document <title> tag should not be used

Document titles must not be hard coded, use add_theme_support( "title-tag" ) instead.

Last updated: