We want to be working locally while working on this project. Just a few reasons:

  • It's fast.
  • We can work offline from anywhere.
  • We're working on a complete redesign that will take many days, we can't leave a live site half-cocked.
  • There is no risk working locally.
  • We can use version control, giving us a record of what changed when and making future team work easier.
  • We can use preprocessors.

To work locally, we use MAMP to create a local domain name with a local folder as the root. We use Sequel Pro to create (and manage) a local MySQL database. We download and install a fresh copy of WordPress and install it. We export all the posts/pages/comments/attachments and stuff from Jeff's live site and import it locally.


  1. Brad Wrage
    Permalink to comment#

    Hi Chris,
    Love the stuff. Is this your typical workflow with wordpress? Making sure you have a local install first? I ask because I’ve seen in some of your other videos you wen super simple with just html, scss, jquery using codekit.


  2. john
    Permalink to comment#

    Great video, just jumped into this new series, only problem so far is the mic on this particular one is quite low, previous videos were fine.

  3. Anthony DeCrescenzo
    Permalink to comment#

    Has no one…NO ONE?…in over a year pointed out that “Environment” is spelled incorrectly in the title?

    Well then, I’m honored. And it is. FYI.


Leave a Comment

Posting Code

We highly encourage you to post problematic HTML/CSS/JavaScript over on CodePen and include the link in your post. It's much easier to see, understand, and help with when you do that.

Markdown is supported, so you can write inline code like `<div>this</div>` or multiline blocks of code in triple backtick fences like this:

  function example() {
    element.innerHTML = "<div>code</div>";

We have a pretty good* newsletter.