Hi list, glad that you mentioned the outdated link. I already removed it.
First i wanted to push you at the nettuts link, but after roughly reading over it, i realized that a lot of the stuff recommended is against blueprints best practice (noted at the wiki now). I also saw, that the wiki quick start guide is an empty page. Due to the fact that Christian & myself are already (slowly) working on blueprint 1.1 - which will bring some nice additions - we ain't got too much time at the moment for writing tutorials. My recommendation is the following: + Load our dev environment [1] ,which contains -- a test page with some explanation -- our debug plugin that will highlight every wrong useage of blueprint classes + Grap the cheat sheet + take a look at our main site [2] and inspect the source of the live demos [3] with firebug or similar + If you got questions left, post them here at the list and you'll find a lot of people who can push you in the right direction Looking at the time i got left over the next weeks i might be able to wright a new quick start with the end of the coming week. Anyway i'll announce it here on the list, so keep reading :) Kaiser. __dev environment will be part of bp 1.1., so don't miss it__ [1] https://github.com/franz-josef-kaiser/blueprint-dev---debug [2] http://blueprintcss.org/ [3] http://blueprintcss.org/tests/ -- You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en.
