We have come a long, long way since you were creating your GitHub account and using JavaScript just as a calculator. Yet with the couple of basic types I taught you, you are able to make a fully interactive web project by making use of Bootstrap, jQuery, and Leaflet. Hopefully your own personal project is coming along as well as the “Could Be” Project has. More importantly, hopefully you’ve figured out a few tricks of your own to get your project to meet your desires and to make your wireframe a reality.

In this final chapter, we’ll do two things: do some blanket styling on your project so it doesn’t totally look like a default Bootstrap website, and then put it live so that you can have a URL you can share with your friends, family, and, also importantly, me, your instructor.

Big style changes

Because the section on CSS was so short, I’ll include some CSS here to inspire you to change your own style sheets for your project. First, let’s change the font. Fonts have to be loaded from somewhere, and, luckily, Google offers that service through fonts.google.com. When you find a font you like there, you click on the red circle with a white cross, and a black bar appears on the bottom of your browser window. When you click on the white line on that bar, a subwindow opens. If you click on “@import,” you get something that looks like this:

@import url("https://fonts.googleapis.com/css?family=Garamond");

Now, in your style sheet, you have to include that line at the top. Then, below, you can define the <body> font as Garamond.

body {
  font-family: "EB Garamond", serif;

Leaflet forces the use of its own font, however, so override it this way:

.leaflet-container {
  font-family: "EB Garamond", serif;

Now I can change the background color for the page as a whole and for the popups:

body, .leaflet-popup-content-wrapper, .leaflet-popup-tip {
  background-color: #fdf6e3;

We could keep going on, adding borders, etc. But here’s a good place to stop. You can view the “finished” version of this “Could Be” Project here.

Going live

Since I’ve started working on the “Could Be” Project, and you’ve been working on your own project, I hope that you have been saving and committing along the way to your GitHub repository. I also hope you’ve been pushing your commits up to GitHub. If the latest and greatest is pushed to GitHub, then going live is a one-minute procedure.

  1. Go to your repository’s page on Github.com.
  2. Click on the “Settings” tab near the top.
  3. Scroll down to “GitHub Pages.”
  4. Click on “None,” choose “Master Branch.”
  5. Click “Save.”
  6. Scroll back down to “GitHub Pages” and you should see something like “Your site is ready to be published at https://YOURUSERNAME.github.io/javascripting-english-major-project/.”

That last line is the URL to your project, with your project’s .html file added to the end, like could-be.html. If you want to rename your project’s file to index.html (thereby replacing the index.html you were working on at the beginning of the course), that would simplify things. Now you can share that with your friends. You can also keep making changes by editing files in Atom, committing, and then pushing back up to GitHub.


And that’s it! We’ve laughed, we’ve cried, we talked a lot about burritos until it got time to start building web sites. And now you know how to use JavaScript and can go on making sites, learning more about Leaflet, Bootstrap, jQuery, and even other, more exciting libraries, like d3.js.

I recommend having a look at the HTML, JavaScript, and CSS for the “final” version of the “Could Be” Project. You can see them here:

I’ve gone through and changed around the JavaScript rather substantially to make it easier to understand as a whole, and I’ve commented it, too. Hopefully it will inspire you, too.

Finally, please let me know what kinds of amazing things you go on to create, and I hope your learning process has been as enjoyable as my writing this course (and teaching it) has been.


  1. Style your project. Then, go live.