Presented by Christine Cheung
+Polished front-end is as important as back-end.
+It may scale, but bloated markup and JS will slow performance.
+The implementation of the design is what the user notices.
+Structure the hierarchy of static and template files.
+Templatetags and Filters
+Template system is meant to express presentation, not logic.
+Avoid plugin overkill. No more than 3-4.
+ * Easier to read & maintain
+Don't use $(document).ready()
+ * Backbone with Tastypie
+Tools For Rapid Development
+ .. note:: I disagree, but not important.
+ * CSS authoring framework & set of utilities
+* Leverage the power of both back and frontends
+* Share the work between them
+* Class-based views for quick prototyping
+* Write out the API, evaluate its design.
+* Know when to make a view vs API
+* Contex Processors (API keys, etc)
+* Google Closure Compiler (turns simple functions into closures)
+* Use a build script to minify and gzip files.
+.. note:: I'd recommend combining files too.
+* Have a ``TEMPLATE_DEBUG``-triggered switcher for flat/compiled static files
+.. note:: Or media: images, video, etc