I used the filesystem information to build a hierarchical list of files in OmniOutliner3 that I could use to complete the “content matrix” Beth gave us as homework.

This format is nice because I can leave virtually all the detail (25,000 files) “folded” away in the outline. But certain example directories I can expand and document in closer detail. The original OmniOutliner document (.oo3) and the OPML exported version have that full data embedded in them.

• OmniOutliner3 format
• OPML exchange format

However, this format is problematic in that almost nobody has OmniOutliner. Even the OPML exchange format (a flavor of XML) is not commonly found outside other outliners. So I’ve created Excel, comma separated value, fixed width text, RTF, and HTML versions of the “folded” document. These can’t be expanded to detail files I didn’t specifically address in the matrix, but they are much more commonly readable.

• Excel version
• comma separated values
• fixed-width text
• rich text format
• HTML

In addition, I found I could not properly respond to the content matrix questions without assuming some new navigation for the website. The old nav is nearly non-existent and feels broken to most users, including myself. This new structure for the site enabled me to respond to the content matrix questions, but it has not be reviewed by DLF staff and should not be considered correct or comprehensive. In fact, I was not even planning to share it, but as I worked through the matrix I could not really imagine making one available without the other. So I’ve included a PDF version of the mindmap that represents the new structure I envisioned as I responded to the content matrix questions.

…Eric (20080825)