← mturro/poem

commit 4577f82

$ git show 4577f82

Update README.md

2013-10-11

README.md

@@ -1,5 +1,5 @@
# Poem(s) in progress...
This repository holds work-in-progress poems written in the markdown syntax. It started as an attempt to expose my creative process (to myself and to anyone who may care to watch) and track the nature and number of edits any given version of a poem might go through. I decided to use git (as opposed to some other tool like mediawiki) simply because it makes sense to me and it's a tool I use on a daily basis. I also found it affords a level of textual simplicty that more bloated CMS style tools lose in their effort to be complete publishing tools. In the process of thinking through the implications of using a code management toolchain to write poetry I became quite interested in exploring how true the old Wordpress tag "Code is Poetry" is and whether it runs in the inverse (ie "Poetry is Code").
This repository holds work-in-progress poems written in the markdown syntax. It started as an attempt to expose my creative process (to myself and to anyone who may care to watch) and track the nature and number of edits any given version of a poem might go through. I decided to use git (as opposed to some other tool like mediawiki) simply because it makes sense to me and it's a tool I use on a daily basis. I also found it affords a level of textual simplicty that more bloated CMS style tools lose in their effort to be complete publishing tools.
# And then this happened.
At some point in the very early onset of this experiment the thought occurred to me that perhaps I wasn't envisioning a collection of poems, but rather had stumbled on to a framework for my own exploration of a technically focused twenty-first century epic poem. And then later on I realized that what I was in fact writing was a number of individual poems - something closer to the original intention of the repo. Whether or not this is a poem or a series of poems what seems clear to me at this point is that this is a definite attempt at coming up with a compositional technique that has something of the transparency of open source software. In other words, what is being explored here is not so much the poetic effect of language, but rather the poetic effect of process and technology.