I've had a script generate my paperlined.org homepage for a while now. (the main "recent changes" list, akin to Wikipedia's recent changes page)
The script is first-generation though. It's slowly had functionality added to it, but it's getting unmaintainable. I also have a better idea of what its core competencies need to be.
So, this will be a ground-up rewrite.
Overall goals
make it slightly more polished/professional, in case prospective employers look at it (even a peer like Roger)
make it easier/quicker/more-friendly for human readers to use
there are two people who've confirmed they read it semi-regularly,
its original goal (to be good Google bait) has already been well-achieved, but being computer-readable and human-readable are two different things
make the back-end more flexible, easier to add more features (a few more features now, and possibly other features in the future)
make the front-end more flexible, integrating as many jQuery tricks as I want
make it generic enough to run on any of my websites — don't make it so tied-down to paperlined.org specifically
End-user requirements
there should be a "sitemap" page, a list of all the important directories (directories only, not files), laid out in a tree fashion
(optional) Each page should have a standard header + footer + navbar, like most normal sites have
if we go this way, then the header should include a "friendly" version of the directory navigation. eg:
directory and document settings should be specified in that directory and as close to that document as possible — having all the settings in one central place has become a huge mess, and it makes it harder to use on other websites
There should be more "classes" of documents. Some of these "classes" will require a separate file (e.g. /index.html, /friends/index.html, and /private/index.html)
documents than anyone can read
"polished" — intended audience = other people
"draft" — intended audience = other people, but it may not be polished enough to be published yet (though these will still be visible to people if they really want to see them)
"internal" — intended audience = only myself (again though, people will be able to view these if they really want to)
each directory can have a ".metadata" file, and that file can change any of the available settings for all files in all sub-directories
any document (for example, "document.txt") can have an associated metadata file (for that example, it'd be called ".document.txt.metadata") that can do per-document settings