When you get ready to set up a WordPress site, typically your process looks something like this:
- Download the latest version of WordPress from wordpress.org
- Unzip it.
- Copy and paste the files into a local directory (you are developing locally, right?)
- Create a MySQL database.
- Run the 5 minute WordPress install.
- Download your starter theme.
- Unzip it.
- Copy and paste the theme file into WordPress’s theme directory.
- Find your base plugins that you know you’ll need. Download each of them individually.
- Copy and paste the plugin files into WordPress’s plugin directory.
- Start your custom work.
That’s 11 steps, at least! I know, if you do it enough times you could probably get that down to a 15 minute setup, and that’s probably only if you have local versions of your boilerplate theme and plugins that you can quickly copy and paste into the respective directories.
But, why? Why would you even want to waste your time doing such mindless work every time you start a project when you could be spending that time designing and developing something beautiful and original?
What if I were to tell you that you could cut down that down to two minutes…on a bad day? Interested?
If you can hang with me for the length of this post, we can get you set up and you can start being more efficient.
Remember in English class, how they told us to (1) say what you’re going to say, (2) say it, and then (3) say what you said. I always remember thinking, “That sounds redundant.” Well, I’m going to take a lesson from Mrs. Nooks. I’ll tell you a little bit about the tools we’re going to put in our tool chest, then I’ll show you practically how to use them. It may get a little technical from time to time, but try to stick with it, it will be worth it.
If we’re going to use it, we have to install it. Fortunately for us, this is easy. There’s a big green “install” button their site. Click it.
Once the package is downloaded, unzip, and double click on the package to install it. Hooray!
Grunt and Gulp also run on Node. (Blog post for the future.) Just know, for now, we’re set up for success!
Yeoman is a project generator. It can do quite a bit, setting up sites and scaffolding (and not just for WordPress). We’re going to take the easy way out and use a generator Wesley Todd has already created specifically for starting a WordPress project: YeoPress.
To run YeoPress, Node is the only thing that is required (which we just installed), however, Wesley encourages you to have git and SASS installed, too. If you don’t, no worries, it’s pretty straightforward too:
You can go to the git website, download the file, unzip, and double click on the package to install it. Done and done.
SASS is a Ruby gem. If you’re working on a Mac, it comes with Ruby already installed. All you have to do is open up your Terminal (GASP I know, it will be OK.) and run the command:
If you get an error, chances are you need to run the sudo command:
Sudo forces your computer to run the command. It will ask you to enter your computer’s password.
If you want to check to make sure everything was installed correctly, you can run:
You should see it return
Sass 3.4.9 (Selective Steve).
Now, for installing Yeoman (yo) and YeoPress (at the same time). Within the Terminal run:
npm just means that it’s a node command.
Now, within the Terminal, we just have to navigate to the folder we want to install WordPress inside of.
For the longest time, I was uncomfortable inside the Terminal, too. But, I promise, the more you use the more comfortable you’ll become. As soon as you see the benefits that the Terminal provides your workflow, it will eventually become something you can’t / won’t want to ignore.
You’ll see the WordPress logo appear and it will start to ask you a series of questions about how you want to set up your WordPress install:
If you’re doing local development (as you should), enter that URL in.
This is the table prefix for your WordPress database. By default it’s wp_. Stay with that. It makes it easy when you’re looking at your database to be able to tell which tables are related to your WordPress install.
Database Host, Name, User, Password
MAMP will also list all the credentials you need (host, user, and password) on the WebStart page.
More on this later, too, but for now, take my word and just say “Yes”…err, rather “Y”.
Would you like to install WordPress as a submodule?
My personal take?
First, let me explain what a submodule is. Submodules are a “Git thing”. It’s essentially an external Git repo that your repo references. Think of it as a nested repo that you can update it independently.
When you think of it in those terms, it makes sense to implement WordPress as a submodule. I don’t manage the WordPress core, so why not make it seperate and reference the actual WordPress repo itself?
If you implement WordPress as a submodule, you’ll using the following commands to update WordPress later:
git fetch && git fetch –tags
git checkout 4.1
git add wp
git commit -m “Updated to WP 4.1”
Not too shabby.
If you get an error, when you try to update WordPress, like:
Your local changes to the following files would be overwritten by checkout. Try forcing the checkout:
So… “Yes” install WordPress as a submodule.
WordPress install directory
My personal preference is “wp.”
This means when I log in to the admin panel, the address will be: http://SITENAME.dev/wp/wp-admin
WordPress content directory
I go with “wp-content.”
Install a custom theme?
I choose “no.” But, I think this would be a good area, in the future, to streamline my process even more.
Does this all look correct?
It’s always comforting that it asks you to double check. “Yes.”
Boom! It will download WordPress for you and set up your config file. Granted, the set up may sound a little verbose, but we just condensed that 11 step process into a few lines of code.
For future reference:
If you clone your repo and the wp directory is blank (WordPress is a submodule, remember), run:
git submodule init && git submodule update
Also, if you need to update YeoPress, it’s as simple as running the following line: