Along the same lines as relative paths, you also want to make sure that you use linux/unix style paths (with the forward slash../) instead of Windows style paths (with the back slash...\). Most browsers theses days can easily deal with either path style, but you will eliminate any potential compatibility issues (and even some server side issues when you start dealing with back end systems) by sticking with forward slash.
For example, instead of .\resources\style.css it would be ./resources/css/style.css. This would apply to all other paths as well (e.g. images, script resources, etc.)
Along the same lines as relative paths, you also want to make sure that you use linux/unix style paths (with the forward slash..
/) instead of Windows style paths (with the back slash...\). Most browsers theses days can easily deal with either path style, but you will eliminate any potential compatibility issues (and even some server side issues when you start dealing with back end systems) by sticking with forward slash.For example, instead of
.\resources\style.cssit would be./resources/css/style.css. This would apply to all other paths as well (e.g. images, script resources, etc.)