WordPress themes developed Step by Step Complete Guideline

WordPress themes developed Step by Step Complete Guideline  

WordPress

Theme Style sheet

In addition to CSS style information for your theme,style.CSS provides details about the Theme in the form of comments. The style sheet must provide details about the Theme in the form of comments. No two Themes are allowed to have the same details listed in their comment headers, as this will lead to problems in the Theme selection dialog. If you make your own Theme by copying an existing one, make sure you change this information first.

The following is an example of the first few lines of the style sheet, called the style sheet header, for the Theme "Twenty Thirteen":

/*
Theme Name: Twenty Thirteen
Theme URI: http://wordpress.org/themes/twentythirteen
Author: the WordPress team
Author URI: http://wordpress.org/
Description: The 2013 theme for WordPress takes us back to the blog, featuring a full range of post formats, each displayed beautifully in their own unique way. Design details abound, starting with a vibrant color scheme and matching header images, beautiful typography and icons, and a flexible layout that looks great on any device, big or small.
Version: 1.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Tags: black, brown, orange, tan, white, yellow, light, one-column, two-columns, right-sidebar, flexible-width, custom-header, custom-menu, editor-style, featured-images, micro formats, post-formats, rt-language-support, sticky-post, translation-ready
Text Domain: twenty thirteen

This theme, like WordPress, is licensed under the GPL.
Use it to make something cool, have fun, and share what you've learned with others.
*/

NB: The name used for the Author is suggested to be the same as the Theme Author's word press.org username, although it can be the author's real name as well. The choice is the Theme Author's.

Note the list of Tags used to describe the theme. These allow user to find your theme using the tag filter. You can find a full list in the Theme Review Handbook.

The comment header lines in style.CSS are required for WordPress to be able to identify the Theme and display it in the Administration Panel under Design > Themes as an available Theme option along with any other installed Themes.

Style sheet Guidelines

• Follow CSS coding standards when authoring your CSS.
• Use valid CSS when possible. As an exception, use vendor-specific prefixes to take advantage of CSS3 features.
• Minimize CSS hacks. The obvious exception is browsers-specific support, usually versions of IE. If possible, separate CSS hacks into separate sections or separate files.
• All possible HTML elements should be styled by your theme (unless it is a child theme), both in post/page content and in comment content.
  • Tables, captions, images, lists, block quotes, et cetera.
• Adding print-friendly styles is highly recommended.
  • You can include a print style sheet with media="print" or add in a print media block in your main style sheet.

Functions File

A theme can optionally use a functions file, which resides in the theme subdirectory and is namedfunctions.php. This file basically acts like a plugin, and if it is present in the theme you are using, it is automatically loaded during WordPress initialization (both for admin pages and external pages). Suggested uses for this file:

• Enqueue theme style sheets and scripts. See wp_enqueue_scripts.
• Enable Theme Features such as Sidebars, Navigation Menus, Post Thumbnails, Post Formats, Custom Headers, Custom Backgrounds and others.
• Define functions used in several template files of your theme.
• Set up an options menu, giving site owners options for colors, styles, and other aspects of your theme.

The default WordPress theme contains a functions.PHP file that defines many of these features, so you might want to use it as a model. Since functions.PHP basically functions as a plugin, the Function_Reference list is the best place to go for more information on what you can do with this file.

Note for deciding when to add functions to functions.php or to a specific plugin: You may find that you need the same function to be available to more than one parent theme. If that is the case, the function should be created in a plugin instead of a functions.php for the specific theme. This can include template tags and other specific functions. Functions contained in plugins will be seen by all themes.

Template Files

Templates are PHP source files used to generate the pages requested by visitors, and are output as HTML. Template files are made up of HTML, PHP, and WordPress Template Tags.

Let's look at the various templates that can be defined as part of a Theme.

WordPress allows you to define separate templates for the various aspects of your site. It is not essential, however, to have all these different template files for your site to fully function. Templates are chosen and generated based upon the Template Hierarchy, depending upon what templates are available in a particular Theme.

As a Theme developer, you can choose the amount of customization you want to implement using templates. For example, as an extreme case, you can use only one template file, called index.PHP as the template for all pages generated and displayed by the site. A more common use is to have different template files generate different results, to allow maximum customization.

Template Files List

