the main conference site. Includes the full session list, which were all recorded and are being posted here. Additional material from various sessions is being put online as well; let me (Mark) know if you’re looking for something specific and I’ll try to help you find it.
My notes (still being compiled and cleaned up). I’ll add links to materials from the sessions I went to in my notes. I’ll also try to cull some of the attendee twitter posts for each session as well here.
My twitter on the event. You’ll see a few retweets and replies on this list also.
the full SXSW twitter blast (very noisy; especially since it will include the music and film festival discussions). Specific hashtags (search terms) were created for various sessions and subjects; for the sessions I went to I included them in my notes (above).
Sitepoint has this very useful list. Some obvious, some I didn’t know. The idea is to resort to as little extra stuff as possible to accommodate IE6’s strangenesses. A few points from the article:
Set position:relative
Use display:inline for floated elements with a margin
Two competitors will swap a file back and forth in real-time, adding to and embellishing the work. Each artist gets fifteen minutes to complete a “volley” and then we post it to the site live. A third participant, a writer, provides play-by-play commentary on the action, as it happens. A match lasts for ten volleys and when it’s complete…
But I’m still agreeing with people who say the CS4 logo looks like a TV station’s (mentioned ~4:00 in):
While remembering what comes with great power, it sounds like responsible designers should treat branding guides like the pirate code—more what you’d call guidelines than actual rules.
Hmmm. So you must be a pirate for the pirate code to apply. How should that relate to a style guide?
Remember those days when a website consisted of about 2,700 nested tables? I sure do. Luckily those days are a thing of the past. With the introduction of CSS2 years back there was no good reason to keep churning out table after table in your layouts. With CSS3 and HTML5 around the corner (hopefully) things are only going to get better.
I find myself so anti-tables, I often trying to get rid of tables – for tabular data!
Even though it’s 2009, apparently some “web designers” still don’t buy into the whole no-tables movement. This past week an article titled Why CSS should not be used for layout has spread like wildfire. If you are are moderate at CSS, you will quickly realize that most his arguments are off base, but it’s any interesting read never-the-less.
Luckily, an article has been written in response to the first, Why CSS should be used for layouts. I might be a bit bias, but I find myself agreeing with the second article.
Moral of the story: let tables die already (at least for layouts). Now if we can just kill off IE6…
As a web designer, I try to stay active in the web design community. Apart from going to conferences (SXSW, Webmaster Jam Session, etc) the easiest way to do this is to follow fellow designers through RSS.
On my Netvibes page I have a Web Design tab where I keep up with a handful of designers I think are legit. Some of them update their websites more than others, but the updates are all solid. I definitely recommend subscribing to their RSS feed or at the very least check them out.
Here is the list of designers/sites I actively follow (in no specific order).
A bunch of trends are described and shown: rich UIs, PNG transparency, big typography, one-page layouts, huge illustrations and vibrant graphics (a fave: Versions for Mac), more white space than ever, etc. etc. etc. They’ve identified 31 distinct trends/design elements, most ranging from pretty cool to very very.
While things like all-Flash sites can be considered passé, here’s a new one that I love: the 2010 Prius site. Great sound design, and it helps that it’s finally a good-looking car.
I often find myself often skipping the slicing in PS and just doing it manually. However, after watching the screencast you will see it can be a true time saver – especially when dealing with sending the file (psd) between multiple designers.
'either (standards or Flash people) stay to themselves, or one...hurls insults at the other' http://is.gd/a3LcY note to self: don't do that