Once there, you can do a lot. Believe it or not, WebGUI is so customizeable that you can choose to upload files and give them any URL you want, regardless of where they were uploaded. If you choose to use the Asset Installer app, images/files might go into the Import Node. I've seen it done, and it makes sense, especially to convert from web templates... to change references from src="images/image.jpg" to src=^FileUrl("images/image.jpg");", where image.jpg is the file you uploaded and the URL is manually changed to images/image.jpg. The downside of this, of course, is to know that the ability to edit or remove that image could be hidden if you don't know the page upon which the filepile was unleashed.

WebGUI Folders could be used to help organize these images (and preview them outside of normal web views) if they become unruly. The beauty of a database of files/images is the complete disconnect between where you think the images are/should be located and the actual location of the images. In a way, user ignorance of their current location except by reference -- that is, a user knows that the image is at images/image.jpg; and user preference about where to dump images for a new project -- "hidden" in the page that's to be shown to the world ; this actually gives rise to the flexibility for you to make your own "best practices".
wg-fomATgwyDOTorg