Fabian

just some more ideas since i just found this in the docs: ``` Adds a test case to be executed, with testCase being an object of key/value pairs with url...

> dynamic scaffolding i guess that has something to do with the vars... but otherwise i am not sure what that could mean...

ah – i guess that is about the full pingy client. you don't want one repo per scaffold, but configure the scaffolds from one pool of files... i'm just wondering...

i get it – bootstrap is good example 👍👍 > That's a possibility. I'll review it again when dynamic scaffolding is released. cool – i fell over that multiple times...

I'd like to keep it usable when being offline. I could probably add a folder for "unmanaged assets" within source, clone the font-awesome repo in there and import the font-files...

for now i went with cloning the whole fa repo into my assets folder. read a lot of comments on recent pull requests of sprockets, rails, sprockets-sass, sprockets-helpers, asf. looks...

hmm, i should have read the slim docs before, sorry :/ http://rdoc.info/gems/slim#Inline_html____HTML_style_

found something related: i like to keep content apart from structure by rendering markdown-files into the pages ([example](https://github.com/filtercake/something/blob/master/source/index.html.haml#L97)). currently i can only render partials in the same language – meaning...

if writing in a text file is the easiest way to go, i'm all for it. there are probably tons of twitter-archiving tools out there already. so having the "log"...

well... mongohq would be another external dependency - which again has external dependencies (S2). not judging, just saying. if it is easier to implement than txt-dumping, and even brings other...