updating static site generators page

mattmakai · mattmakai · commit 082ef94b0eff · 2015-11-05T09:19:36.000-08:00
diff --git a/all.html b/all.html
@@ -3047,12 +3047,13 @@ <h2>How do static website generators work?</h2>
 as input then combine them to output a set of static HTML files.</p>
 <p><img src="theme/img/pelican-flow.jpg" width="100%" alt="Example of how static site generators work with a markup language and templates." class="technical-diagram"></a></p>
 <h2>What's the downside to using static site generators?</h2>
-<p>The major downside is that the code is not dynamic, so you won't be able to
-do many seemingly-necessary tasks provided by running an application created
-with a traditional <a href="/web-frameworks.html">web framework</a>. Any content that
-is typically powered by a database, such as comments, sessions and user data
-can only be done through third party services. For example, if you want to
-have comments on a static website you'd need to 
+<p>The major downside is that code cannot be executed after a site is created. 
+You are stuck with the output files so if you're used to building web 
+applications with a traditional <a href="/web-frameworks.html">web framework</a> you'll
+have to change your expectations. </p>
+<p>Content that is typically powered by a database, such as comments, sessions 
+and user data can only be handled through third party services. For example, 
+if you want to have comments on a static website you'd need to 
 <a href="https://disqus.com/">embed Disqus's form</a> and be completely reliant upon
 their service.</p>
 <p>Many web applications simply cannot be built with only a static site generator.
@@ -3061,7 +3062,7 @@ <h2>What's the downside to using static site generators?</h2>
 If done right, those web applications have the potential to scale better than
 if every page is rendered by the WSGI server. The complexity may or may not be
 worth it for your specific application.</p>
-<h2>Python static site generator implementations</h2>
+<h2>Python implementations</h2>
 <p>Numerous static website generators exist in many different languages. The
 ones listed here are primarily coded in Python.</p>
 <ul>
@@ -3074,6 +3075,14 @@ <h2>Python static site generator implementations</h2>
   AsciiDoc are supported with the default configuration.</p>
 </li>
 <li>
+<p><a href="http://www.mkdocs.org/">MkDocs</a> 
+  (<a href="https://github.com/mkdocs/mkdocs/">source code</a>) uses a YAML configuration
+  file to take Markdown files and an optional theme to output a documentation
+  site. The templating engine is Jinja, but a user doesn't have to create her
+  own templates unless a custom site is desired at which point it might make
+  more sense to use a different static site generator instead.</p>
+</li>
+<li>
 <p><a href="http://posativ.org/acrylamid/">Acrylamid</a> 
   (<a href="https://github.com/posativ/acrylamid">source code</a>) uses incremental 
   builds to generate static sites faster than recreating every page after
@@ -3114,6 +3123,11 @@ <h3>Static site generator resources</h3>
   <a href="http://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/">why static website generators are the next big thing</a>.
   I'd argue static website generators have been big for a long time now.</p>
 </li>
+<li>
+<p><a href="http://www.mattmakai.com/introduction-to-pelican.html">Getting started with Pelican and GitHub pages</a>
+  is a tutorial I wrote to use the Full Stack Python source code to create
+  and deploy your first static site.</p>
+</li>
 </ul>
           <h1>Data</h1>
 <p>Data is an incredibly broad topic but it can be broken down into many
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-11-04T16:49: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-11-05T09:16:58Z</updated></feed>
diff --git a/source/content/pages/04-web-development/16-static-site-generator.markdown b/source/content/pages/04-web-development/16-static-site-generator.markdown
@@ -47,12 +47,14 @@ as input then combine them to output a set of static HTML files.
 
 
 ## What's the downside to using static site generators?