Here is the list of the Theme files recognized by WordPress. Of course, your Theme can contain any other style sheets, images, or files. Just keep in mind that the following have special meaning to WordPress -- see Template Hierarchy for more information.

style.css

The main style sheet. This must be included with your Theme, and it must contain the information header for your Theme.

rtl.css

The rtl style sheet. This will be included automatically if the website's text direction is right-to-left. This can be generated using the RTLer plugin.

index.php

The main template. If your Theme provides its own templates, index.php must be present.

comments.php

The comments template.

front-page.php

The front page template.

home.php

The home page template, which is the front page by default. If you use a static front page this is the template for the page with the latest posts.

single.php

The single post template. Used when a single post is queried. For this and all other query templates,index.php is used if the query template is not present.

single-{post-type}.php

The single post template used when a single post from a custom post type is queried. For example,single-book.php would be used for displaying single posts from the custom post type named "book".index.php is used if the query template for the custom post type is not present.

page.php

The page template. Used when an individual Page is queried.

category.php

The category template. Used when a category is queried.

tag.php

The tag template. Used when a tag is queried.

taxonomy.php

The term template. Used when a term in a custom taxonomy is queried.

author.php

The author template. Used when an author is queried.

date.php

The date/time template. Used when a date or time is queried. Year, month, day, hour, minute, second.

archive.php

The archive template. Used when a category, author, or date is queried. Note that this template will be overridden by category.php, author.php, and date.phpfor their respective query types.

search.php

The search results template. Used when a search is performed.

attachment.php

Attachment template. Used when viewing a single attachment.

image.php

Image attachment template. Used when viewing a single image attachment. If not present, attachment.php will be used.

404.php

The 404 Not Found template. Used when WordPress cannot find a post or page that matches the query.

These files have a special meaning with regard to WordPress because they are used as a replacement forindex.php, when available, according to the Template Hierarchy, and when the corresponding Conditional Tagreturns true. For example, if only a single post is being displayed, the is_single() function returns 'true', and, if there is a single.php file in the active Theme, that template is used to generate the page.

Basic Templates

At the very minimum, a WordPress Theme consists of two files:

• style.css
• index.php

Both of these files go into the Theme directory. Theindex.php template file is very flexible. It can be used to include all references to the header, sidebar, footer, content, categories, archives, search, error, and any other page created in WordPress.

Or, it can be divided into modular template files, each one taking on part of the workload. If you do not provide other template files, WordPress may have default files or functions to perform their jobs. For example, if you do not provide a searchform.php template file, WordPress has a default function to display the search form.

Typical template files include:

• comments.php
• comments-popup.php
• footer.php
• header.php
• sidebar.php

Using these template files you can put template tags within the index.php master file to include these other files where you want them to appear in the final generated page.

• To include the header, use get_header().
• To include the sidebar, use get_sidebar().
• To include the footer, use get_footer().
• To include the search form, useget_search_form().

Here is an example of the include usage:

<?php get_sidebar(); ?>

<?php get_footer(); ?>

The default files for some template functions may be deprecated or not present, and you should provide these files in your theme. As of version 3.0, the deprecated default files are located in wp-includes/theme-compat. For example, you should provide header.php for the function get_header() to work safely, andcomments.php for the functioncomments_template().

For more on how these various Templates work and how to generate different information within them, read the Templates documentation.

Custom Page Templates

The files defining each page template are found in yourThemes directory. To create a new custom page template for a page you must create a file. Let's call our first page template for our page snarfer.php. At the top of the snarfer.php file, put the following:

<?php
/*
Template Name: Snarfer
*/
?>

The above code defines this snarfer.php file as the "Snarfer" template. Naturally, "Snarfer" may be replaced with most any text to change the name of the page template. This template name will appear in the Theme Editor as the link to edit this file.

The file may be named almost anything with a .phpextension (see reserved Theme filenames for filenames you should not use; these are special file names WordPress reserves for specific purposes).

What follows the above five lines of code is up to you. The rest of the code you write will control how pages that use the Snarfer page template will display. SeeTemplate Tags for a description of the various WordPress template functions you can use for this purpose. You may find it more convenient to copy some other template (perhaps page.php or index.php) tosnarfer.php and then add the above five lines of code to the beginning of the file. That way, you will only have toalter the HTML and PHP code, instead of creating it all from scratch. Examples are shown below. Once you have created a page template and placed it in your theme's directory, it will be available as a choice when you create or edit a page. (Note: when creating or editing a page, the Page Template option does not appear unless there is at least one template defined in the above manner.)

