fixing up the source and app dependencies pages

mattmakai · mattmakai · commit 35427aaa5480 · 2015-06-02T07:10:20.000-04:00
diff --git a/all.html b/all.html
@@ -4647,24 +4647,29 @@ <h2>Git resources</h2>
 </li>
 </ul>
 <h2>Source control learning checklist</h2>
-<p><i class="fa fa-check-square-o"></i>
-Pick a version control system. Git is recommended because on the web there 
-are a significant number of tutorials to help both new and advanced users.</p>
-<p><i class="fa fa-check-square-o"></i>
-Learn basic use cases for version control such as committing changes, rolling 
-back to earlier file versions and searching for when lines of code were 
-modified during development history.</p>
-<p><i class="fa fa-check-square-o"></i>
-Ensure your source code is backed up in a central repository. A central
-repository is critical not only if your local development version is corrupted
-but also for the deployment process.</p>
-<p><i class="fa fa-check-square-o"></i>
-Integrate source control into your deployment process in three ways. First,
-pull the project source code from version control during deployments. Second, 
-kick off deployments when code is modified by using webhooks or polling on 
-the repository. Third, ensure you can roll back to a previous version if a 
-code deployment goes wrong.</p>
-<h3>Now that your source code is versioned, what's next?</h3>
+<ol>
+<li>
+<p>Pick a version control system. Git is recommended because on the web there
+   are a significant number of tutorials to help both new and advanced users.</p>
+</li>
+<li>
+<p>Learn basic use cases for version control such as committing changes, 
+   rolling back to earlier file versions and searching for when lines of code 
+   were modified during development history.</p>
+</li>
+<li>
+<p>Ensure your source code is backed up in a central repository. A central
+   repository is critical not only if your local development version is 
+   corrupted but also for the deployment process.</p>
+</li>
+<li>
+<p>Integrate source control into your deployment process in three ways. First,
+   pull the project source code from version control during deployments. 
+   Second, kick off deployments when code is modified by using webhooks or 
+   polling on the repository. Third, ensure you can roll back to a previous 
+   version if a code deployment goes wrong.</p>
+</li>
+</ol>
           <h1>Application Dependencies</h1>
 <p>Application dependencies are the libraries other than your project code
 that are required to create and run your application. </p>
@@ -4824,20 +4829,25 @@ <h2>Open source app dependency projects</h2>
 </li>
 </ul>
 <h2>Application dependencies learning checklist</h2>
-<p><i class="fa fa-check-square-o"></i>
-Ensure the libraries your web application depends on are all captured in a
-requirement.txt file with pegged versions. </p>
-<p><i class="fa fa-check-square-o"></i>
-An easy way to capture currently installed dependencies is with the 
-<code>pip freeze</code> command.</p>
-<p><i class="fa fa-check-square-o"></i>
-Create a fresh virtualenv and install the dependencies from your 
-requirements.txt file by using the <code>pip install -r requirements.txt</code> 
-command.</p>
-<p><i class="fa fa-check-square-o"></i>
-Check that your application runs properly with the fresh virtualenv and only
-the installed dependencies from the requirements.txt file.</p>
-<h3>What do you need to learn after installing your app dependencies?</h3>
+<ol>
+<li>
+<p>Ensure the libraries your web application depends on are all captured in 
+   a requirement.txt file with pegged versions. </p>
+</li>
+<li>
+<p>An easy way to capture currently installed dependencies is with the 
+   <code>pip freeze</code> command.</p>
+</li>
+<li>
+<p>Create a fresh virtualenv and install the dependencies from your 
+   requirements.txt file by using the <code>pip install -r requirements.txt</code> 
+   command.</p>
+</li>
+<li>
+<p>Check that your application runs properly with the fresh virtualenv and 
+   only the installed dependencies from the requirements.txt file.</p>
+</li>
+</ol>
           <h1>Static content</h1>
 <p>Some content on a website does not change and therefore should be served
 up either directly through the web server or a content delivery network (CDN).
diff --git a/application-dependencies.html b/application-dependencies.html
@@ -193,20 +193,26 @@ <h2>Open source app dependency projects</h2>
 </li>
 </ul>
 <h2>Application dependencies learning checklist</h2>
