properly read & render markdown files in subdirectories

[sethvincent]

Right now only the files in the top level markdown directory are read.

It's easy to make a change that recursively reads the files by changing the filter argument passed to read-directory, but currently the name of the subdirectories are excluded from the resulting object keys.

Main questions:

• Should the routes of the app reflect the directory structure?
• Should there be an option that determines if the routes reflect the directory structure?
• If routes reflect directory structure, what should happen when a markdown file is at /test/foo and a user navigates to /test/? Probably just show the first matching file?

This is somewhat related to #5, inferring the table of contents from the directory structure

[joehand]

Should the routes of the app reflect the directory structure?

This makes sense to me.

If routes reflect directory structure, what should happen when a markdown file is at /test/foo and a user navigates to /test/? Probably just show the first matching file?

Sounds good. When you say first, is that first alphabetically or first in the TOC (latter would be preferable)?