What CSS properties might it make sense to apply to every single element on the page? We’ll take a look at some that may (or may not) be a good idea.
Quick overview of the hot drama regarding vendor prefixes.
I’ve been using SASS for pretty much everything I do recently. Here’s some musings on the journey. From hold-ups, to trip-ups, to turn-offs. From apps and teams to workflows and syntax.…
Interesting question:
css3 speech bubble question: for the “triangle”‘s border color, how can I set it to whatever its parent div’s bgcolor is automagically?
— Jin Yang (@jzy) February 1, 2012…
What do you think folks? Is a new language going to come along in the next ten years that deals with layout / style / design and unseat CSS? Or at least give it a run for its money?
You should vote not based on if there will be any attempt at it, which there certainly will be and already has. But instead if you think one of those attempts will actually make it into native support by a browser …
In this screencast I move my own personal website from my old live FTP editing ways to a proper version controlled system including deployment. I haven't had much experience with this, so forgive me if it's a big rough.
We start by moving the live website local, including bringing all the files down and copying the database. Then we set up a Git repository in Beanstalk and push it all up to that. Then we give Beanstalk our FTP credentials and set up how we want deployment done. Then we make some local changes to our site, and commit/push them to Beanstalk, which does the deployment for us. By then end, it's all working perfectly.
If you've got questions/comments/suggestions on this workflow, I'd love to hear!
Links from the video:
I'll be representin' Wufoo at a bunch of BarCamps again this year. Super fun. We need to figure out exactly what (U.S.) cities we are going to go to this year, so if you are organizing one, hit us up at the form on the site.
Jeffrey Way, Dave and I talk shop about some newly released projects, -webkit-gate, and our weekly staple of Q&A.
Interesting idea by Felipe G on using a new at-rule, @-vendor-unlock, to tell the browser to use it's experimental implementation of any particular property, rather than using a vendor prefix on that property. Unfortunately at this point, even if you could get all the browsers on board, you'd need to use this and vendor prefixes to get deep support, which makes the problem worse. What we really need is for all browsers to implement auto-updating so eventually "supporting older browsers" is something we can look back and laugh at.
