##Prototype test notes template
###Observations:
- Observation 1
- Observation 2
- Observation 3
- Observation 4
- Observation 5
###Questions:
##Prototype test notes template
###Observations:
###Questions:
Add the ext property to both the options and object in the files array:
assemble: {
docs: {
options: {
layout: 'default.hbs',
ext: '.html'
},
files: [| @import "compass/css3/shared"; | |
| // NOTE: | |
| // All mixins for the 2009 spec have been written assuming they'll be fed property values that | |
| // correspond to the standard spec. Some mixins can be fed values from the 2009 spec, but don't | |
| // rely on it. The `legacy-order` mixin will increment the value fed to it because the 2009 | |
| // `box-ordinal-group` property begins indexing at 1, while the modern `order` property begins | |
| // indexing at 0. | |
| // if `true`, the 2009 properties will be emitted as part of the normal mixin call |
You wanna serve up static files, but are bored by the usual trick of:
python -m SimpleHTTPServer
This is pretty simple but why type this every time? Let's use Pow for some zero-effort web serving. If you have Pow already set up, then just drop the provided config.ru file into the root of your static files. Then link your directory into ~/.pow so Pow can see it and that's it!
Let's say you have a directory with mockups you wanna show people, they are in ~/Dropbox/Mockups/ then you might do this:
| // We all know how to use mixins, right? | |
| @mixin kung { | |
| background: green; | |
| color: yellow; | |
| } | |
| @mixin foo { | |
| background: orange; | |
| color: red; |
This gist assumes:
| set :application, 'foo' | |
| set :repository, '_site' | |
| set :scm, :none | |
| set :deploy_via, :copy | |
| set :copy_compression, :gzip | |
| set :use_sudo, false | |
| set :host, '127.0.0.1' | |
| role :web, host | |
| role :app, host |