All of the code below can be put inside your functions.php page in your theme folder.

It all starts with the function register_post_type:

register_post_type ( $post_type, $options );

The $post_type is the name of the custom post type you want to associate it as. For example we will create a custom post type called Events like the below code:

$options = array
(
    'label' => 'Events',
    'singular_label' => 'Event',
    'public' => TRUE,
    'show_ui' => TRUE,
    'capability_type' => 'post',
    'hierarchical' => TRUE,
    'rewrite' => array( 'slug' => 'events' ),
    'query_var' => TRUE,
    'supports' => array( 'title', 'editor', 'author' )
);

register_post_type ( 'events', $options );

The description and other options can be found on the register_post_type function page at WordPress’ website.

Now you will have a custom post type in the backend of your WordPress theme.

remove_action ( 'wp_head', 'wp_generator' )

It will auto remove the tag that says:

<meta name="generator" content="WordPress 3.0.1" />

The explosion of JavaScript libraries and frameworks such as jQuery onto the front-end development scene has opened up the power of JavaScript to a far wider audience than ever before. It was born of the need — expressed by a crescendo of screaming by front-end developers who were fast running out of hair to pull out — to improve JavaScript’s somewhat primitive API, to make up for the lack of unified implementation across browsers and to make it more compact in its syntax.

All of which means that, unless you have some odd grudge against jQuery, those days are gone — you can actually get stuff done now. A script to find all links of a certain CSS class in a document and bind an event to them now requires one line of code, not 10. To power this, jQuery brings to the party its own API, featuring a host of functions, methods and syntactical peculiarities. Some are confused or appear similar to each other but actually differ in some way. This article clears up some of these confusions.

via Smashing Magazine

error_reporting ( E_ALL );
ini_set ( 'display_errors', '1' );