Skip to content

Commit 3d08c83

Browse files
committed
update static site generator page and changelog
1 parent 833e204 commit 3d08c83

File tree

5 files changed

+47
-47
lines changed

5 files changed

+47
-47
lines changed

all.html

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4675,27 +4675,30 @@ <h2>What's the downside of using static site generators?</h2>
46754675
if you want to have comments on a static website you'd need to
46764676
<a href="https://disqus.com/">embed Disqus's form</a> and be completely reliant upon
46774677
their service.</p>
4678-
<p>Many web applications simply cannot be built with only a static site generator.
4679-
However, a static website generator can create part of a site that will be
4680-
served up by a web server while other pages are handled by the WSGI server.
4681-
If done right, those web applications have the potential to scale better than
4682-
if every page is rendered by the WSGI server. The complexity may or may not be
4683-
worth it for your specific application.</p>
4678+
<p>Many web applications simply cannot be built with only a static site
4679+
generator. However, a static website generator can create part of a site
4680+
that will be served up by a web server while other pages are handled by the
4681+
WSGI server. If done right, those web applications have the potential to
4682+
scale better than if every page is rendered by the WSGI server. The
4683+
complexity may or may not be worth it for your specific application.</p>
46844684
<h2>Python implementations</h2>
46854685
<p>Numerous static website generators exist in many different languages. The
46864686
ones listed here are primarily coded in Python.</p>
46874687
<ul>
46884688
<li>
4689-
<p><a href="http://blog.getpelican.com/">Pelican</a>
4690-
(<a href="https://github.com/getpelican/pelican">source code</a>)
4689+
<p><a href="/pelican.html">Pelican</a>
46914690
is a commonly used Python static website generator which is used to create
46924691
<a href="https://github.com/mattmakai/fullstackpython.com">Full Stack Python</a>. The
46934692
primary templating engine is Jinja and Markdown, reStructuredText and
46944693
AsciiDoc are supported with the default configuration.</p>
46954694
</li>
46964695
<li>
4697-
<p><a href="http://www.mkdocs.org/">MkDocs</a>
4698-
(<a href="https://github.com/mkdocs/mkdocs/">source code</a>) uses a YAML configuration
4696+
<p><a href="/lektor.html">Lektor</a> is a static content management system and site
4697+
generator that can deploy its output to any webserver. It uses
4698+
<a href="/jinja2.html">Jinja2</a> as its <a href="/template-engines.html">template engine</a>.</p>
4699+
</li>
4700+
<li>
4701+
<p><a href="/mkdocs.html">MkDocs</a> uses a YAML configuration
46994702
file to take Markdown files and an optional theme to output a documentation
47004703
site. The templating engine is Jinja, but a user doesn't have to create her
47014704
own templates unless a custom site is desired at which point it might make
@@ -4734,12 +4737,6 @@ <h2>Python implementations</h2>
47344737
"experimental" phase.</p>
47354738
</li>
47364739
<li>
4737-
<p><a href="https://www.getlektor.com/">Lektor</a>
4738-
(<a href="https://github.com/lektor/lektor">source code</a>) is a Python static
4739-
content management system that can deploy to any webserver. It uses
4740-
<a href="/jinja2.html">Jinja2</a> as a <a href="/template-engines.html">template engine</a>.</p>
4741-
</li>
4742-
<li>
47434740
<p><a href="http://complexity.readthedocs.org/en/latest/">Complexity</a>
47444741
(<a href="https://github.com/audreyr/complexity">source code</a>) is a site generator
47454742
for users who like to work in HTML. It uses HTML for templating but
@@ -9815,6 +9812,9 @@ <h1>Change Log</h1>
98159812
<h2>2016</h2>
98169813
<h3>December</h3>
98179814
<ul>
9815+
<li>Added a small <a href="/mkdocs.html">MkDocs</a> page that needs to be expanded.</li>
9816+
<li>Updated the <a href="/nginx.html">Nginx</a> page with a better description of reverse
9817+
proxies.</li>
98189818
<li>Add new <a href="/lektor.html">Lektor</a> page. Will be expanded upon during the
98199819
month as I get to use the library.</li>
98209820
<li>Merged <a href="https://github.com/mattmakai/fullstackpython.com/pull/111">PR #111</a>

change-log.html

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,9 @@ <h1>Change Log</h1>
4343
<h2>2016</h2>
4444
<h3>December</h3>
4545
<ul>
46+
<li>Added a small <a href="/mkdocs.html">MkDocs</a> page that needs to be expanded.</li>
47+
<li>Updated the <a href="/nginx.html">Nginx</a> page with a better description of reverse
48+
proxies.</li>
4649
<li>Add new <a href="/lektor.html">Lektor</a> page. Will be expanded upon during the
4750
month as I get to use the library.</li>
4851
<li>Merged <a href="https://github.com/mattmakai/fullstackpython.com/pull/111">PR #111</a>

