This should be implemented either as a build hook (ahead-of-time; static assets live on the server as minified) or as a Tornado mixin (readily available; assets are minified and cached as such).
Noticeable performance gains can be had once this is implemented on JS and CSS files.
This isn't a necessary goal for the EECS demo, and will be sidelined while higher-priority issues are tackled; however, this is an important enhancement as this application nears a public rollout, and shouldn't be overlooked long-term.
This should be implemented either as a build hook (ahead-of-time; static assets live on the server as minified) or as a Tornado mixin (readily available; assets are minified and cached as such).
Noticeable performance gains can be had once this is implemented on JS and CSS files.
This isn't a necessary goal for the EECS demo, and will be sidelined while higher-priority issues are tackled; however, this is an important enhancement as this application nears a public rollout, and shouldn't be overlooked long-term.