diff options
Diffstat (limited to 'about.html')
-rw-r--r-- | about.html | 44 |
1 files changed, 33 insertions, 11 deletions
diff --git a/about.html b/about.html index 872cba5..e7c2100 100644 --- a/about.html +++ b/about.html | |||
@@ -82,25 +82,47 @@ | |||
82 | <p>Because this project lives online (welcome to the Internet!), I’ve used a fair amount of technology to get it there.</p> | 82 | <p>Because this project lives online (welcome to the Internet!), I’ve used a fair amount of technology to get it there.</p> |
83 | <p>First, I typed all of the objects present into a human-readable markup format called <a href="http://daringfireball.net/projects/markdown/">Markdown</a> by John Gruber, using a plain-text editor called <a href="http://www.vim.org">Vim</a>.<a href="#fn5" class="footnoteRef" id="fnref5"><sup>5</sup></a> Markdown is a plain-text format that uses unobtrusive mark-up to signal semantic meaning around a text. A text written with markup can then be passed to a compiler, such as John Gruber’s <code>Markdown.pl</code> script, to turn it into functioning HTML for viewing in a browser.</p> | 83 | <p>First, I typed all of the objects present into a human-readable markup format called <a href="http://daringfireball.net/projects/markdown/">Markdown</a> by John Gruber, using a plain-text editor called <a href="http://www.vim.org">Vim</a>.<a href="#fn5" class="footnoteRef" id="fnref5"><sup>5</sup></a> Markdown is a plain-text format that uses unobtrusive mark-up to signal semantic meaning around a text. A text written with markup can then be passed to a compiler, such as John Gruber’s <code>Markdown.pl</code> script, to turn it into functioning HTML for viewing in a browser.</p> |
84 | <p>As an example, here’s the previous paragraph as I typed it:</p> | 84 | <p>As an example, here’s the previous paragraph as I typed it:</p> |
85 | <pre class="sourceCode markdown"><code class="sourceCode markdown">First, I typed all of the objects present into a human-readable markup | 85 | <pre class="sourceCode markdown"><code class="sourceCode markdown">First, I typed all of the objects present into a |
86 | format called <span class="ot">[Markdown][] </span>by John Gruber, using a plain-text editor called | 86 | human-readable markup format called <span class="ot">[Markdown][]</span> |
87 | <span class="ot">[Vim][]</span>.<span class="ot">[^5]</span> Markdown is a plain-text format that uses unobtrusive mark-up to | 87 | by John Gruber, using a plain-text editor called |
88 | signal semantic meaning around a text. A text written with markup can then be | 88 | <span class="ot">[Vim][]</span>.<span class="ot">[^5]</span> Markdown is a plain-text format |
89 | passed to a compiler, such as John Gruber's original Markdown.pl script, to | 89 | that uses unobtrusive mark-up to signal semantic |
90 | turn it into functioning HTML for viewing in a browser. | 90 | meaning around a text. A text written with |
91 | markup can then be passed to a compiler, such as | ||
92 | John Gruber's original Markdown.pl script, to | ||
93 | turn it into functioning HTML for viewing in a | ||
94 | browser. | ||
91 | 95 | ||
92 | <span class="ot">[Markdown]: http://daringfireball.net/projects/markdown/</span> | 96 | <span class="ot">[Markdown]: http://daringfireball.net/projects/markdown/</span> |
93 | <span class="ot">[Vim]: http://www.vim.org</span> | 97 | <span class="ot">[Vim]: http://www.vim.org</span> |
94 | 98 | ||
95 | <span class="ot">[^5]</span>: I could've used any text editor for the composition step, including | 99 | <span class="ot">[^5]</span>: I could've used any text editor for the |
96 | <span class="bn"> Notepad, but I personally like Vim for its extensibility, composability,</span> | 100 | <span class="bn"> composition step, including Notepad, but I</span> |
97 | <span class="bn"> and honestly its colorschemes.</span></code></pre> | 101 | <span class="bn"> personally like Vim for its extensibility,</span> |
102 | <span class="bn"> composability, and honestly its colorschemes.</span></code></pre> | ||
98 | <p>And here it is as a compiled HTML file:</p> | 103 | <p>And here it is as a compiled HTML file:</p> |
99 | <pre class="sourceCode html"><code class="sourceCode html"><span class="kw"><p></span>First, I typed all of the objects present into a human-readable markup format called <span class="kw"><a</span><span class="ot"> href=</span><span class="st">"http://daringfireball.net/projects/markdown/"</span><span class="kw">></span>Markdown<span class="kw"></a></span> by John Gruber, using a plain-text editor called <span class="kw"><a</span><span class="ot"> href=</span><span class="st">"http://www.vim.org"</span><span class="kw">></span>Vim<span class="kw"></a></span>.<span class="kw"><a</span><span class="ot"> href=</span><span class="st">"#fn1"</span><span class="ot"> class=</span><span class="st">"footnoteRef"</span><span class="ot"> id=</span><span class="st">"fnref1"</span><span class="kw">><sup></span>1<span class="kw"></sup></a></span> Markdown is a plain-text format that uses unobtrusive mark-up to signal semantic meaning around a text. A text written with markup can then be passed to a compiler, such as John Gruber's original Markdown.pl script, to turn it into functioning HTML for viewing in a browser.<span class="kw"></p></span> | 104 | <pre class="sourceCode html"><code class="sourceCode html"><span class="kw"><p></span> |
105 | First, I typed all of the objects present into a human-readable markup | ||
106 | format called <span class="kw"><a</span><span class="ot"> href=</span><span class="st">"http://daringfireball.net/projects/markdown/"</span><span class="kw">></span> | ||
107 | Markdown<span class="kw"></a></span> by John Gruber, using a plain-text editor called | ||
108 | <span class="kw"><a</span><span class="ot"> href=</span><span class="st">"http://www.vim.org"</span><span class="kw">></span>Vim<span class="kw"></a></span>.<span class="kw"><a</span><span class="ot"> href=</span><span class="st">"#fn1"</span><span class="ot"> class=</span><span class="st">"footnoteRef"</span> | ||
109 | <span class="ot"> id=</span><span class="st">"fnref1"</span><span class="kw">><sup></span>1<span class="kw"></sup></a></span> Markdown is a plain-text format that uses | ||
110 | unobtrusive mark-up to signal semantic meaning around a text. A text | ||
111 | written with markup can then be passed to a compiler, such as John Gruber's | ||
112 | original Markdown.pl script, to turn it into functioning HTML for viewing | ||
113 | in a browser. | ||
114 | <span class="kw"></p></span> | ||
100 | <span class="kw"><section</span><span class="ot"> class=</span><span class="st">"footnotes"</span><span class="kw">></span> | 115 | <span class="kw"><section</span><span class="ot"> class=</span><span class="st">"footnotes"</span><span class="kw">></span> |
101 | <span class="kw"><hr</span> <span class="kw">/></span> | 116 | <span class="kw"><hr</span> <span class="kw">/></span> |
102 | <span class="kw"><ol></span> | 117 | <span class="kw"><ol></span> |
103 | <span class="kw"><li</span><span class="ot"> id=</span><span class="st">"fn1"</span><span class="kw">><p></span>I could've used any text editor for the composition step, including Notepad, but I personally like Vim for its extensibility, composability, and honestly its colorschemes.<span class="kw"><a</span><span class="ot"> href=</span><span class="st">"#fnref1"</span><span class="kw">></span>↩<span class="kw"></a></p></li></span> | 118 | <span class="kw"><li</span><span class="ot"> id=</span><span class="st">"fn1"</span><span class="kw">></span> |
119 | <span class="kw"><p></span> | ||
120 | I could've used any text editor for the composition step, including | ||
121 | Notepad, but I personally like Vim for its extensibility, | ||
122 | composability, and honestly its colorschemes. | ||
123 | <span class="kw"><a</span><span class="ot"> href=</span><span class="st">"#fnref1"</span><span class="kw">></span>↩<span class="kw"></a></span> | ||
124 | <span class="kw"></p></span> | ||
125 | <span class="kw"></li></span> | ||
104 | <span class="kw"></ol></span> | 126 | <span class="kw"></ol></span> |
105 | <span class="kw"></section></span></code></pre> | 127 | <span class="kw"></section></span></code></pre> |
106 | <p>For these files, I opted to use John McFarlane’s <a href="http://johnmcfarlane.net/pandoc/">pandoc</a> over the original <code>Markdown.pl</code> compiler, because it’s more consistent with edge cases in formatting, and because it can compile the Markdown source into a wide variety of different formats, including DOCX, ODT, PDF, HTML, and others. I use an <a href="https://github.com/duckwork/autocento/blob/gh-pages/template.html">HTML template</a> for <code>pandoc</code> to correctly typeset each object in the web browser. The compiled HTML pages are what you’re reading now.</p> | 128 | <p>For these files, I opted to use John McFarlane’s <a href="http://johnmcfarlane.net/pandoc/">pandoc</a> over the original <code>Markdown.pl</code> compiler, because it’s more consistent with edge cases in formatting, and because it can compile the Markdown source into a wide variety of different formats, including DOCX, ODT, PDF, HTML, and others. I use an <a href="https://github.com/duckwork/autocento/blob/gh-pages/template.html">HTML template</a> for <code>pandoc</code> to correctly typeset each object in the web browser. The compiled HTML pages are what you’re reading now.</p> |