source/content/pages/07-web-development/28-static-site-generator.markdown

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -60,27 +60,29 @@ if you want to have comments on a static website you'd need to
6060
[embed Disqus's form](https://disqus.com/) and be completely reliant upon
6161
their service.
6262

63-
Many web applications simply cannot be built with only a static site generator.
64-
However, a static website generator can create part of a site that will be
65-
served up by a web server while other pages are handled by the WSGI server.
66-
If done right, those web applications have the potential to scale better than
67-
if every page is rendered by the WSGI server. The complexity may or may not be
68-
worth it for your specific application.
63+
Many web applications simply cannot be built with only a static site
64+
generator. However, a static website generator can create part of a site
65+
that will be served up by a web server while other pages are handled by the
66+
WSGI server. If done right, those web applications have the potential to
67+
scale better than if every page is rendered by the WSGI server. The
68+
complexity may or may not be worth it for your specific application.
6969

7070

7171
## Python implementations
7272
Numerous static website generators exist in many different languages. The
7373
ones listed here are primarily coded in Python.
7474

75-
* [Pelican](http://blog.getpelican.com/)
76-
([source code](https://github.com/getpelican/pelican))
75+
* [Pelican](/pelican.html)
7776
is a commonly used Python static website generator which is used to create
7877
[Full Stack Python](https://github.com/mattmakai/fullstackpython.com). The
7978
primary templating engine is Jinja and Markdown, reStructuredText and
8079
AsciiDoc are supported with the default configuration.
8180

82-
* [MkDocs](http://www.mkdocs.org/)
83-
([source code](https://github.com/mkdocs/mkdocs/)) uses a YAML configuration
81+
* [Lektor](/lektor.html) is a static content management system and site
82+
generator that can deploy its output to any webserver. It uses
83+
[Jinja2](/jinja2.html) as its [template engine](/template-engines.html).
84+
85+
* [MkDocs](/mkdocs.html) uses a YAML configuration
8486
file to take Markdown files and an optional theme to output a documentation
8587
site. The templating engine is Jinja, but a user doesn't have to create her
8688
own templates unless a custom site is desired at which point it might make
@@ -114,11 +116,6 @@ ones listed here are primarily coded in Python.
114116
structure so the site can be generated. The project remains in the
115117
"experimental" phase.
116118

117-
* [Lektor](https://www.getlektor.com/)
118-
([source code](https://github.com/lektor/lektor)) is a Python static
119-
content management system that can deploy to any webserver. It uses
120-
[Jinja2](/jinja2.html) as a [template engine](/template-engines.html).
121-
122119
* [Complexity](http://complexity.readthedocs.org/en/latest/)
123120
([source code](https://github.com/audreyr/complexity)) is a site generator
124121
for users who like to work in HTML. It uses HTML for templating but

source/content/pages/12-meta/01-change-log.markdown

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ inception in December 2012. You can view detailed changes via the
1515

1616
## 2016
1717
### December
18+
* Added a small [MkDocs](/mkdocs.html) page that needs to be expanded.
19+
* Updated the [Nginx](/nginx.html) page with a better description of reverse
20+
proxies.
1821
* Add new [Lektor](/lektor.html) page. Will be expanded upon during the
1922
month as I get to use the library.
2023
* Merged [PR #111](https://github.com/mattmakai/fullstackpython.com/pull/111)

static-site-generator.html

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -77,27 +77,30 @@ <h2>What's the downside of using static site generators?</h2>
7777
if you want to have comments on a static website you'd need to
7878
<a href="https://disqus.com/">embed Disqus's form</a> and be completely reliant upon
7979
their service.</p>
80-
<p>Many web applications simply cannot be built with only a static site generator.
81-
However, a static website generator can create part of a site that will be
82-
served up by a web server while other pages are handled by the WSGI server.
83-
If done right, those web applications have the potential to scale better than
84-
if every page is rendered by the WSGI server. The complexity may or may not be
85-
worth it for your specific application.</p>
80+
<p>Many web applications simply cannot be built with only a static site
81+
generator. However, a static website generator can create part of a site
82+
that will be served up by a web server while other pages are handled by the
83+
WSGI server. If done right, those web applications have the potential to
84+
scale better than if every page is rendered by the WSGI server. The
85+
complexity may or may not be worth it for your specific application.</p>
8686
<h2>Python implementations</h2>
8787
<p>Numerous static website generators exist in many different languages. The
8888
ones listed here are primarily coded in Python.</p>
8989
<ul>
9090
<li>
91-
<p><a href="http://blog.getpelican.com/">Pelican</a>
92-
(<a href="https://github.com/getpelican/pelican">source code</a>)
91+
<p><a href="/pelican.html">Pelican</a>
9392
is a commonly used Python static website generator which is used to create
9493
<a href="https://github.com/mattmakai/fullstackpython.com">Full Stack Python</a>. The
9594
primary templating engine is Jinja and Markdown, reStructuredText and
9695
AsciiDoc are supported with the default configuration.</p>
9796
</li>
9897
<li>
99-
<p><a href="http://www.mkdocs.org/">MkDocs</a>
100-
(<a href="https://github.com/mkdocs/mkdocs/">source code</a>) uses a YAML configuration
98+
<p><a href="/lektor.html">Lektor</a> is a static content management system and site
99+
generator that can deploy its output to any webserver. It uses
100+
<a href="/jinja2.html">Jinja2</a> as its <a href="/template-engines.html">template engine</a>.</p>
101+
</li>
102+
<li>
103+
<p><a href="/mkdocs.html">MkDocs</a> uses a YAML configuration
101104
file to take Markdown files and an optional theme to output a documentation
102105
site. The templating engine is Jinja, but a user doesn't have to create her
103106
own templates unless a custom site is desired at which point it might make
@@ -136,12 +139,6 @@ <h2>Python implementations</h2>
136139
"experimental" phase.</p>
137140
</li>
138141
<li>
139-
<p><a href="https://www.getlektor.com/">Lektor</a>
140-
(<a href="https://github.com/lektor/lektor">source code</a>) is a Python static
141-
content management system that can deploy to any webserver. It uses
142-
<a href="/jinja2.html">Jinja2</a> as a <a href="/template-engines.html">template engine</a>.</p>
143-
</li>
144-
<li>
145142
<p><a href="http://complexity.readthedocs.org/en/latest/">Complexity</a>
146143
(<a href="https://github.com/audreyr/complexity">source code</a>) is a site generator
147144
for users who like to work in HTML. It uses HTML for templating but

0 commit comments

Comments
 (0)