We are going to be taking a hard look at file organization on the site. These are the sorts of issues that bubble to the surface over time, one must understand, and it is a Good Thing that this need has come to our attention at this early stage. We can almost guarantee that things are going to break in a major way. For that, we prematurely apologize.
In order to bring some order to the file structure, we are going to alter the upload system in such a way that user files will be created in user directories, reserving the root of the files tree for site graphics such as the logo. This will help keep things from becoming nightmarishly cluttered.
Additionally, we will be reorganizing how the system creates paths. Similar to the *nix behavior of "everything is a file", in DrupalThe Content Management System (CMS) that powers this website. It is a free and open source software solution created by Dries Buytaert. Find more information at Drupal.org. "everything is a nodeA node is a piece of content in Drupal. A node usually corresponds to a page. Nodes generally have a title and a body. Nodes may have more fields (or different names for the two default fields). Each node has a content type and may be further classified by taxonomy, the node author, and so on. As the primary building blocks, nodes are the site in a very real way. A large variety of core and contributed modules are available to alter the way nodes are organized, displayed, and created.". Usually, this will not be obvious from a user perspective. They will see a link to, for instance, wwandi.com/content/foobar. That is actually an alias to, for example, wwandi.com/node/123. Internally, the system works with nodes numerically. Like IP addresses aliased to something more human-readable (example.com instead of 123.123.10.123), this is done for mostly cosmetic and ease-of-use purposes.
Ideally, each type of content will appear to be a file in a subdirectory of content. To clarify: if one creates an Image node titled Random Drawing, it would be located at wwandi.com/content/ink/images/random-drawing and the image file would be stored in /sites/default/files/[user]/images/[filename].
Some things (the Eye Candy slide show and the Images page, for instance) should be theoretically unaffected by these changes because the system creates those automagically. Statically linked images that are not in the root of the files tree will be broken.
This is not necessarily a necessary thing, but it does seem important. Getting organized early on is a good way to be organized later when moving things around would be a nightmare.