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 @@
+<!DOCTYPE html>
+<!-- AUTOCENTO OF THE BREAKFAST TABLE -->
+<!-- vim: fdm=indent
+-->
+<html lang="en">
+<head>
+    <meta charset="utf-8">
+    <meta name="generator" content="pandoc">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
+    <meta name="author" content="Case Duckworth">
+    <title>Autocento of the breakfast table | Autocento of the breakfast table</title>
+    <link rel="icon" type="image/png" href="img/favico.png" />
+    <link rel="stylesheet" type="text/css" href="./css/common.css">
+    <script src="./js/lozenge.js" type="text/javascript"> </script>
+    <script src="./js/hylo.js" type="text/javascript"> </script>
+        <link rel="stylesheet" type="text/css" href="./css/prose.css">
+    <script src="./js/prose.js" type="text/javascript"> </script>
+            <link rel="stylesheet" type="text/css" href="./css/autocento.css">
+    <script src="./js/autocento.js" type="text/javascript"> </script>
+        <!--[if lt IE 9]>
+    <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"> </script>
+    <![endif]-->
+    <!-- <script src="js/external.js"> </script> -->
+    </head>
+<body>
+    
+    <article id="container">
+        <header>
+            <!-- title -->
+            <h1 class="title">Autocento of the breakfast table</h1>
+            <h1 class="subtitle">about this site</h1>
+            <div class="header-extra">
+                
+                                    <!-- epigraph -->
+                    <div class="epigraph">
+                                            by Case Duckworth
+                    
+                                        </div>
+                            </div>
+        </header>
+        
+        <section class="content prose"><section id="introduction" class="level2">
+<h2>Introduction</h2>
+<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>
+</section>
+<section id="process" class="level2">
+<h2>Process</h2>
+<p>In compiling the works that make up this text, I’ve pulled from a few different projects:</p>
+<ul>
+<li><a href="and.html">Elegies for alternate selves</a></li>
+<li><a href="prelude.html">The book of Hezekiah</a></li>
+<li><a href="table_contents.html">Stark raving</a></li>
+<li><a href="art.html">Buildings out of air</a></li>
+</ul>
+<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>
+</section>
+<section id="technology" class="level2">
+<h2>Technology</h2>
+<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>
+<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>
+</section>
+<section id="using-this-site" class="level2">
+<h2>Using this site</h2>
+<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>
+<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>
+<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>
+</section>
+<section id="contact-me" class="level2">
+<h2>Contact me</h2>
+<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">
+<!--
+h='&#x61;&#x75;&#116;&#x6f;&#x63;&#x65;&#110;&#116;&#x6f;&#46;&#x6d;&#x65;';a='&#64;';n='&#x63;&#x61;&#x73;&#x65;';e=n+a+h;
+document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+e+'<\/'+'a'+'>');
+// -->
+</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>
+<!-- links & footnotes -->
+</section>
+<section class="footnotes">
+<hr />
+<ol>
+<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>
+<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>
+<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>
+</ol>
+</section></section>
+    </article>
+    <nav>
+                <a href="#" id="lozenge" title="Random page"> &loz; </a>
+            </nav>
+    
+</body>
+</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 @@
+autocento
+of
+the
+breakfast
+table
+about
+this
+site
+introduction
+autocento
+of
+the
+breakfast
+table
+is
+a
+hypertextual
+exploration
+of
+the
+workings
+of
+revision
+across
+time
+somebody
+citation
+needed
+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
+process
+in
+compiling
+the
+works
+that
+make
+up
+this
+text
+i've
+pulled
+from
+a
+few
+different
+projects
+elegies
+for
+alternate
+selves
+the
+book
+of
+hezekiah
+stark
+raving
+buildings
+out
+of
+air
+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
+technology
+because
+this
+project
+lives
+online
+i've
+used
+a
+fair
+amount
+of
+technology
+to
+get
+it
+there
+first
+i
+converted
+all
+the
+articlesi'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
+i'm
+aware
+that
+the
+true
+etymology
+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
+present
+into
+plain
+text
+files
+which
+are
+viewable
+here
+then
+i
+used
+john
+mcfarlane's
+venerable
+document
+preparation
+system
+pandoc
+along
+with
+a
+short
+script
+to
+compile
+the
+text
+sources
+to
+html
+using
+this
+template
+the
+compiled
+html
+is
+what
+you're
+reading
+now
+the
+great
+thing
+about
+pandoc
+is
+that
+it
+can
+compile
+to
+and
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 @@
+---
+title: Autocento of the breakfast table
+subtitle: about this site
+genre: prose
+epigraph:
+    content: by Case Duckworth
+project:
+    title: Autocento of the breakfast table
+    css: autocento
+...
+Introduction
+------------
+_Autocento [of the breakfast table][]_ is a hypertextual exploration of the workings of revision across time.
+Somebody^[citation needed]^ 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.
+I'm also an MFA candidate at [Northern Arizona University][NAU].
+This is my thesis.
+Process
+-------
+In compiling the works that make up this text, I've pulled from a few different projects:
+* [Elegies for alternate selves](and.html)
+* [The book of Hezekiah](prelude.html)
+* [Stark raving](table_contents.html)
+* [Buildings out of air](art.html)
+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.
+Technology
+----------
+Because this project lives online, I've used a fair amount of technology to get it there.
+First, I converted all the articles[^1] present into plain text files, which are viewable [here][text].
+Then, 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][].
+The compiled HTML is what you're reading now.[^2]
+To host the project, I'm using [Github][], an online code-collaboration tool with the version control system [git][] 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 [my Github profile][].[^3]
+Using this site
+---------------
+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 [index][] and click through the titles in order---that poem contains the titles of all the other poems in this project.
+Alternatively, you can click the lozenge (&loz;) at the bottom of each page.
+It'll take you to a random article in the project, thanks to [this javascript][].
+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.
+Things still to do
+------------------
+_Autocento of the breakfast table_ is a work in progress.
+The first draft is completed, but some revision and aesthetic work remains to be done for me to consider it fully "[published][]"
+(what does this word mean in 2015?).
+You can see the full list of to-dos by visiting the [issues page][issues] of the Github site.
+Contact me
+----------
+If 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>.
+<!-- links & footnotes -->
+[of the breakfast table]: http://www.ibiblio.org/eldritch/owh/abt.html
+[text]: src/index.html
+[pandoc]: http://johnmacfarlane.net/pandoc/
+[compile.lua]: https://github.com/duckwork/autocento/blob/gh-pages/compile.lua
+[this template]: https://github.com/duckwork/autocento/blob/gh-pages/.template.html
+[Github]: https://github.com/
+[git]: http://www.git-scm.com/
+[my Github profile]: https://github.com/duckwork/autocento
+[index]: index.html
+[this javascript]: https://github.com/duckwork/autocento/blob/gh-pages/js/lozenge.js
+[published]: published.html
+[issues]: https://github.com/duckwork/autocento/issues
+[^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.
+    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.
+[^2]: The great thing about `pandoc` 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.
+[^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.

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	<!--
	78	h='autocento.me';a='@';n='case';e=n+a+h;
	79	document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+e+'<\/'+'a'+'>');
	80	// -->
	81	</script><noscript>case at autocento dot me</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 @@
	1	autocento
	2	of
	3	the
	4	breakfast
	5	table
	6	about
	7	this
	8	site
	9	introduction
	10	autocento
	11	of
	12	the
	13	breakfast
	14	table
	15	is
	16	a
	17	hypertextual
	18	exploration
	19	of
	20	the
	21	workings
	22	of
	23	revision
	24	across
	25	time
	26	somebody
	27	citation
	28	needed
	29	once
	30	said
	31	that
	32	every
	33	relationship
	34	we
	35	have
	36	is
	37	part
	38	of
	39	the
	40	same
	41	relationship
	42	the
	43	same
	44	is
	45	true
	46	of
	47	authorship
	48	as
	49	we
	50	write
	51	as
	52	we
	53	continue
	54	writing
	55	across
	56	our
	57	lives
	58	patterns
	59	thread
	60	themselves
	61	through
	62	our
	63	work
	64	images
	65	certain
	66	phrases
	67	preoccupations
	68	this
	69	project
	70	attempts
	71	to
	72	make
	73	those
	74	threads
	75	more
	76	apparent
	77	using
	78	the
	79	technology
	80	of
	81	hypertext
	82	process
	83	in
	84	compiling
	85	the
	86	works
	87	that
	88	make
	89	up
	90	this
	91	text
	92	i've
	93	pulled
	94	from
	95	a
	96	few
	97	different
	98	projects
	99	elegies
	100	for
	101	alternate
	102	selves
	103	the
	104	book
	105	of
	106	hezekiah
	107	stark
	108	raving
	109	buildings
	110	out
	111	of
	112	air
	113	as
	114	well
	115	as
	116	added
	117	new
	118	poems
	119	written
	120	quite
	121	recently
	122	as
	123	i've
	124	compiled
	125	them
	126	into
	127	this
	128	project
	129	i've
	130	linked
	131	them
	132	together
	133	based
	134	on
	135	common
	136	images
	137	or
	138	language
	139	moving
	140	back
	141	and
	142	forth
	143	through
	144	time
	145	this
	146	should
	147	give
	148	the
	149	reader
	150	a
	151	fair
	152	idea
	153	of
	154	what
	155	my
	156	head
	157	looks
	158	like
	159	on
	160	the
	161	inside
	162	technology
	163	because
	164	this
	165	project
	166	lives
	167	online
	168	i've
	169	used
	170	a
	171	fair
	172	amount
	173	of
	174	technology
	175	to
	176	get
	177	it
	178	there
	179	first
	180	i
	181	converted
	182	all
	183	the
	184	articlesi've
	185	decided
	186	to
	187	use
	188	the
	189	word
	190	article
	191	instead
	192	of
	193	poem
	194	because
	195	not
	196	all
	197	of
	198	the
	199	texts
	200	included
	201	are
	202	poems
	203	and
	204	instead
	205	of
	206	piece
	207	because
	208	piece
	209	is
	210	vague
	211	and
	212	to
	213	my
	214	mind
	215	pretentious
	216	i'm
	217	aware
	218	that
	219	the
	220	true
	221	etymology
	222	of
	223	article
	224	does
	225	not
	226	reflect
	227	my
	228	use
	229	of
	230	it
	231	namely
	232	a
	233	little
	234	chunk
	235	of
	236	art
	237	a
	238	la
	239	the
	240	personal
	241	folk
	242	derivation
	243	of
	244	icicle
	245	treicle
	246	etc
	247	present
	248	into
	249	plain
	250	text
	251	files
	252	which
	253	are
	254	viewable
	255	here
	256	then
	257	i
	258	used
	259	john
	260	mcfarlane's
	261	venerable
	262	document
	263	preparation
	264	system
	265	pandoc
	266	along
	267	with
	268	a
	269	short
	270	script
	271	to
	272	compile
	273	the
	274	text
	275	sources
	276	to
	277	html
	278	using
	279	this
	280	template
	281	the
	282	compiled
	283	html
	284	is
	285	what
	286	you're
	287	reading
	288	now
	289	the
	290	great
	291	thing
	292	about
	293	pandoc
	294	is
	295	that
	296	it
	297	can
	298	compile
	299	to
	300	and


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	---
	2	title: Autocento of the breakfast table
	3	subtitle: about this site
	4	genre: prose
	5
	6	epigraph:
	7	content: by Case Duckworth
	8
	9	project:
	10	title: Autocento of the breakfast table
	11	css: autocento
	12	...
	13
	14	Introduction
	15	------------
	16
	17	_Autocento [of the breakfast table][]_ is a hypertextual exploration of the workings of revision across time.
	18	Somebody^[citation needed]^ once said that every relationship we have is part of the same relationship; the same is true of authorship.
	19	As we write, as we continue writing across our lives, patterns thread themselves through our work: images, certain phrases, preoccupations.
	20	This project attempts to make those threads more apparent, using the technology of hypertext.
	21
	22	I'm also an MFA candidate at [Northern Arizona University][NAU].
	23	This is my thesis.
	24
	25	Process
	26	-------
	27
	28	In 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
	35	as well as added new poems, written quite recently.
	36	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.
	37	This should give the reader a fair idea of what my head looks like on the inside.
	38
	39	Technology
	40	----------
	41
	42	Because this project lives online, I've used a fair amount of technology to get it there.
	43	First, I converted all the articles[^1] present into plain text files, which are viewable [here][text].
	44	Then, 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][].
	45	The compiled HTML is what you're reading now.[^2]
	46
	47	To host the project, I'm using [Github][], an online code-collaboration tool with the version control system [git][] under the hood.
	48	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.
	49	You can view the repository and its changes and files at [my Github profile][].[^3]
	50
	51	Using this site
	52	---------------
	53
	54	All of the articles on this site are linked together hypertextually, that is, like a webpage.
	55	This means that all you need to do to explore the creative threads linking these articles together is to start clicking links.
	56	However, 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
	58	Alternatively, you can click the lozenge (&loz;) at the bottom of each page.
	59	It'll take you to a random article in the project, thanks to [this javascript][].
	60
	61	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.
	62	Sometimes, there are more than one of each of these---they represent other work I've done with hypertextuality.
	63
	64	Things still to do
	65	------------------
	66
	67	_Autocento of the breakfast table_ is a work in progress.
	68	The 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?).
	70	You can see the full list of to-dos by visiting the [issues page][issues] of the Github site.
	71
	72	Contact me
	73	----------
	74
	75	If 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.