title: cookieless domain to serve css and js - way to organize code?
body: <p>I would like to configure my environment to serve css and javascript files from static.example.com instead of example.com/static.</p>
  
  <p>The second has the convenience that I can code my html pages to load the css and javascript files relatively eg "static/reset.css" independent of the actual domain.</p>
  
  <p>Is there a good practice to avoid altering all my source files whenever I change</p>
  
  <p>static.example.com to static.otherexample.com</p>
  
  <p>as I would have to rewrite all my HTML source files importing css and javascript?</p>