johnbillion

INITIALISATION
==============

load wp-config.php
set up default constants
load wp-content/advanced-cache.php if it exists
load wp-content/db.php if it exists
connect to mysql, select db
load object cache (object-cache.php if it exists, or wp-include/cache.php if not)
load wp-content/sunrise.php if it exists (multisite only)

kadamwhite

JavaScript Coding Standards

The core WordPress PHP files become cleaner and easier to read with every release, thanks in part to our strong standards for PHP code style. Our JavaScript, on the other hand, hasn't gotten nearly enough love. This post is intended to open up the recent discussion around JavaScript style to the greater community so we can make up for lost time.

Don't we already have a style guide for JavaScript?

Back in March, @tommcfarlin added a set of coding standards for JavaScript to the developer handbook. These WordPress JS coding standards were a great work-in-progress, but weren't fully comprehensive (leading to some comment threads clarifying various areas). More importantly, without any clear implementation plan the style guide failed to gain traction.

At WordCamp Boston's core

markjaquith

sites
  |__ ms.dev
  | |__ content
  | |__ index.php
  | |__ wp => ../../wordpress/stable
  | |__ wp-config.php
  |__ one.dev
  | |__ content
  | |__ index.php
  | |__ wp => ../../wordpress/stable

curtismchale

Contract Killer 3

Revised date: 07/11/2012

Between us [company name] and you [customer name]

Summary:

We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

Viper007Bond

<?php

/**
 * This little class records how long it takes each WordPress action or filter
 * to execute which gives a good indicator of what hooks are being slow.
 * You can then debug those hooks to see what hooked functions are causing problems.
 * 
 * This class does NOT time the core WordPress code that is being run between hooks.
 * You could use similar code to this that doesn't have an end processor to do that.
 * 

nathansmith

// `Default font for form elements.
//----------------------------------------------------------------------------------------------------

$form-font-stack: Arial, "Liberation Sans", FreeSans, sans-serif !default;
$form-font-size: 13px !default;

// `Form Element Reset.
//----------------------------------------------------------------------------------------------------

input::ms-clear,