Query-based Template Files

WordPress can load different Templates for differentquery types. There are two ways to do this: as part of the built-in Template Hierarchy, and through the use ofConditional Tags within The Loop of a template file.

To use the Template Hierarchy, you basically need to provide special-purpose Template files, which will automatically be used to override index.php. For instance, if your Theme provides a template calledcategory.php and a category is being queried,category.php will be loaded instead of index.php. Ifcategory.php is not present, index.php is used as usual.

You can get even more specific in the Template Hierarchy by providing a file called, for instance,category-6.php -- this file will be used rather thancategory.php when generating the page for the category whose ID number is 6. (You can find category ID numbers in Manage > Categories if you are logged in as the site administrator in WordPress version 2.3 and below. In WordPress 2.5 the ID column was removed from the Admin panels. You can locate the category id by clicking 'Edit Category' and looking on the URL address bar for the cat_ID value. It will look '...categories.php?action=edit&cat_ID=3' where '3' is the category id). For a more detailed look at how this process works, see Category Templates.

If your Theme needs to have even more control over which Template files are used than what is provided in the Template Hierarchy, you can use Conditional Tags. The Conditional Tag basically checks to see if some particular condition is true, within the WordPress Loop, and then you can load a particular template, or put some particular text on the screen, based on that condition.

For example, to generate a distinctive stylesheet in a post only found within a specific category, the code might look like this:

<?php
if ( is_category( '9' ) ) {
    get_template_part( 'single2' ); // looking for posts in category with ID of '9'
} else {
    get_template_part( 'single1' ); // put this on every other category post
}
?>

Or, using a query, it might look like this:

<?php
$post = $wp_query->post;
if ( in_category( '9' ) ) {
    get_template_part( 'single2' );
} else {
    get_template_part( 'single1' );
}
?>

In either case, this example code will cause different templates to be used depending on the category of the particular post being displayed. Query conditions are not limited to categories, however, see the Conditional Tagsarticle to look at all the options.

Defining Custom Templates

It is possible to use the WordPress plugin system to define additional templates that are shown based on your own custom criteria. This advanced feature can be accomplished using the "template_include" action hook. More information about creating plugins can be found in the Plugin API reference.

Including Template Files

To load another template (other than header, sidebar, footer, which have predefined included commands likeget_header()) into a template, you can useget_template_part(). This makes it easy for a Theme to reuse sections of code.

Referencing Files From a Template

When referencing other files within the same Theme, avoid hard-coded URIs and file paths. Instead reference the URIs and file paths with bloginfo(): seeReferencing Files From a Template.

Note that URIs that are used in the stylesheet are relative to the stylesheet, not the page that references the stylesheet. For example, if you include an images/directory in your Theme, you need only specify this relative directory in the CSS, like so:

h1 {
    background-image: url(images/my-background.jpg);
}

Plugin API Hooks

When developing Themes, it's good to keep in mind that your Theme should be set up so that it can work well with any WordPress plugins users might decide to install. Plugins add functionality to WordPress via "Action Hooks" (see Plugin API for more information).

Most Action Hooks are within the core PHP code of WordPress, so your Theme does not have to have any special tags for them to work. But a few Action Hooks do need to be present in your Theme, in order for Plugins to display information directly in your header, footer, sidebar, or in the page body. Here is a list of the special Action Hook Template Tags you need to include:

wp_enqueue_scripts

Used in the theme functions file. Used to load external scripts and stylesheets.

wp_head()

Goes in the <head> element of a theme, inheader.php. Example plugin use: add JavaScript code.

wp_footer()

Goes in footer.php, just before the closing </body>tag. Example plugin use: insert PHP code that needs to run after everything else, at the bottom of the footer. Very commonly used to insert web statistics code, such as Google Analytics.

wp_meta()

Typically goes in the <li>Meta</li> section of a Theme's menu or sidebar; sidebar.php template. Example plugin use: include a rotating advertisement or a tag cloud.

comment_form()

Goes in comments.php directly before the file's closing tag (</div>). Example plugin use: display a comment preview.

