The reason I’m asking this questions is I’m attempting to develop a set of best practices to work into my normal workflow.
After doing a little research it looks like a lot of people are using Unix/Windows filenames, but lowercase lettering for any folders they create. It also looks like most people prefer one common resource folder, but I don’t know why one option would be better than the other.
Lower-case folders and filenames are traditional, but not required. The only thing you really have to fix is spaces in filenames. In a Unix filesystem, capital letters sort higher than lower-case, so you could see
Resources
apple
banana
chocolate
resources
if you looked in a directory on your server using a tool that didn’t enforce Mac sorting.
The common resource folder seems to be a current thing, getting around a problem with constant re-uploads, but I have also used that feature in the past for sites that used template systems, since it makes it less confusing to figure out which resources folder to hit when you don’t know precisely where the page is being called from.
Walter
On Feb 11, 2012, at 3:33 AM, RavenManiac wrote:
The reason I’m asking this questions is I’m attempting to develop a set of best practices to work into my normal workflow.
After doing a little research it looks like a lot of people are using Unix/Windows filenames, but lowercase lettering for any folders they create. It also looks like most people prefer one common resource folder, but I don’t know why one option would be better than the other.
It depends on the system. If I know I will be doing something clever with a CMS, then I generally use Single Resource Folder, otherwise I leave it with the default Separate Resource Folders. I generally always use Unix file names, and XHTML Strict. I’ve rarely seen a reason to do otherwise.
Walter
On Feb 11, 2012, at 12:01 PM, RavenManiac wrote:
So, when you’re designing a system from scratch which method do you personally prefer?