about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorCase Duckworth2015-03-18 11:41:43 -0700
committerCase Duckworth2015-03-18 11:41:43 -0700
commit544d6f5e304453897f5e28b9b92daf8259eeac84 (patch)
tree0af9a341c38253ec4f23e14f625f7da62a41e61a
parentAdd README.txt in src/ (diff)
downloadautocento-544d6f5e304453897f5e28b9b92daf8259eeac84.tar.gz
autocento-544d6f5e304453897f5e28b9b92daf8259eeac84.zip
Add README (for real this time) & update with TODOs
-rw-r--r--README.html99
-rw-r--r--river/README.river300
-rw-r--r--src/README.txt101
3 files changed, 500 insertions, 0 deletions
diff --git a/README.html b/README.html new file mode 100644 index 0000000..92abb22 --- /dev/null +++ b/README.html
@@ -0,0 +1,99 @@
1<!DOCTYPE html>
2<!-- AUTOCENTO OF THE BREAKFAST TABLE -->
3<!-- vim: fdm=indent
4-->
5<html lang="en">
6<head>
7 <meta charset="utf-8">
8 <meta name="generator" content="pandoc">
9 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
10 <meta name="author" content="Case Duckworth">
11
12 <title>Autocento of the breakfast table | Autocento of the breakfast table</title>
13 <link rel="icon" type="image/png" href="img/favico.png" />
14
15 <link rel="stylesheet" type="text/css" href="./css/common.css">
16 <script src="./js/lozenge.js" type="text/javascript"> </script>
17 <script src="./js/hylo.js" type="text/javascript"> </script>
18
19 <link rel="stylesheet" type="text/css" href="./css/prose.css">
20 <script src="./js/prose.js" type="text/javascript"> </script>
21 <link rel="stylesheet" type="text/css" href="./css/autocento.css">
22 <script src="./js/autocento.js" type="text/javascript"> </script>
23 <!--[if lt IE 9]>
24 <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"> </script>
25 <![endif]-->
26 <!-- <script src="js/external.js"> </script> -->
27 </head>
28<body>
29
30
31 <article id="container">
32 <header>
33 <!-- title -->
34 <h1 class="title">Autocento of the breakfast table</h1>
35 <h1 class="subtitle">about this site</h1>
36
37 <div class="header-extra">
38
39 <!-- epigraph -->
40 <div class="epigraph">
41 by Case Duckworth
42
43 </div>
44 </div>
45 </header>
46
47
48 <section class="content prose"><section id="introduction" class="level2">
49<h2>Introduction</h2>
50<p><em>Autocento <a href="http://www.ibiblio.org/eldritch/owh/abt.html">of the breakfast table</a></em> is a hypertextual exploration of the workings of revision across time. Somebody<sup>[citation needed]</sup> once said that every relationship we have is part of the same relationship; the same is true of authorship. As we write, as we continue writing across our lives, patterns thread themselves through our work: images, certain phrases, preoccupations. This project attempts to make those threads more apparent, using the technology of hypertext.</p>
51</section>
52<section id="process" class="level2">
53<h2>Process</h2>
54<p>In compiling the works that make up this text, I’ve pulled from a few different projects:</p>
55<ul>
56<li><a href="and.html">Elegies for alternate selves</a></li>
57<li><a href="prelude.html">The book of Hezekiah</a></li>
58<li><a href="table_contents.html">Stark raving</a></li>
59<li><a href="art.html">Buildings out of air</a></li>
60</ul>
61<p>as well as added new poems, written quite recently. As I’ve compiled them into this project, I’ve linked them together based on common images or language, moving back and forth through time. This should give the reader a fair idea of what my head looks like on the inside.</p>
62</section>
63<section id="technology" class="level2">
64<h2>Technology</h2>
65<p>Because this project lives online, I’ve used a fair amount of technology to get it there. First, I converted all the articles<a href="#fn1" class="footnoteRef" id="fnref1"><sup>1</sup></a> present into plain text files, which are viewable <a href="src/index.html">here</a>. Then, I used John McFarlane’s venerable document preparation system <a href="http://johnmacfarlane.net/pandoc/">pandoc</a>, along with a short <a href="https://github.com/duckwork/autocento/blob/gh-pages/compile.lua">script</a>, to compile the text sources to HTML using <a href="https://github.com/duckwork/autocento/blob/gh-pages/.template.html">this template</a>. The compiled HTML is what you’re reading now.<a href="#fn2" class="footnoteRef" id="fnref2"><sup>2</sup></a></p>
66<p>To host the project, I’m using <a href="https://github.com/">Github</a>, an online code-collaboration tool with the version control system <a href="http://www.git-scm.com/">git</a> under the hood. This enables me (and you, dear Reader!) to explore the path of revision even more, from beginning to end, based on my commits to the repository. You can view the repository and its changes and files at <a href="https://github.com/duckwork/autocento">my Github profile</a>.<a href="#fn3" class="footnoteRef" id="fnref3"><sup>3</sup></a></p>
67</section>
68<section id="using-this-site" class="level2">
69<h2>Using this site</h2>
70<p>All of the articles on this site are linked together hypertextually, that is, like a webpage. This means that all you need to do to explore the creative threads linking these articles together is to start clicking links. However, if you find you’re looping around to a lot of the same articles, you can head back to the <a href="index.html">index</a> and click through the titles in order—that poem contains the titles of all the other poems in this project.</p>
71<p>Alternatively, you can click the lozenge (◊) at the bottom of each page. It’ll take you to a random article in the project, thanks to <a href="https://github.com/duckwork/autocento/blob/gh-pages/js/lozenge.js">this javascript</a>.</p>
72<p>If you want to experience the earlier projects in something resembling the original orders, previous and next links are provided at the bottom of each page, next to the lozenge. Sometimes, there are more than one of each of these—they represent other work I’ve done with hypertextuality.</p>
73</section>
74<section id="contact-me" class="level2">
75<h2>Contact me</h2>
76<p>If you’d like to contact me about the state of this work or my writing in general, you can email me at <script type="text/javascript">
77<!--
78h='&#x61;&#x75;&#116;&#x6f;&#x63;&#x65;&#110;&#116;&#x6f;&#46;&#x6d;&#x65;';a='&#64;';n='&#x63;&#x61;&#x73;&#x65;';e=n+a+h;
79document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+e+'<\/'+'a'+'>');
80// -->
81</script><noscript>&#x63;&#x61;&#x73;&#x65;&#32;&#x61;&#116;&#32;&#x61;&#x75;&#116;&#x6f;&#x63;&#x65;&#110;&#116;&#x6f;&#32;&#100;&#x6f;&#116;&#32;&#x6d;&#x65;</noscript>.</p>
82<!-- links & footnotes -->
83</section>
84<section class="footnotes">
85<hr />
86<ol>
87<li id="fn1"><p>I’ve decided to use the word <em>article</em> instead of <em>poem</em>, because not all of the texts included are poems; and instead of <em>piece</em>, because <em>piece</em> is vague and, to my mind, pretentious. I’m aware that the true <a href="http://www.etymonline.com/index.php?search=article">etymology</a> of <em>article</em> does not reflect my use of it, namely “a little chunk of art”, a la the (personal folk) derivation of <em>icicle</em>, <em>treicle</em>, etc.<a href="#fnref1">↩</a></p></li>
88<li id="fn2"><p>The great thing about <code>pandoc</code> is that it can compile to, and convert between, about fifty formats or so. This means that if, in the future, I choose to convert this project to a printable form (for example PDF, ODT, or even DOCX), I’ll be able to with a fairly small amount of work.<a href="#fnref2">↩</a></p></li>
89<li id="fn3"><p>For more information on the technological aspect of this project, see the <a href="https://github.com/duckwork/autocento/blob/gh-pages/README.md">README.md</a> file at the root of the github repo.<a href="#fnref3">↩</a></p></li>
90</ol>
91</section></section>
92 </article>
93 <nav>
94 <a href="#" id="lozenge" title="Random page"> &loz; </a>
95 </nav>
96
97
98</body>
99</html>
diff --git a/river/README.river b/river/README.river new file mode 100644 index 0000000..af68ce4 --- /dev/null +++ b/river/README.river
@@ -0,0 +1,300 @@
1autocento
2of
3the
4breakfast
5table
6about
7this
8site
9introduction
10autocento
11of
12the
13breakfast
14table
15is
16a
17hypertextual
18exploration
19of
20the
21workings
22of
23revision
24across
25time
26somebody
27citation
28needed
29once
30said
31that
32every
33relationship
34we
35have
36is
37part
38of
39the
40same
41relationship
42the
43same
44is
45true
46of
47authorship
48as
49we
50write
51as
52we
53continue
54writing
55across
56our
57lives
58patterns
59thread
60themselves
61through
62our
63work
64images
65certain
66phrases
67preoccupations
68this
69project
70attempts
71to
72make
73those
74threads
75more
76apparent
77using
78the
79technology
80of
81hypertext
82process
83in
84compiling
85the
86works
87that
88make
89up
90this
91text
92i've
93pulled
94from
95a
96few
97different
98projects
99elegies
100for
101alternate
102selves
103the
104book
105of
106hezekiah
107stark
108raving
109buildings
110out
111of
112air
113as
114well
115as
116added
117new
118poems
119written
120quite
121recently
122as
123i've
124compiled
125them
126into
127this
128project
129i've
130linked
131them
132together
133based
134on
135common
136images
137or
138language
139moving
140back
141and
142forth
143through
144time
145this
146should
147give
148the
149reader
150a
151fair
152idea
153of
154what
155my
156head
157looks
158like
159on
160the
161inside
162technology
163because
164this
165project
166lives
167online
168i've
169used
170a
171fair
172amount
173of
174technology
175to
176get
177it
178there
179first
180i
181converted
182all
183the
184articlesi've
185decided
186to
187use
188the
189word
190article
191instead
192of
193poem
194because
195not
196all
197of
198the
199texts
200included
201are
202poems
203and
204instead
205of
206piece
207because
208piece
209is
210vague
211and
212to
213my
214mind
215pretentious
216i'm
217aware
218that
219the
220true
221etymology
222of
223article
224does
225not
226reflect
227my
228use
229of
230it
231namely
232a
233little
234chunk
235of
236art
237a
238la
239the
240personal
241folk
242derivation
243of
244icicle
245treicle
246etc
247present
248into
249plain
250text
251files
252which
253are
254viewable
255here
256then
257i
258used
259john
260mcfarlane's
261venerable
262document
263preparation
264system
265pandoc
266along
267with
268a
269short
270script
271to
272compile
273the
274text
275sources
276to
277html
278using
279this
280template
281the
282compiled
283html
284is
285what
286you're
287reading
288now
289the
290great
291thing
292about
293pandoc
294is
295that
296it
297can
298compile
299to
300and
diff --git a/src/README.txt b/src/README.txt new file mode 100644 index 0000000..f1da4a7 --- /dev/null +++ b/src/README.txt
@@ -0,0 +1,101 @@
1---
2title: Autocento of the breakfast table
3subtitle: about this site
4genre: prose
5
6epigraph:
7 content: by Case Duckworth
8
9project:
10 title: Autocento of the breakfast table
11 css: autocento
12...
13
14Introduction
15------------
16
17_Autocento [of the breakfast table][]_ is a hypertextual exploration of the workings of revision across time.
18Somebody^[citation needed]^ once said that every relationship we have is part of the same relationship; the same is true of authorship.
19As we write, as we continue writing across our lives, patterns thread themselves through our work: images, certain phrases, preoccupations.
20This project attempts to make those threads more apparent, using the technology of hypertext.
21
22I'm also an MFA candidate at [Northern Arizona University][NAU].
23This is my thesis.
24
25Process
26-------
27
28In compiling the works that make up this text, I've pulled from a few different projects:
29
30* [Elegies for alternate selves](and.html)
31* [The book of Hezekiah](prelude.html)
32* [Stark raving](table_contents.html)
33* [Buildings out of air](art.html)
34
35as well as added new poems, written quite recently.
36As I've compiled them into this project, I've linked them together based on common images or language, moving back and forth through time.
37This should give the reader a fair idea of what my head looks like on the inside.
38
39Technology
40----------
41
42Because this project lives online, I've used a fair amount of technology to get it there.
43First, I converted all the articles[^1] present into plain text files, which are viewable [here][text].
44Then, I used John McFarlane's venerable document preparation system [pandoc][], along with a short [script][compile.lua], to compile the text sources to HTML using [this template][].
45The compiled HTML is what you're reading now.[^2]
46
47To host the project, I'm using [Github][], an online code-collaboration tool with the version control system [git][] under the hood.
48This enables me (and you, dear Reader!) to explore the path of revision even more, from beginning to end, based on my commits to the repository.
49You can view the repository and its changes and files at [my Github profile][].[^3]
50
51Using this site
52---------------
53
54All of the articles on this site are linked together hypertextually, that is, like a webpage.
55This means that all you need to do to explore the creative threads linking these articles together is to start clicking links.
56However, if you find you're looping around to a lot of the same articles, you can head back to the [index][] and click through the titles in order---that poem contains the titles of all the other poems in this project.
57
58Alternatively, you can click the lozenge (&loz;) at the bottom of each page.
59It'll take you to a random article in the project, thanks to [this javascript][].
60
61If you want to experience the earlier projects in something resembling the original orders, previous and next links are provided at the bottom of each page, next to the lozenge.
62Sometimes, there are more than one of each of these---they represent other work I've done with hypertextuality.
63
64Things still to do
65------------------
66
67_Autocento of the breakfast table_ is a work in progress.
68The first draft is completed, but some revision and aesthetic work remains to be done for me to consider it fully "[published][]"
69(what does this word mean in 2015?).
70You can see the full list of to-dos by visiting the [issues page][issues] of the Github site.
71
72Contact me
73----------
74
75If you'd like to contact me about the state of this work or my writing in general, you can email me at <case@autocento.me>.
76
77<!-- links & footnotes -->
78[of the breakfast table]: http://www.ibiblio.org/eldritch/owh/abt.html
79
80[text]: src/index.html
81
82[pandoc]: http://johnmacfarlane.net/pandoc/
83[compile.lua]: https://github.com/duckwork/autocento/blob/gh-pages/compile.lua
84[this template]: https://github.com/duckwork/autocento/blob/gh-pages/.template.html
85[Github]: https://github.com/
86[git]: http://www.git-scm.com/
87[my Github profile]: https://github.com/duckwork/autocento
88
89[index]: index.html
90[this javascript]: https://github.com/duckwork/autocento/blob/gh-pages/js/lozenge.js
91
92[published]: published.html
93[issues]: https://github.com/duckwork/autocento/issues
94
95[^1]: I've decided to use the word _article_ instead of _poem_, because not all of the texts included are poems; and instead of _piece_, because _piece_ is vague and, to my mind, pretentious.
96 I'm aware that the true [etymology](http://www.etymonline.com/index.php?search=article) of _article_ does not reflect my use of it, namely "a little chunk of art", a la the (personal folk) derivation of _icicle_, _treicle_, etc.
97
98[^2]: The great thing about `pandoc` is that it can compile to, and convert between, about fifty formats or so.
99 This means that if, in the future, I choose to convert this project to a printable form (for example PDF, ODT, or even DOCX), I'll be able to with a fairly small amount of work.
100
101[^3]: For more information on the technological aspect of this project, see the [README.md](https://github.com/duckwork/autocento/blob/gh-pages/README.md) file at the root of the github repo.