-<p><i class="fa fa-check-square-o"></i>
-Ensure the libraries your web application depends on are all captured in a
-requirement.txt file with pegged versions. </p>
-<p><i class="fa fa-check-square-o"></i>
-An easy way to capture currently installed dependencies is with the 
-<code>pip freeze</code> command.</p>
-<p><i class="fa fa-check-square-o"></i>
-Create a fresh virtualenv and install the dependencies from your 
-requirements.txt file by using the <code>pip install -r requirements.txt</code> 
-command.</p>
-<p><i class="fa fa-check-square-o"></i>
-Check that your application runs properly with the fresh virtualenv and only
-the installed dependencies from the requirements.txt file.</p>
-<h3>What do you need to learn after installing your app dependencies?</h3>
+<ol>
+<li>
+<p>Ensure the libraries your web application depends on are all captured in 
+   a requirement.txt file with pegged versions. </p>
+</li>
+<li>
+<p>An easy way to capture currently installed dependencies is with the 
+   <code>pip freeze</code> command.</p>
+</li>
+<li>
+<p>Create a fresh virtualenv and install the dependencies from your 
+   requirements.txt file by using the <code>pip install -r requirements.txt</code> 
+   command.</p>
+</li>
+<li>
+<p>Check that your application runs properly with the fresh virtualenv and 
+   only the installed dependencies from the requirements.txt file.</p>
+</li>
+</ol>
+<h3>What's next after installing app dependencies?</h3>
 <div class="row">
     <div class="col-md-4">
         <div class="well select-next">
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-31T13:47:14Z</updated></feed>
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-06-02T07:10:09Z</updated></feed>
diff --git a/source-control.html b/source-control.html
@@ -186,24 +186,30 @@ <h2>Git resources</h2>
 </li>
 </ul>
 <h2>Source control learning checklist</h2>
-<p><i class="fa fa-check-square-o"></i>
-Pick a version control system. Git is recommended because on the web there 
-are a significant number of tutorials to help both new and advanced users.</p>
-<p><i class="fa fa-check-square-o"></i>
-Learn basic use cases for version control such as committing changes, rolling 
-back to earlier file versions and searching for when lines of code were 
-modified during development history.</p>
-<p><i class="fa fa-check-square-o"></i>
-Ensure your source code is backed up in a central repository. A central
-repository is critical not only if your local development version is corrupted
-but also for the deployment process.</p>
-<p><i class="fa fa-check-square-o"></i>
-Integrate source control into your deployment process in three ways. First,
-pull the project source code from version control during deployments. Second, 
-kick off deployments when code is modified by using webhooks or polling on 
-the repository. Third, ensure you can roll back to a previous version if a 
-code deployment goes wrong.</p>
-<h3>Now that your source code is versioned, what's next?</h3>
+<ol>
+<li>
+<p>Pick a version control system. Git is recommended because on the web there
+   are a significant number of tutorials to help both new and advanced users.</p>
+</li>
+<li>
+<p>Learn basic use cases for version control such as committing changes, 
+   rolling back to earlier file versions and searching for when lines of code 
+   were modified during development history.</p>
+</li>
+<li>
+<p>Ensure your source code is backed up in a central repository. A central
+   repository is critical not only if your local development version is 
+   corrupted but also for the deployment process.</p>
+</li>
+<li>
+<p>Integrate source control into your deployment process in three ways. First,
+   pull the project source code from version control during deployments. 
+   Second, kick off deployments when code is modified by using webhooks or 
+   polling on the repository. Third, ensure you can roll back to a previous 
+   version if a code deployment goes wrong.</p>
+</li>
+</ol>
+<h3>What do you want to learn about after source control?</h3>
 <div class="row">
     <div class="col-md-4">
         <div class="well select-next">
diff --git a/source/content/pages/07-web-app-deployment/08-source-control.markdown b/source/content/pages/07-web-app-deployment/08-source-control.markdown
@@ -141,26 +141,20 @@ reviews the basics of distributed version control systems.
 
 
 ## Source control learning checklist
