Wordpress Theme Guide

You should always use topic log prefixes such as underscores or wraparound codes in an immediately called functional statement (IFFE). Each design must use the HTML5 doc type and contain semiantic mark-up.

The topics must be fast and reactive. Do not add IE9 extended codes or scripting. Subjects must have widget permission. Designs must have at least one custom menu. Refer to the Documented Guide to make sure your user has a clear grasp of a topic's functionality and where to get help.

Designs must be formatted from right to left. to right. The translator must be able to disable web font that does not understand the font of their own langauge. Use the customizer to restrict the implementation of theme selections. The topic option must be located in a section titled "Topic Options". Topic choices should not allow the user to append scripting or style.

Topics must be Jetpack Infinite Scroll supported. For the theme, the elementary css of the theme must be style.css. Topic tag in stile. bss must be lower case without space. The row height must be adjusted to relatively high value for custom fonts to work properly. Topics must comply with the template hierarchy. Home page. Php must comply with the user's preferences at ? reading ? Front Page Displays value.

You must configure $content_width to the standard width of the theme. Simply invoking the_post() in a style sheet like single.php or page.php is not enough. Subjects must use WP_Query. Topics must not change the primary interrogation. Widgetitle with the theme name, i.e. Theme Name: Broadget areas must not contain any hard-coded widgets.

Visual feed link may not appear in topics. Topics must somehow be supportive of both category and tag. Extend Jetpack content options as much as possible. Explanation: Both the page header and the tagline can be suppressed at any time via the customizer, so that the standard suppression of such an option causes a bewildering userscape.

When the website has no side bar or the side bar has no widgets, the length of the contents line should be adjusted. Normally, if a page consists of two or more pages with a widget, the page should adapt to a unique page size if a page bar visitor has not added any pages to the page bar without showing an empty page.

It gives the operator the flexibility to use a single-column design without the need for a page style or design options. The widget-visibility utility can be used if a widget is only desired on certain pages. Menus should indicate the storage place and, if the design has more than one support, its place, e.g. header above, header below, footer, etc.

It is not possible for the operator to know which menus refer to which areas without this. Items in the menus should have the formats of menus 1, 2, etc.. Topic consistence means that a subscriber can change topics and does not have to adjust his menus to the topic's item. It should be referred to as the societal meal.

consistent change theme, which means that the page still shows the user's main page after a change of theme. Dropdown boxes should have an arrowset that indicates the orientation in which the box opens. You should have a Hamburg symbol and the Menue labeled on your portable device. Endorsers can always see the same portable display and don't have to memorize a new symbol or phrase every change of topic.

Theme does not need to be able to handle postal format unless the theme is a tumblog theme, in which case the theme should be able to handle all available postal format. User expects only Postformats of Tumblog-like topics. You should have all your originals in a single directory named Originals. You should name the default asset allocation page.php.

The full width pattern should be named full-width-page.php. The grid should be grid-page.php. You should call your templates your own page.php. The menu templates should be named something like menu-page.php. The guestbook should be named guestbook-page.php. You should call the contributor submission a contributor - page.php. The title page should be named front-page.php. By consistently designating templates, you can shorten set-up times after a change of topic and shorten reviews.

Topic consistent means that a users can change topics and don't have to re-assign their widgets to the topic's broadget positions. It is recommended to use navigational menu to deal with soft symbols.