For a real world usage example, you'll find these plugin hooks included in the default Theme's templates.

Theme Customization API

As of WordPress 3.4, a new Theme Customization feature is available by default for nearly all WordPress themes. The Theme Customization admin page is automatically populated with options that a theme declares support for with add_theme_support() or using the Settings API, and allows admins to see non-permanent previews of changes they make in real time.

Theme and plugin developers interested in adding new options to a theme's Theme Customization page should see the documentation on the Theme Customization API. Additional tutorials on the Theme Customization API are available at the Ottopress.com website.

Untrusted Data

You should escape dynamically generated content in your Theme, especially content that is output to HTML attributes. As noted in WordPress Coding Standards, text that goes into attributes should be run throughesc_attr() so that single or double quotes do not end the attribute value and invalidate the XHTML and cause a security issue. Common places to check are title,alt, and value attributes.

There are few special template tags for common cases where safe output is needed. One such case involves outputting a post title to a title attribute usingthe_title_attribute() instead of the_title()to avoid a security vulnerability. Here's an example of correct escaping for the title attribute of a post title link when using translatable text:

<a href="<?php the_permalink(); ?>" title="<?php sprintf( __( 'Permanent Link to %s', 'theme-name' ), the_title_attribute( 'echo=0' ) ); ?>"><?php the_title(); ?></a>

Replace deprecated escape calls with the correct calls:wp_specialchars() and htmlspecialchars()with esc_html(), clean_url() with esc_url(), andattribute_escape() with esc_attr(). SeeData_Validation for more.

Translation Support / I18n

To ensure smooth transition for language localization, use the WordPress gettext-based i18n functions for wrapping all translatable text within the template files. This makes it easier for the translation files to hook in and translate the labels, titles and other template text into the site's current language. See more at WordPress Localization and I18n for WordPress Developers.

Theme Classes

Implement the following template tags to add WordPress-generated class attributes to body, post, and comment elements. For post classes, apply only to elements within The Loop.

• body_class()
• post_class()
• comment_class()

Template File Checklist

When developing a Theme, check your template files against the following template file standards.

Document Head (header.php)

• Use the proper DOCTYPE.
• The opening <html> tag should includelanguage_attributes().
• The <meta> charset element should be placed before everything else, including the <title> element.
• Use bloginfo() to set the <meta> charset and description elements.
• Use wp_title() to set the <title> element. See why.
• Use Automatic Feed Links to add feed links.
• Add a call to wp_head() before the closing </head>tag. Plugins use this action hook to add their own scripts, stylesheets, and other functionality.
• Do not link the theme stylesheets in the Header template. Use the wp_enqueue_scripts action hook in a theme function instead.

Here's an example of a correctly-formatted HTML5 compliant head area:

<!DOCTYPE html>
<html <?php language_attributes(); ?>>
    <head>
        <meta charset="<?php bloginfo( 'charset' ); ?>" />
        <title><?php wp_title(); ?></title>
        <link rel="profile" href="http://gmpg.org/xfn/11" />
        <link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>" />
        <?php if ( is_singular() && get_option( 'thread_comments' ) ) wp_enqueue_script( 'comment-reply' ); ?>
        <?php wp_head(); ?>
    </head>

Navigation Menus (header.php)

• The Theme's main navigation should support a custom menu with wp_nav_menu().
  • Menus should support long link titles and a large amount of list items. These items should not break the design or layout.
  • Submenu items should display correctly. If possible, support drop-down menu styles for submenu items. Drop-downs allowing showing menu depth instead of just showing the top level.

Widgets (sidebar.php)

• The Theme should be widgetized as fully as possible. Any area in the layout that works like a widget (tag cloud, blogroll, list of categories) or could accept widgets (sidebar) should allow widgets.
• Content that appears in widgetized areas by default (hard-coded into the sidebar, for example) should disappear when widgets are enabled from Appearance > Widgets.

Footer (footer.php)

• Use the wp_footer() call, to appear just before closing body tag.

<?php wp_footer(); ?>
</body>
</html>

Index (index.php)

• Display a list of posts in excerpt or full-length form. Choose one or the other as appropriate.
• Include wp_link_pages() to support navigation links within posts.

Archive (archive.php)