-<i class="fa fa-check-square-o"></i>
-Pick a version control system. Git is recommended because on the web there 
-are a significant number of tutorials to help both new and advanced users.
+1. Pick a version control system. Git is recommended because on the web there
+   are a significant number of tutorials to help both new and advanced users.
 
-<i class="fa fa-check-square-o"></i>
-Learn basic use cases for version control such as committing changes, rolling 
-back to earlier file versions and searching for when lines of code were 
-modified during development history.
+1. Learn basic use cases for version control such as committing changes, 
+   rolling back to earlier file versions and searching for when lines of code 
+   were modified during development history.
 
-<i class="fa fa-check-square-o"></i>
-Ensure your source code is backed up in a central repository. A central
-repository is critical not only if your local development version is corrupted
-but also for the deployment process.
+1. Ensure your source code is backed up in a central repository. A central
+   repository is critical not only if your local development version is 
+   corrupted but also for the deployment process.
 
-<i class="fa fa-check-square-o"></i>
-Integrate source control into your deployment process in three ways. First,
-pull the project source code from version control during deployments. Second, 
-kick off deployments when code is modified by using webhooks or polling on 
-the repository. Third, ensure you can roll back to a previous version if a 
-code deployment goes wrong.
+1. Integrate source control into your deployment process in three ways. First,
+   pull the project source code from version control during deployments. 
+   Second, kick off deployments when code is modified by using webhooks or 
+   polling on the repository. Third, ensure you can roll back to a previous 
+   version if a code deployment goes wrong.
 
-
-### Now that your source code is versioned, what's next?
diff --git a/source/content/pages/07-web-app-deployment/09-app-dependencies.markdown b/source/content/pages/07-web-app-deployment/09-app-dependencies.markdown
@@ -164,22 +164,16 @@ further clarification.
 
 
 ## Application dependencies learning checklist
-<i class="fa fa-check-square-o"></i>
-Ensure the libraries your web application depends on are all captured in a
-requirement.txt file with pegged versions. 
+1. Ensure the libraries your web application depends on are all captured in 
+   a requirement.txt file with pegged versions. 
 
-<i class="fa fa-check-square-o"></i>
-An easy way to capture currently installed dependencies is with the 
-``pip freeze`` command.
+1. An easy way to capture currently installed dependencies is with the 
+   ``pip freeze`` command.
 
-<i class="fa fa-check-square-o"></i>
-Create a fresh virtualenv and install the dependencies from your 
-requirements.txt file by using the ``pip install -r requirements.txt`` 
-command.
+1. Create a fresh virtualenv and install the dependencies from your 
+   requirements.txt file by using the ``pip install -r requirements.txt`` 
+   command.
 
-<i class="fa fa-check-square-o"></i>
-Check that your application runs properly with the fresh virtualenv and only
-the installed dependencies from the requirements.txt file.
+1. Check that your application runs properly with the fresh virtualenv and 
+   only the installed dependencies from the requirements.txt file.
 
-
-### What do you need to learn after installing your app dependencies?
diff --git a/source/theme/templates/choices/application-dependencies.html b/source/theme/templates/choices/application-dependencies.html
@@ -1,3 +1,4 @@
+<h3>What's next after installing app dependencies?</h3>
 <div class="row">
     <div class="col-md-4">
         <div class="well select-next">
diff --git a/source/theme/templates/choices/source-control.html b/source/theme/templates/choices/source-control.html
@@ -1,3 +1,4 @@
+<h3>What do you want to learn about after source control?</h3>
 <div class="row">
     <div class="col-md-4">
         <div class="well select-next">

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	`<?xml version="1.0" encoding="utf-8"?>`
`2`		`-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-31T13:47:14Z</updated></feed>`
	`2`	`+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-06-02T07:10:09Z</updated></feed>`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,4 @@`
	`1`	`+<h3>What's next after installing app dependencies?</h3>`
`1`	`2`	`<div class="row">`
`2`	`3`	`<div class="col-md-4">`
`3`	`4`	`<div class="well select-next">`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,4 @@`
	`1`	`+<h3>What do you want to learn about after source control?</h3>`
`1`	`2`	`<div class="row">`
`2`	`3`	`<div class="col-md-4">`
`3`	`4`	`<div class="well select-next">`