Web development in 2018 can be a bit overwhelming. There are so many new tools and techniques that it’s easy to experience paralysis by analysis.
If you’ve been struggling to put the pieces of the puzzle together, we hope that this article will help. We’ll cover the the web development tools we use here at 45royale to build client projects locally before pushing them out to the world.
Two notes before we begin:
1. The environmental set up outlined below can handle anything from custom web applications to WordPress sites. The latter will be our focus in this article, but if your project requires a server and/or database, this set up will still work.
2. We aim to make this article a step-by-step guide you can follow along with. We’ve included a lot of images for reference, hoping to make your pathway more clear. If for any reason you feel that something doesn’t make sense or could be more clear, please reach out in the comments. We’d be happy to include more detail where we can. Onward!
Getting started with your web development environment
The first thing we need to do to is to get familiar with Local by Flywheel.
Local makes building WordPress sites super easy. It’s a free tool that Flywheel has created to quickly and easily set up WordPress environments on your own computer.
We’ve used MAMP for many years, but with Local, it’s dead simple to get a sight up and running. With options for one-click WordPress installation and flexible environment options (we’ll see that in a minute), it couldn’t be easier to jump right in.
First, head on over to Flywheel’s website and download Local. Once you install and open the app, Local will walk you through the steps to set up your first WordPress site.
Local will configure your VirtualBox and Host Machine for you, just sit back and let it do its thing. Once it’s done, it will show you a blank dashboard where your projects will show up once they’re created.
Go ahead and click “Create a new site”.
Local will then prompt you to fill out information about your new site. In this example, I’ve named mine MDv2 and given my local site a domain of
mdv2.local. You can select other URL patterns, but I like using
.local. Double check the site path and make sure “Don’t use a Blueprint” is active. Click “Continue” to move on to the next step.
Next, Local will ask you to select your environment. For most people, the “Preferred” tab is what you’ll need. However, you can customize your settings to match your needs.
For example, you can change your versions of PHP and/or MySQL if your project has specific needs. For our purposes though, we’ll go with the “Preferred” environment. Click “Continue” to move to WordPress Setup.
Here you’ll enter your credentials for your WordPress installation. Enter the username, password, and email address you’ll want to use on your local WordPress site.
Under the Advanced Options you have the ability to select if your WordPress install will be a Subdirectory or Subdomain multisite. For most people, you won’t need to select these. But in case you do, you can adjust those settings here.
We won’t need any of the advanced options so let’s move forward by clicking “Add Site”.
Local will now gather all the settings you input and prepare your environment. This includes building the databases, getting the servers up and running, downloading WordPress, and more. In a matter of seconds you’ll be up and running with a WordPress site.
When Local host has finished, you’ll see your site appear on the dashboard. It shows your local environment specifics, a button to “View Site”, and more.
One thing to point out here that some people miss: Have a look at the “Live Link” button at the bottom. If you enable Live Link on your site, you’ll be able to send a link of your local site to a friend or client and they’ll be able to see your progress along the way.
No uploading to a server, no configuring a domain. Simply share the link with them and they’ll be able to see your site along with you in real time. It’s magic.
So now you’re set up with Local and you have your WordPress site ready to go. Let’s move on to the next step which is getting a theme installed on your site.
Underscores: The best starter theme we’ve found for WordPress web development
Before you start diving in to your site, it’s important to take a step back and set yourself up for success.
If you’re building a custom WordPress site from scratch based on a design you or a designer came up with, you’re going to want to start with a blank slate. That’s where Underscores.me comes in.
Built and maintained by the folks at Automattic (the people behind WordPress), Underscores is one of the best themes you can start out with. With “ultra-minimal CSS” you’ll find far less bloat than you would on other “starter” themes.
But the best part about the Underscores theme is that it gives you proper, well-commented WordPress page templates to start with. It’s literally the best theme we’ve found to start custom projects, we think you’ll love it.
Head on over to the underscores.me home page and start creating your theme. If you’re in a hurry, simply input your theme name in to the input field and hit “Generate”.
However, we recommend filling in some of the advanced options so that we have a more complete theme. At a minimum we fill in the options in the screenshot above.
After you click “Generate”, Underscores will package your theme and download it to your computer. Once you unzip your new theme (ours is called mdv2), add it to your WordPress site by moving it into the [themes] folder at
Local Sites ➝ app ➝ public ➝ wp-content ➝ themes. Next you’ll want to activate the theme.
Activating your new WordPress theme
Now that your new theme is in your [themes] folder, let’s jump in to WordPress and activate it.
Point your browser at your newly created site (our example lives at mdv2.local). Use the same login credentials you input during the Local installation to get in to the Admin panel.
Go to the “Appearance” tab in the left sidebar and select “Themes”. You should see your new theme there (ours is mdv2). Click “Activate”.
Go back to your site and you’ll see that the default WordPress theme is gone and a standard, un-styled theme has taken its place. We now have a fresh start for our design styles.
So far, so good? Well buckle in, because we’re about to get to take things up a notch. This part of the article can get a little complex, so take it slow and we’ll walk you through it.
Codekit: Build websites faster and better
Codekit can do many things, but it’s probably most well known for it’s compiling, pre-processing, minification, and image optimization. All the things you want in your modern site build to keep file sizes and server requests to a minimum.
Codekit is a life-saver, a time-saver, and a sanity-saver. Yes, it costs $34, but it’s worth every penny.
With incredible support and documentation, we’re sure that Codekit will change the way you build sites.
But wait, before we get started with Codekit…
Because Codekit has built in compiling, we need to add two folders to our WordPress theme we just activated: a Source folder and a Build folder.
…ok, now we can install Codekit
Once you’ve downloaded, installed, and opened Codekit, you’ll be see a blank dashboard. Click on the “Add a project”.
From here, you’ll want to hunt down your theme folder. Once you find it, click “Add” and Codekit will create a new project for you.
You should see all the files and folders here, including the new Build and Source folders you just made.
The first step after confirming that your theme files are showing up properly is to click the Settings icon on the left hand side of the page. You’ll see a lot of options appear, click on “Browser Refreshing” first.
To enable automatic browser refreshing on your project, make sure to toggle on “External Server Required” and enter your Local site address in the input field.
Next, click on “Build Settings” underneath “Browser Refreshing” to set up the compiling. Make sure that “This project uses a build folder” is checked, the folder names are correct (they should be by default) and click “Apply Changes”.
Now you’ll want to set up the Sass options. Under “Languages”, select “Sass”. Set the “Output Style” to “Compressed” and make sure “Create a source map” and “Run Autoprefixer” are selected. The autoprefixer will append all browser-specific CSS to your stylesheets, a time-save and a half. Make sure your settings match up to the screenshot’s before moving on.
Now that we have all our settings saved, it’s time to download Bootstrap.
But why Bootstrap?
Besides being very popular, Bootstrap also shines a spotlight on being a responsive, mobile-first framework. Out of the box, Bootstrap makes your site look great across several device types—saving you tons of time and money.
Convinced? Ok, let’s install Bootstrap
Click on the cloud icon in the sidebar to see all the components available in the Codekit library. Click the “All Components” drop down and type in “bootstrap” to see the results.
Sort the results by “Stars” and look for the bootstrap by twbs project. There are several that are returned in the results, so take special care to download the correct one. Click “Install” and Codekit will handle the rest.
Once Codekit finishes installing Bootstrap, you’ll see a new folder in your theme directory called
bower_components. This is where Bootstrap lives. We’re now ready to move on to the next steps of adding and configuring Bootstrap for our WordPress theme.
Before we configure Bootstrap, read this…
Before we go further, it’s important to note that you don’t want to edit any of the files or folders inside the
Why, you ask? The most important reasons is because when a new version of Bootstrap is released, you’ll likely want to upgrade. And if you’ve edited those files to customize your site, all of those edits will be blown away when you upgrade. That’s no good.
So now you may be asking, “Ok, then how will we customize our version of Bootstrap for our new site?” Good question, and it’s simple really. We’ll copy the code from a few Bootstrap files and put it inside our Source folder to edit and customize without overwriting the source Bootstrap files. Easy as pie.
Configuring your site to use Bootstrap
Remember when we added the Source and Build folders to our WordPress theme folder above? Well now we’ll want to flesh these out a bit further.
First, in the
Sass folder, create a new file called
Also in the
Sass folder, create a sub-folder called
variables. Inside of the
variables folder, create a new file called
We’ll need both of these files in the following steps.
In your text editor, go to your theme directory and go to
bower_components ➝ bootstrap ➝ scss ➝ bootstrap.scss.
Copy everything underneath the commented section (all of the
@import code) and paste it in to your newly created
styles.scss file inside the
Next, go to
bower_components ➝ bootstrap ➝ scss ➝ _variables.scss. Copy all of these styles and paste them in to the
_bootstrap.scss file inside the newly created
variables folder in the
Now we’re ready to start editing our Bootstrap files without overwriting the core framework files in the
bower_components folder. Boom!
One thing to note here as an aside from the incredible Bootstrap documentation: “Every Sass variable in Bootstrap 4 includes the
!default flag allowing you to override the variable’s default value in your own Sass without modifying Bootstrap’s source code. Copy and paste variables as needed, modify their values, and remove the
!default flag. If a variable has already been assigned, then it won’t be re-assigned by the default values in Bootstrap.”
Setting up your stylesheet foundation
In the screenshot above, you’ll notice that the code looks a lot different than it did in the
bootstrap.scss file we just copied over. That’s because I’ve made some edits which I’ll explain in more detail below.
The first line references the
functions.scss file inside of the core Bootstrap folder. This is imported first so that all the other Bootstrap styles and mixins can run smoothly.
The second line references our custom Bootstrap file we just copied over from the core Bootstrap folder and put in the
After that, we
@import all of the other Bootstrap styles and dependencies we’ll need on our project. These include mixins, root, reboot, type, images, code, and grid.
Below those you’ll notice that we still have a TON more styles we could import from our Bootstrap core framework. We’ll only add them as needed so we don’t overload the server with requests.
Adding additional styles
After we have our basic
styles.scss file set up, we can start building upon it.
In the screenshot above, you’ll notice that I have added some new style declarations in the form of
@import. I’ve created a
blocks folder for general layout CSS, a
pages folder for page-specific CSS, and a
_general.scss file for global styles. I
@import them all below the Bootstrap styles so the fall beneath them in the cascade and override any unwanted/unneeded styles.
A couple odds and ends you need to do to get your stylesheets up and running
1. Delete your theme’s default styles
Go in to the theme’s
style.css file and delete everything but the comments. This will remove all the default styles from the Underscores theme and replace them with Bootstrap’s default styles.
2. Set up your Sass stylesheet to compile to the build folder
In order for your site to use your custom styles, you need to tell Codekit how to compile your stylesheet.
In Codekit, click on your
styles.scss. On the right, under “Output” make sure when the file changes it’s set to “Compile It”. Set the path to
build/css/style.css. That folder probably won’t exist yet, but you can add it during this process. Once you set the output path, click “Compile” and you should have your first stylesheet compiled.
3. Enqueue your new stylesheet
Before your new styles will show up on your theme, you need to tell WordPress where they live. Open up
functions.php inside of your theme folder and find the line that says “Enqueue scripts and styles”.
Update the path for the stylesheet to the following, noting that you’ll need to replace
mdv2 with your theme name:
wp_enqueue_style( 'mdv2-style', get_template_directory_uri() . '/build/css/style.css' );
wp_enqueue_script( 'mdv2-style', get_template_directory_uri() . '/bower_components/bootstrap/dist/js/bootstrap.min.js', array(), false, true );
You’re all set! Here’s what you should do next…
The first thing I like to do after getting my web development environment in order is to update some of the basic styles. Setting up things like typography, grids and grid-columns, and gutter-width will give you a good foundation for your build.
The second thing you should do is ask questions. If something is unclear or you’re confused, please don’t hesitate to leave us a comment below. This is a lot of info to document and explain, so any insight you can give us to make this article better is appreciated! We hope this helps and can’t wait to hear from you.