title: Xcode Project Resource Organization and Structure
body: <p>I am relatively new to Xcode and one thing that has bothered me is that when I add a resource it gets added to the top level directory of my project directory. So for example, at the moment, all of my images are at the top level directory and it makes things look messy. I rather would've liked, for example, to have an <strong>images/</strong> folder and then sub-folders within that to store images for certain things, like <strong>tab-bar/</strong> icons. Is this possible? Or is it convention to just keep everything in the top level directory?</p>
  
  <p>Someone in the <code>#iphonedev</code> channel at freenode told me something about the build process rule or something, it just seemed too complicated I figured I shouldn't bother, and that most people just kept things at their root directory considering the complexity of the solution. Perhaps it isn't all that complicated though, I just felt it should be easier.</p>
  
  <p>For example I would also like to have a sub-folder for my views, like <strong>views/</strong> that stores all of my nib files; currently they are all in the top level directory. And the same goes for my property lists.</p>
  
  <p>I would appreciate it if you could tell me what the convention is, I doubt it is to just store everything in the top level directory. And I'm referring to the actual file system, not simply creating 'virtual folders' in Xcode to organize things, because the top level directory of my project will still be a mess. And if it is possible to organize things better, I would appreciate any detailed help on how to accomplish it.</p>
  
  <p>I think I have heard that in the final build, the entire file structure gets squashed to the root directory. I don't mind so much about that, I just want things to be organized while I am working on my project. I think this is where that 'build rule' thing comes in, but I'm not sure how or what to do.</p>