Commit message:

Add new file blog-template.html. Add new html versions of blog files.
Delete markdown versions of blogs. Add profile image for blog html pages.
Add css for blog-template.

diff --git a/blog/blog-template.html b/blog/blog-template.html
new file mode 100644
index 0000000..e16c4bd
--- /dev/null
+++ b/blog/blog-template.html
@@ -0,0 +1,48 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>blog template</title>
+  <link type="text/css" rel="stylesheet" href="../stylesheets/blog-stylesheet.css">
+</head>
+
+<body>
+
+<header>
+<img src="../imgs/jeremy_gagon.jpg" alt="Headshot Jeremy Gagon" />
+<div>
+<h1>Jeremy Gagon</h1>
+<h2>Web Developer</h2>
+</div>
+</header>
+
+<nav>
+<ul>
+  <li><a href="#">Home</a></li>
+  <li class="line"><a href="#">Portfolio</a></li>
+  <li class="line"><a href="#">Blog</a></li>
+  <li class="line"><a href="#">About Me</a></li>
+  <li class="line"><a href="#">Contact</a></li>
+</ul>
+</nav>
+
+<div id="blog">
+<h1>11/28/14 Title</h1>
+<!-- <h2>Secondary Title</h2> -->
+<p></p>
+<p></p>
+</div>
+
+</body>
+
+<footer>
+  <ul>
+  <li><a href="mailto:jergagon1@gmail.com">Email</a></li>
+  <li class="line"><a href="https://github.com/jergagon1">GitHub</a></li>
+  <li class="line"><a href="https://www.facebook.com/jeremygagon">Facebook</a></li>
+  <li class="line"><a href="https://twitter.com/jergagon1">Twitter</a></li>
+  <li class="line"><a href="http://www.quora.com/Jeremy-Gagon">Quora</a></li>
+  <li class="line"><a href="http://www.linkedin.com/pub/jeremy-gagon/30/750/285/">Linkedin</a></li>
+  </ul>
+</footer>
+
+</html>
\ No newline at end of file
diff --git a/blog/c1-chefs-kitchen.html b/blog/c1-chefs-kitchen.html
new file mode 100644
index 0000000..87b4c35
--- /dev/null
+++ b/blog/c1-chefs-kitchen.html
@@ -0,0 +1,86 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>blog template</title>
+  <link type="text/css" rel="stylesheet" href="../stylesheets/blog-stylesheet.css">
+</head>
+
+<body>
+
+<header>
+<img src="../imgs/jeremy_gagon.jpg" alt="Headshot Jeremy Gagon" />
+<div>
+<h1>Jeremy Gagon</h1>
+<h2>Web Developer</h2>
+</div>
+</header>
+
+<nav>
+<ul>
+  <li><a href="#">Home</a></li>
+  <li class="line"><a href="#">Portfolio</a></li>
+  <li class="line"><a href="#">Blog</a></li>
+  <li class="line"><a href="#">About Me</a></li>
+  <li class="line"><a href="#">Contact</a></li>
+</ul>
+</nav>
+
+<div id="blog">
+<h1>11/23/14 Cultural Blog: Chefs in the Kitchen</h1>
+
+<h2>Reflections on the Culture of Devbootcamp</h2>
+
+<p>As I set out on my journey with Devbootcamp, I am both extremely excited and extremely nervous. I believe these feelings stem from uncertainty about my skill level and the expectations of what I've signed up for.</p>
+
+<p>Luckily, there are some great resources available to students to help manage expectations including a video introduction to the culture of DBC: Shereef's Fireside Chat. In it, Shereef discusses how Devbootcamp came to be and how it has developed over time. He reflects on the culture and dynamics of how things work at DBC and some of the things that affect a student's success.</p>
+
+<p>The central theme of the chat is that Devbootcamp is a "big experiment". Things are constantly developing and changing. Students tend to succeed if they have a compatible mindset with the experiment.</p>
+
+<p>Students tend to arrive at Devbootcamp with one of two mindsets:</p>
+
+<p>The first is the "restaurant" mindset, where a student feels that they can get their education by paying money, getting a download of the material, completing a set of tasks and then going off to get a job. They want their education served up like something ordered from a restaurant.</p>
+
+<p>The second mindset is the "kitchen" mindset, where you show up and "put an apron on" to help make things happen.  You decide that you are going to make the experience your own. You engage, lead, show initiative, help, teach, learn, experiment, etc...</p>
+
+<p>Shereef talks about how most people have a mixture of these mindsets and that you need to learn to encourage one and discourage the other.</p>
+
+<p>The kitchen mindset is clearly the path to success at DBC as well as everything else in life.</p>
+
+<p>From watching Shereef's video, I have a very positive impression of DBC and I believe that the spirit of the school is in keeping with the culture of software development.</p>
+
+<p>My impression is that to be a software developer, you have to be open, curious, confident, willing to help others, willing to learn from others and able to work with other people in a highly productive and empathetic way. You share your expertise and freely admit your ignorance about something.</p>
+
+<p>I believe that DBC has been designed to help encourage these traits in students and my impression is that personal growth in these areas is far more important than just learning to code.</p>
+
+<p>I believe that this will be a great learning experience for me and I am ready to embrace the culture.
+</p>
+
+<p>In the past, I had a passive or reactive mindset about my career path. With that as my mindset, life provided exactly what I was asking for: a career path that I was not really happy with, my potential was unrealized and I was undervalued as an employee.</p>
+
+<p>DBC is the first specific deliberate career choice I have made. I am not afraid of the challenge of growing and making this my own. I am afraid of NOT doing so and ending up in the same random dead-end situation.
+</p>
+
+<p>In my research prior to signing up for DBC, I had a sense that it was a place where you made your own destiny based on your level of engagement and commitment. After watching Shereef's video, I am happy to know that I wasn't far off target. It was helpful to hear it explained explicitly.</p>
+
+<p>I am excited to participate in this learning environment because I feel I have a lot of room for growth in my emotional intelligence. I feel that growth in that area will unlock my potential.</p>
+
+<p>I am also nervous about the process for the same reason: I have a lot of room for growth in my emotional intelligence.</p>
+
+<p>I can't wait to see how I develop through the process.</p>
+
+</div>
+
+</body>
+
+<footer>
+  <ul>
+  <li><a href="mailto:jergagon1@gmail.com">Email</a></li>
+  <li class="line"><a href="https://github.com/jergagon1">GitHub</a></li>
+  <li class="line"><a href="https://www.facebook.com/jeremygagon">Facebook</a></li>
+  <li class="line"><a href="https://twitter.com/jergagon1">Twitter</a></li>
+  <li class="line"><a href="http://www.quora.com/Jeremy-Gagon">Quora</a></li>
+  <li class="line"><a href="http://www.linkedin.com/pub/jeremy-gagon/30/750/285/">Linkedin</a></li>
+  </ul>
+</footer>
+
+</html>
\ No newline at end of file
diff --git a/blog/c1-chefs-kitchen.md b/blog/c1-chefs-kitchen.md
deleted file mode 100644
index 79a2ffa..0000000
--- a/blog/c1-chefs-kitchen.md
+++ /dev/null
@@ -1,41 +0,0 @@
-Cultural Blog: Chefs in the Kitchen
-
-Reflections on the Culture of Devbootcamp
-
-November 23, 2014
-
-As I set out on my journey with Devbootcamp, I am both extremely excited and extremely nervous. I believe these feelings stem from uncertainty about my skill level and the expectations of what I've signed up for.
-
-Luckily, there are some great resources available to students to help manage expectations including a video introduction to the culture of DBC: Shereef's Fireside Chat. In it, Shereef discusses how Devbootcamp came to be and how it has developed over time. He reflects on the culture and dynamics of how things work at DBC and some of the things that affect a student's success.
-
-The central theme of the chat is that Devbootcamp is a "big experiment". Things are constantly developing and changing. Students tend to succeed if they have a compatible mindset with the experiment.
-
-Students tend to arrive at Devbootcamp with one of two mindsets:
-
-The first is the "restaurant" mindset, where a student feels that they can get their education by paying money, getting a download of the material, completing a set of tasks and then going off to get a job. They want their education served up like something ordered from a restaurant.
-
-The second mindset is the "kitchen" mindset, where you show up and "put an apron on" to help make things happen.  You decide that you are going to make the experience your own. You engage, lead, show initiative, help, teach, learn, experiment, etc...
-
-Shereef talks about how most people have a mixture of these mindsets and that you need to learn to encourage one and discourage the other.
-
-The kitchen mindset is clearly the path to success at DBC as well as everything else in life.
-
-From watching Shereef's video, I have a very positive impression of DBC and I believe that the spirit of the school is in keeping with the culture of software development.
-
-My impression is that to be a software developer, you have to be open, curious, confident, willing to help others, willing to learn from others and able to work with other people in a highly productive and empathetic way. You share your expertise and freely admit your ignorance about something.
-
-I believe that DBC has been designed to help encourage these traits in students and my impression is that personal growth in these areas is far more important than just learning to code.
-
-I believe that this will be a great learning experience for me and I am ready to embrace the culture.
-
-In the past, I had a passive or reactive mindset about my career path. With that as my mindset, life provided exactly what I was asking for: a career path that I was not really happy with, my potential was unrealized and I was undervalued as an employee.
-
-DBC is the first specific deliberate career choice I have made. I am not afraid of the challenge of growing and making this my own. I am afraid of NOT doing so and ending up in the same random dead-end situation.
-
-In my research prior to signing up for DBC, I had a sense that it was a place where you made your own destiny based on your level of engagement and commitment. After watching Shereef's video, I am happy to know that I wasn't far off target. It was helpful to hear it explained explicitly.
-
-I am excited to participate in this learning environment because I feel I have a lot of room for growth in my emotional intelligence. I feel that growth in that area will unlock my potential.
-
-I am also nervous about the process for the same reason: I have a lot of room for growth in my emotional intelligence.
-
-I can't wait to see how I develop through the process.
\ No newline at end of file
diff --git a/blog/t1-git-blog.html b/blog/t1-git-blog.html
new file mode 100644
index 0000000..93a4684
--- /dev/null
+++ b/blog/t1-git-blog.html
@@ -0,0 +1,85 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>blog template</title>
+  <link type="text/css" rel="stylesheet" href="../stylesheets/blog-stylesheet.css">
+</head>
+
+<body>
+
+<header>
+<img src="../imgs/jeremy_gagon.jpg" alt="Headshot Jeremy Gagon" />
+<div>
+<h1>Jeremy Gagon</h1>
+<h2>Web Developer</h2>
+</div>
+</header>
+
+<nav>
+<ul>
+  <li><a href="#">Home</a></li>
+  <li class="line"><a href="#">Portfolio</a></li>
+  <li class="line"><a href="#">Blog</a></li>
+  <li class="line"><a href="#">About Me</a></li>
+  <li class="line"><a href="#">Contact</a></li>
+</ul>
+</nav>
+
+<div id="blog">
+<h1>11/22/14 A Crash Course from a Crash Course Newbie</h1>
+<h2>Version Control, Git and GitHub</h2>
+
+<p>Welcome to my blog! I'm writing on the verge of completing my first week of Phase 0 at Devbootcamp. It's been awesome and I am excited to share some of the great things I've learned.</p>
+
+<p>This week focused on version control, Git and Github. These sound great, right? Except...you might not know what any of these are! Don't worry, you will in a few paragraphs - that's where the crash course comes in.
+</p>
+
+
+<p>Version control is simply a mechanism to track and record changes to files over time. As you work on code (or any other type of document), you have to make constant decisions about how to proceed: should I turn left or right? Should I use an array or a hash? Version control systems record the state of your files at key points so you can revert to those points if things go wrong.</p>
+
+<p>Using a version control system (VCS) also provides you with a level of backup for your project. Generally, you can recover lost or deleted files.</p>
+
+<p>The odds are pretty good that on a large development project, you won't be writing every line of code by yourself. Version control systems allow developers to collaborate on big projects by keeping track of who is working on what or if two people are working on different parts of the same thing.</p>
+
+<p>VCSs allow developers to experiment with ideas while not destroying the main repository of project code. The developer can save out a version (branch) of the source files (the tree) to try things out. If they work, the version control system can merge them back into the tree.  If not, no harm, no foul. You simply abandon the branch.</p>
+
+<h3>Okay, so what's Git?</h3>
+
+<p>Git is a popular free version control system developed originally by Linus Torvalds of Linux fame.</p>
+
+<p>Git is a distributed version control system which means that you download and run the software locally on your computer. Each collaborator has a full copy of all of the files and file history, so if one computer or server crashes, nothing is lost. Essentially, everyone has the master set of files. Awesome, right?</p>
+
+<p>Git tracks folders and detects when you make changes in them. If you add a file or change a comma in a document, Git knows. It will tell you if you type "git status" in your command line.</p>
+
+<p>There's a temporary staging area where you can hold files before you save them to Git. You can group a set of similar files together by adding them to the staging area with the command "git add my_awesome_file.rb" or better yet "git add ." to add all the files at once.</p>
+
+<p>Now that you have all of your files in the staging area, it's time to save them out. You do this with a "commit". A commit does a couple of things: it saves out a snapshot of the current state of the files, it allows you to add a message to describe what changed and it lets your collaborators know that you've saved stuff out and that they should get the latest files.</p>
+
+<h3>What's GitHub?</h3>
+
+<p>What if there was a place on the internet where you could put your awesome Git folder and all of your collaborators could upload and download changes whenever they were online? What if there was a place where you could post your code and brilliant people would help you fix bugs, suggest improvements and even write code for you? GitHub is that place.</p>
+
+<p>GitHub allows developers to post code in open repositories that other developers can view, tweak and use in their own projects. It's a collaborative hub for developers to share their expertise.</p>
+
+<p>For a fee, individuals or organizations can have private repositories, but the free accounts are open to everyone.</p>
+
+<p>Varying types of open source licenses can be included with your project repository on GitHub to offer some control over redistribution and use of your code, but generally open source licenses favor less restriction and encourage code reuse.</p>
+
+<p>On to week 2!!!</p>
+
+</div>
+
+</body>
+
+<footer>
+  <ul>
+  <li><a href="mailto:jergagon1@gmail.com">Email</a></li>
+  <li class="line"><a href="https://github.com/jergagon1">GitHub</a></li>
+  <li class="line"><a href="https://www.facebook.com/jeremygagon">Facebook</a></li>
+  <li class="line"><a href="https://twitter.com/jergagon1">Twitter</a></li>
+  <li class="line"><a href="http://www.quora.com/Jeremy-Gagon">Quora</a></li>
+  <li class="line"><a href="http://www.linkedin.com/pub/jeremy-gagon/30/750/285/">Linkedin</a></li>
+  </ul>
+</footer>
+
+</html>
\ No newline at end of file
diff --git a/blog/t1-git-blog.md b/blog/t1-git-blog.md
deleted file mode 100644
index 6e8e37a..0000000
--- a/blog/t1-git-blog.md
+++ /dev/null
@@ -1,41 +0,0 @@
-A Crash Course from a Crash Course Newbie
-
-Version Control, Git and GitHub
-
-November 22, 2014
-
-Welcome to my blog! I'm writing on the verge of completing my first week of Phase 0 at Devbootcamp. It's been awesome and I am excited to share some of the great things I've learned.
-
-This week focused on version control, Git and Github. These sound great, right? Except...you might not know what any of these are! Don't worry, you will in a few paragraphs - that's where the crash course comes in.
-
-Version control is simply a mechanism to track and record changes to files over time. As you work on code (or any other type of document), you have to make constant decisions about how to proceed: should I turn left or right? Should I use an array or a hash? Version control systems record the state of your files at key points so you can revert to those points if things go wrong.
-
-Using a version control system (VCS) also provides you with a level of backup for your project. Generally, you can recover lost or deleted files.
-
-The odds are pretty good that on a large development project, you won't be writing every line of code by yourself. Version control systems allow developers to collaborate on big projects by keeping track of who is working on what or if two people are working on different parts of the same thing.
-
-VCSs allow developers to experiment with ideas while not destroying the main repository of project code. The developer can save out a version (branch) of the source files (the tree) to try things out. If they work, the version control system can merge them back into the tree.  If not, no harm, no foul. You simply abandon the branch.
-
-Okay, so what's Git?
-
-Git is a popular free version control system developed originally by Linus Torvalds of Linux fame.
-
-Git is a distributed version control system which means that you download and run the software locally on your computer. Each collaborator has a full copy of all of the files and file history, so if one computer or server crashes, nothing is lost. Essentially, everyone has the master set of files. Awesome, right?
-
-Git tracks folders and detects when you make changes in them. If you add a file or change a comma in a document, Git knows. It will tell you if you type "git status" in your command line.
-
-There's a temporary staging area where you can hold files before you save them to Git. You can group a set of similar files together by adding them to the staging area with the command "git add my_awesome_file.rb" or better yet "git add ." to add all the files at once.
-
-Now that you have all of your files in the staging area, it's time to save them out. You do this with a "commit". A commit does a couple of things: it saves out a snapshot of the current state of the files, it allows you to add a message to describe what changed and it lets your collaborators know that you've saved stuff out and that they should get the latest files.
-
-What's GitHub?
-
-What if there was a place on the internet where you could put your awesome Git folder and all of your collaborators could upload and download changes whenever they were online? What if there was a place where you could post your code and brilliant people would help you fix bugs, suggest improvements and even write code for you? GitHub is that place.
-
-GitHub allows developers to post code in open repositories that other developers can view, tweak and use in their own projects. It's a collaborative hub for developers to share their expertise.
-
-For a fee, individuals or organizations can have private repositories, but the free accounts are open to everyone.
-
-Varying types of open source licenses can be included with your project repository on GitHub to offer some control over redistribution and use of your code, but generally open source licenses favor less restriction and encourage code reuse.
-
-On to week 2!!!
\ No newline at end of file
diff --git a/imgs/jeremy_gagon.jpg b/imgs/jeremy_gagon.jpg
new file mode 100644
index 0000000..e1020b7
Binary files /dev/null and b/imgs/jeremy_gagon.jpg differ
diff --git a/stylesheets/blog-stylesheet.css b/stylesheets/blog-stylesheet.css
new file mode 100644
index 0000000..b98bfe6
--- /dev/null
+++ b/stylesheets/blog-stylesheet.css
@@ -0,0 +1,110 @@
+* {
+	font-family: sans-serif;
+}
+
+body {
+	padding: 20px;
+}
+
+header img {
+	float: left;
+	height: 100px;
+	width: 100px;
+}
+
+header div {
+	float: left;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+	padding-top: 40px;
+	padding-left: 10px;
+}
+
+header h1 {
+	font-size: 24px;
+	font-weight: 600;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+	font-family: sans-serif;
+
+}
+
+header h2 {
+	font-size: 16px;
+	font-weight: 500;
+	font-family: sans-serif;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+	padding-top: 0px;
+	margin-top: 0px;
+}
+
+nav {
+	border-bottom: 1px solid black;
+	padding-bottom: 10px;
+}
+
+nav a {
+	text-decoration: none;
+}
+
+nav ul {
+	clear: both;
+	padding-left: 0px;
+	padding-top: 10px;
+}
+
+nav li {
+	float: left;
+	padding-right: 10px;
+	list-style: none;
+}
+
+.line {
+	border-left: 1px solid black;
+	padding-left: 10px;
+}
+
+#blog {
+	border-bottom: 1px solid black;
+}
+
+#blog h1 {
+	font-size: 20px;
+	font-weight: 500;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+}
+
+#blog h2 {
+	font-size: 18px;
+	font-weight: 500;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+}
+
+#blog h3 {
+	font-size: 16px;
+	font-weight: 500;
+	padding-bottom: 0px;
+	margin-bottom: 0px;
+}
+
+#blog p {
+	padding-top: 0px;
+	margin-top: 10px;
+}
+
+footer a {
+	text-decoration: none;
+}
+
+footer ul {
+	padding-left: 0px;
+}
+
+footer li {
+	float: left;
+	padding-right: 10px;
+	list-style: none;
+}
\ No newline at end of file