bowdenweb

Anyone who’s spent anytime in webdev should be quite familiar with “standard” naming conventions for folder directories: I’m speaking specifically about root/images, root/javascript, root/styles, etc. With 140 characters being a key target in mind, as well as simply trying to minimalize all of my processes/work-flows, I’ve decided to break from the flock and (gasp) make my directory structure as simple as possible. Note: this is probably not the best idea if you work with enterprise code unless your team has well established documentation and is open to ideas. Then again, if your team is that up to speed, you wouldn’t be working with enterprise code.

This process is not hard or complicated, just minimalize the naming convention, whereas root/images is now root/i. Seriously, that’s it. Point. Blank. Period. Minimalizing your information architecture and site architecture, while also possibly getting your domain/branding/content more exposure.

Note: While I find these naming conventions to be user-friendly, it should be pointed out that most people will not; at least not until you explain it to them. Also, this method is probably not as seo-friendly as the former, basically because I’m assuming that the bots recognize /img and/or /images (“standards”) for better indexing, so if Image Search is important to you, you might want to rethink this. Although I see no reason for the bots to not adapt.