summary refs log tree commit diff stats
path: root/process.html
diff options
context:
space:
mode:
authorCase Duckworth2015-03-28 10:50:24 -0700
committerCase Duckworth2015-03-28 10:50:24 -0700
commit417eddb940ec0b364a11d459e27d5ae05d2c7d11 (patch)
tree291dd47551917c6cc1e5ec819b5d76312ee89f80 /process.html
parentAdd backlinks pages (fixes #16). (diff)
downloadautocento-417eddb940ec0b364a11d459e27d5ae05d2c7d11.tar.gz
autocento-417eddb940ec0b364a11d459e27d5ae05d2c7d11.zip
Add Abstract and Process Narrative
Diffstat (limited to 'process.html')
-rw-r--r--process.html69
1 files changed, 45 insertions, 24 deletions
diff --git a/process.html b/process.html index 67f8046..2246863 100644 --- a/process.html +++ b/process.html
@@ -21,7 +21,7 @@
21 <![endif]--> 21 <![endif]-->
22 </head> 22 </head>
23<body id="process" class="meta"> 23<body id="process" class="meta">
24 24
25 25
26 <article class="container"> 26 <article class="container">
27 <header> 27 <header>
@@ -30,38 +30,60 @@
30 <h1 class="subtitle">process narrative</h1> 30 <h1 class="subtitle">process narrative</h1>
31 31
32 <div class="header-extra"> 32 <div class="header-extra">
33 33
34 </div> 34 </div>
35 </header> 35 </header>
36 36
37 37
38 <section class="content prose"> 38 <section class="content prose">
39 <section id="outline" class="level2"> 39 <section id="hi.-my-name-is-case-duckworth.-this-is-my-thesis." class="level2">
40 <h2>Outline</h2> 40 <h2>Hi. My name is Case Duckworth. This is my thesis.</h2>
41 <ul> 41 <p><em>Autocento of the breakfast table</em> is an inter/hypertextual exploration of the workings of inspiration, revision, and obsession. I’ve compiled this work over multiple years, and recently linked it all together to form a (hopefully) more cohesive whole. To make this easier than collating everything by hand, I’ve relied on a process that leverages open-source technologies to publish my work onto a web platform.</p>
42 <li>Hi. My name is Case Duckworth. This is my thesis.</li>
43 </ul>
44 </section> 42 </section>
45 <section id="process-steps" class="level2"> 43 <section id="process-steps" class="level2">
46 <h2>Process steps</h2> 44 <h2>Process steps</h2>
47 <ol type="1"> 45 <ol type="1">
48 <li>Write poems.</li> 46 <li>Write poems.</li>
49 <li>Convert to Markdown – generally easy.</li> 47 <li>Convert to Markdown.
50 <li>Compile to HTML with Pandoc.</li> 48 <ul>
51 <li>Style the pages with CSS.</li> 49 <li>Markdown, originally by <a href="http://daringfireball.net/projects/markdown/">John Gruber</a>, is a lightweight markup language that allows me to focus on the <em>content</em> of my writing, knowing that I can work on the <em>presentation</em> later.</li>
52 <li>Use Github to put them online. 50 <li>The original <code>markdown.pl</code> program is buggy and inconsistent with how it applies styles to markup. It also only works to convert text to HTML.</li>
51 <li>Because of these limitations, I’ve used John MacFarlane’s <a href="http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown">extended Markdown syntax</a>, which lets me write richer documents and programmatically compile my work into multiple formats.</li>
52 </ul></li>
53 <li>Compile to HTML with Pandoc.
53 <ul> 54 <ul>
54 <li><code>git</code> has been used throughout to keep track of changes.</li> 55 <li><p>At first, I used this code in the shell to generate my HTML:</p>
55 <li>It’s a Version Control System – usually used for code but adapted for creative writing.</li> 56 <pre class="sourceCode bash"><code class="sourceCode bash"><span class="kw">for</span> <span class="kw">file</span> in *.txt<span class="kw">;</span> <span class="kw">do</span>
57 <span class="kw">pandoc</span> <span class="st">&quot;</span><span class="ot">$file</span><span class="st">&quot;</span> -f markdown -t html5 \
58 --template=template.html -o <span class="st">&quot;</span><span class="ot">${file%</span>txt<span class="ot">}</span><span class="st">html&quot;</span>
59<span class="kw">done</span></code></pre>
60 but this proved tedious with time.</li>
61 <li>After a lot of experimenting with different scripting languages, I finally realized that <a href="https://www.gnu.org/software/make/manual/make.html"><code>GNU make</code></a> would fit this task perfectly.</li>
62 <li>You can see my makefile <a href="https://github.com/duckwork/autocento/blob/gh-pages/makefile">here</a>—it’s kind of a mess, but it does the job. See below for a more detailed explanation of the makefile.</li>
56 </ul></li> 63 </ul></li>
57 <li>Write Makefile for ease-of-compilation. 64 <li>Style the pages with CSS.
58 <ul> 65 <ul>
59 <li>A <code>makefile</code> is a collection of instructions to <code>make</code> that tells it how to compile a set of files.</li> 66 <li>I use a pretty basic style for <em>Autocento</em>. You can see my stylesheet <a href="https://github.com/duckwork/autocento/blob/gh-pages/style.css">here</a>.</li>
60 <li>It’s made the other parts of this much easier.</li> 67 </ul></li>
68 <li>Use <a href="https://github.com">Github</a> to put them online.
69 <ul>
70 <li>Github uses <code>git</code> under the hood—a Version Control System developed for keeping track of large code projects.</li>
71 <li>My workflow with <code>git</code> looks like this:
72 <ul>
73 <li>Change files in the project directory—revise a poem, change the makefile, add a style, etc.</li>
74 <li>(If necessary, re-compile with <code>make</code>.)</li>
75 <li><code>git status</code> tells me which files have changed, which have been added, and if any have been deleted.</li>
76 <li><code>git add -A</code> adds all the changes to the <em>staging area</em>, or I can add individual files, depending on what I want to commit.</li>
77 <li><code>git commit -m &quot;[message]&quot;</code> commits the changes to git. This means they’re “saved”—if I do something I want to revert, I can <code>git revert</code> back to a commit and start again.</li>
78 <li><code>git push</code> pushes the changes to the <em>remote repository</em>—in this case, the Github repo that serves <a href="http://autocento.me" class="uri">http://autocento.me</a>.</li>
79 <li>Lather, rinse, repeat.</li>
80 </ul></li>
81 </ul></li>
82 <li>Write Makefile to extend build capabilities.
83 <ul>
84 <li>As of now, I’ve completed a <em><a href="hapax.html">Hapax legomenon</a></em> compiler, a <a href="makefile">back-link</a> compiler, and an updater for the <a href="trunk/lozenge.js">random link functionality</a> that’s on this site.</li>
85 <li>I’d like to build a compiler for the <a href="first-lines.html">Index of first lines</a> and <a href="common-titles.html">Index of common titles</a> once I have time.</li>
61 </ul></li> 86 </ul></li>
62 <li>Write <em>Hapax legomenon</em> compiler.</li>
63 <li>Write compiler for backlinks.</li>
64 <li>(TODO) write compiler for Index of first lines and common titles.</li>
65 </ol> 87 </ol>
66 </section> 88 </section>
67 <section id="the-beauty-of-this-system" class="level2"> 89 <section id="the-beauty-of-this-system" class="level2">
@@ -69,14 +91,13 @@
69 <ul> 91 <ul>
70 <li>I can compile these poems into (almost) any format: <code>pandoc</code> supports a lot.</li> 92 <li>I can compile these poems into (almost) any format: <code>pandoc</code> supports a lot.</li>
71 <li>Once I complete the above process once, I can focus on revising my poems.</li> 93 <li>Once I complete the above process once, I can focus on revising my poems.</li>
72 <li>These poems are online for anyone to see and work off of.</li> 94 <li>These poems are online for anyone to see and use for their own work.</li>
73 <li>Something something intertextuality.</li>
74 </ul> 95 </ul>
75 </section> 96 </section>
76 </section> 97 </section>
77 </article> 98 </article>
78 <nav> 99 <nav>
79 100
80 <!-- ANCHORS --> 101 <!-- ANCHORS -->
81 <div class="anchors"> 102 <div class="anchors">
82 <a href="process_backlinks.htm" id="back-link" title="Links to this page"> 103 <a href="process_backlinks.htm" id="back-link" title="Links to this page">
@@ -88,6 +109,6 @@
88 109
89 </nav> 110 </nav>
90 111
91 112
92</body> 113</body>
93</html> 114</html>