filesystem interface (workflow)

screenshot of http://pzwart1.wdka.hro.nl/~manetta/i-could-have-written-that/

info

This is an interface that i use to collect material related to my research for 'i-could-have-written-that'. The interface uses the elements from the default filesystem on current computers:

the form of a list
its nested structure
foldernames, filenames
file-extensions
and a visual preview

By displaying the filenames as links, files could also be viewed individually. This all is an attempt to reveal the nature of the workflow into the interface.

This workflow enables me to work offline on my files (eg.: when traveling by train), i store my files as documents (as opposed to database entries), it is therefore easy to re-use them in other ways. Another big pro is to not be dependent on WordPress or similar software packages, which would cost me quite some 'deconstruction' time, before i can start building my imagined interface.

And, working with the documents in this way means that i need to built everything from scratch, which of course makes the system very basic, but therefore it is a way to learn about very basic elements of 'document processing design'.

upload workflow

filesystem (to order and collect material)
markdown files (to write documents)
pandoc (to convert markdown to HTML documents)
python (to 'walk' through filesystem and write the static index.html)
git (to upload to pzwart1, and git-hook to automatic 'pull' an update to the public_html folder)
makefile (to run these commands at once, by typing 'make')

notes

in a filesystem, documents are either files or folders