This is going to be a planning lesson, sorry, not code for this one. If you are wondering why we will occasionally take a step back before implementing a feature, take a look at our sign:

Yes, planning is important. With that in mind let's put together a plan on what needs to get done in order to implement our design:

1. As with all new features, perform all work on an isolated git branch

2. Integrate the CSS files into the Rails asset pipeline

3. Configure the master layout file

4. Integrate shared items, such as the navigation and footer into view partials that can be shared across pages

5. Implement each of layouts for each page, including Topics, Topic, Posts, Post, you get the idea. We can follow our design guide in the requirements document

Let's start by creating the git branch, first ensure that you're on the master branch and that you have the latest version of the code:

git branch

If it doesn't highly master, run git checkout master to get back to the master branch.

Then run:

git pull

This will pull down all of the latest changes, such as our latest code from the add-posts pull request. If you have any conflicts, such as work performed on the local master branch that conflicts with the pull request it will let you know which files need to be cleaned up. If there were any changes to be made make sure you push up the code to the remote master branch by running git push.

Now let's create the new feature branch by running:

git checkout -b add-design

And with that branch done we're ready to start integrating the design and making our application look more professional.

Resources

• Design Assets Zip File