• Display archive title (tag, category, date-based, or author archives).
• Display a list of posts in excerpt or full-length form. Choose one or the other as appropriate.
• Include wp_link_pages() to support navigation links within posts.

Pages (page.php)

• Display page title and page content.
• Display comment list and comment form (unless comments are off).
• Include wp_link_pages() to support navigation links within a page.
• Metadata such as tags, categories, date and author should not be displayed.
• Display an "Edit" link for logged-in users with edit permissions.

Single Post (single.php)

• Include wp_link_pages() to support navigation links within a post.
• Display post title and post content.
  • The title should be plain text instead of a link pointing to itself.
• Display the post date.
  • Respect the date and time format settings unless it's important to the design. (User settings for date and time format are in Administration Panels >Settings > General).
  • For output based on the user setting, usethe_time( get_option( 'date_format' ) ).
• Display the author name (if appropriate).
• Display post categories and post tags.
• Display an "Edit" link for logged-in users with edit permissions.
• Display comment list and comment form.
• Show navigation links to next and previous post usingprevious_post_link() andnext_post_link().

Comments (comments.php)

• Author comment should be highlighted differently.
• Display gravatars (user avatars) if appropriate.
• Support threaded comments.
• Display trackbacks/pingbacks.
• This file shouldn’t contain function definitions unless in the function_exist() check to avoid redeclaration errors. Ideally all functions should be infunctions.php.

Search Results (search.php)

• Display a list of posts in excerpt or full-length form. Choose one or the other as appropriate.
• The search results page shows the search term which generated the results. It's a simple but useful way to remind someone what they just searched for -- especially in the case of zero results. Usethe_search_query() or get_search_query()(display or return the value, respectively). For example:

  <h2><?php printf( __( 'Search Results for: %s' ), '<span>' . get_search_query() . '</span>'); ?></h2>

• It's a good practice to include the search form again on the results page. Include it with:get_search_form().

JavaScript

• JavaScript code should be placed in external files whenever possible.
• Use wp_enqueue_script() to load your scripts.
• JavaScript loaded directly into HTML documents (template files) should be CDATA encoded to prevent errors in older browsers.

<script type="text/javascript">
/* <![CDATA[ */
// content of your Javascript goes here
/* ]]> */
</script>

Screenshot

Create a screenshot for your theme. The screenshot should be named screenshot.png, and should be placed in the top level directory. The screenshot should accurately show the theme design and saved in PNG format. While .jpg, .jpeg, and .gif are also valid extensions and file formats for the screenshot, they are not recommended.

The recommended image size is 1200px wide by 900px tall. The screenshot will usually be shown smaller but the over-sized image allows for high-resolution viewing on HiDPI displays. Note that because the Manage Themes screen is responsive, the top and bottom of the screenshot image might not be viewable so keep graphics near the center.

Theme Options

Themes can optionally support the Theme Customize Screen. For an example code, see A Sample WordPress Theme Options Page.

When enabling the availability of the Theme Customize Screen for a user role, use the "edit_theme_options" user capability instead of the "switch_themes" capability unless the user role actually should also be able to switch the themes. See more at Roles and Capabilitiesand Adding Administration Menus.

If you are using the "edit_themes" capability anywhere in your Theme to gain the Administrator role access to the Theme Customize Screen (or maybe some custom screens), be aware that since Version 3.0, this capability has not been assigned to the Administrator role by default in the case of WordPress Multisite installation. See the explanation. In such a case, use the "edit_theme_options" capability instead if you want the Administrator to see the "Theme Options" menu. See theadditional capabilities of Administrator role when using WordPress Multisite.

Theme Testing Process

1. Fix PHP and WordPress errors. Add the following debug setting to your wp-config.php file to see deprecated function calls and other WordPress-related errors: define('WP_DEBUG', true);. See Deprecated Functions Hook for more information.
2. Check template files against Template File Checklist(see above).
3. Do a run-through using the Theme Unit Test.
4. Validate HTML and CSS. See Validating a Website.
5. Check for JavaScript errors.
6. Test in all your target browsers. For example, IE9, Safari, Chrome, Opera, Firefox and Microsoft Edge.
7. Clean up any extraneous comments, debug settings, or TODO items.
8. See Theme Review if you are publicly releasing the Theme by submitting it to the Themes Directory.