[eluser]Nick Husher[/eluser]
I agree.
My own personal structural convention for client-executed code is to set up my root directory like this:
Code:
/index.php
/system/... #CI Applciation (server-executed code)
/.htaccess
/src/ #client-executed code
/src/css #css files
/src/js #javascript files
/src/img #site image files (background images, icons, non-dynamic artwork etc.)
/src/fla #site flash files (for sIFR, usually)
At that point, it becomes quite easy to include those files in my CI views:
Code:
<head>
<base href="path-to-application/" />
<link rel="stylesheet" type="text/css" href="/src/css/screen.css" media="screen" />
...
</head>
Note that your base href can be dynamically generated from your CI config settings. You might want to use more human-friendly directory names; I picked abbreviated ones because I started doing web development entirely on the command line where three-character directory names are sorta-standard. The only reason I keep it up is out of habit.