mozilla/kuma — pull request #1243 by darkwing (2013-07-24 02:21:01+00:00)
Title: DO NOT MERGE:  Add redesign structure, including assets and template

Submitting this PR to start a conversation about the redesign implementation. Within this PR, I have:

1. Created a "/media/redesign" directory where all of our new CSS, JS, fonts, and images will go
2. Created a "/templates/redesign_base.html" file so that we don't have to add numerous more IF/ELSE's to accommodate for the new structure
3. Created "styl" files within "/media/redesign/stylus"; these starter files accommodate basics like CSS reset, the sandstone grid, print styles, and more.
4. A "compile" executable which outputs our stylus code to full, compressed CSS

Taking points include:

1. Does the "redesign_base.html" seem reasonable or do we want to stick to one base.html file with a bunch of conditionals? Do we foresee any problems here?

2. Where should the "compile" executable go, and can it be added to our push/build script?

Interested in hearing thoughts.