Until we find a way to translate Django's URLconf mapping and `reverse` function into Javascript, it's still the case that the best way to pass URLs in a loosely-coupled way to templates and Javascript modules is by dropping them on the page as global variables. That way, we can go through Mako and use Django's `reverse` function, rather than hard-coding URLs into static Javascript files. If we had a way to pass this information into a static Javascript file, then we wouldn't need to set up a `CMS.URL` namespace at all.