-The major downside is that the code is not dynamic, so you won't be able to
-do many seemingly-necessary tasks provided by running an application created
-with a traditional [web framework](/web-frameworks.html). Any content that
-is typically powered by a database, such as comments, sessions and user data
-can only be done through third party services. For example, if you want to
-have comments on a static website you'd need to 
+The major downside is that code cannot be executed after a site is created. 
+You are stuck with the output files so if you're used to building web 
+applications with a traditional [web framework](/web-frameworks.html) you'll
+have to change your expectations. 
+
+Content that is typically powered by a database, such as comments, sessions 
+and user data can only be handled through third party services. For example, 
+if you want to have comments on a static website you'd need to 
 [embed Disqus's form](https://disqus.com/) and be completely reliant upon
 their service.
 
@@ -64,7 +66,7 @@ if every page is rendered by the WSGI server. The complexity may or may not be
 worth it for your specific application.
 
 
-## Python static site generator implementations
+## Python implementations
 Numerous static website generators exist in many different languages. The
 ones listed here are primarily coded in Python.
 
@@ -75,6 +77,13 @@ ones listed here are primarily coded in Python.
   primary templating engine is Jinja and Markdown, reStructuredText and
   AsciiDoc are supported with the default configuration.
 
+* [MkDocs](http://www.mkdocs.org/) 
+  ([source code](https://github.com/mkdocs/mkdocs/)) uses a YAML configuration
+  file to take Markdown files and an optional theme to output a documentation
+  site. The templating engine is Jinja, but a user doesn't have to create her
+  own templates unless a custom site is desired at which point it might make
+  more sense to use a different static site generator instead.
+
 * [Acrylamid](http://posativ.org/acrylamid/) 
   ([source code](https://github.com/posativ/acrylamid)) uses incremental 
   builds to generate static sites faster than recreating every page after
@@ -108,3 +117,7 @@ ones listed here are primarily coded in Python.
   [why static website generators are the next big thing](http://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/).
   I'd argue static website generators have been big for a long time now.
 
+* [Getting started with Pelican and GitHub pages](http://www.mattmakai.com/introduction-to-pelican.html)
+  is a tutorial I wrote to use the Full Stack Python source code to create
+  and deploy your first static site.
+
diff --git a/static-site-generator.html b/static-site-generator.html
@@ -63,12 +63,13 @@ <h2>How do static website generators work?</h2>
 as input then combine them to output a set of static HTML files.</p>
 <p><img src="theme/img/pelican-flow.jpg" width="100%" alt="Example of how static site generators work with a markup language and templates." class="technical-diagram"></a></p>
 <h2>What's the downside to using static site generators?</h2>
-<p>The major downside is that the code is not dynamic, so you won't be able to
-do many seemingly-necessary tasks provided by running an application created
-with a traditional <a href="/web-frameworks.html">web framework</a>. Any content that
-is typically powered by a database, such as comments, sessions and user data
-can only be done through third party services. For example, if you want to
-have comments on a static website you'd need to 
+<p>The major downside is that code cannot be executed after a site is created. 
+You are stuck with the output files so if you're used to building web 
+applications with a traditional <a href="/web-frameworks.html">web framework</a> you'll
+have to change your expectations. </p>
+<p>Content that is typically powered by a database, such as comments, sessions 
+and user data can only be handled through third party services. For example, 
+if you want to have comments on a static website you'd need to 
 <a href="https://disqus.com/">embed Disqus's form</a> and be completely reliant upon
 their service.</p>
 <p>Many web applications simply cannot be built with only a static site generator.
@@ -77,7 +78,7 @@ <h2>What's the downside to using static site generators?</h2>
 If done right, those web applications have the potential to scale better than
 if every page is rendered by the WSGI server. The complexity may or may not be
 worth it for your specific application.</p>
-<h2>Python static site generator implementations</h2>
+<h2>Python implementations</h2>
 <p>Numerous static website generators exist in many different languages. The
 ones listed here are primarily coded in Python.</p>
 <ul>
@@ -90,6 +91,14 @@ <h2>Python static site generator implementations</h2>
   AsciiDoc are supported with the default configuration.</p>
 </li>
 <li>
+<p><a href="http://www.mkdocs.org/">MkDocs</a> 
+  (<a href="https://github.com/mkdocs/mkdocs/">source code</a>) uses a YAML configuration
+  file to take Markdown files and an optional theme to output a documentation
+  site. The templating engine is Jinja, but a user doesn't have to create her
+  own templates unless a custom site is desired at which point it might make
+  more sense to use a different static site generator instead.</p>
+</li>
+<li>
 <p><a href="http://posativ.org/acrylamid/">Acrylamid</a> 
   (<a href="https://github.com/posativ/acrylamid">source code</a>) uses incremental 
   builds to generate static sites faster than recreating every page after
@@ -130,6 +139,11 @@ <h3>Static site generator resources</h3>
   <a href="http://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/">why static website generators are the next big thing</a>.
   I'd argue static website generators have been big for a long time now.</p>
 </li>
+<li>
+<p><a href="http://www.mattmakai.com/introduction-to-pelican.html">Getting started with Pelican and GitHub pages</a>
+  is a tutorial I wrote to use the Full Stack Python source code to create
+  and deploy your first static site.</p>
+</li>
 </ul>
 <h3>What else do you want to learn about Python web dev?</h3>
 <div class="row">

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-11-04T16:49: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-11-05T09:16:58Z</updated></feed>`