This document summarizes the highlights from the FOWD 2009 conference, compressing 8 hours of talks into 25 minutes. It includes summaries of presentations on progressive enhancements with CSS3, designing for user feedback at Digg, the future of web design with new display technologies, actively designing community at Vimeo, getting work done without worrying, the future of markup languages, and creating art with technology. The document also notes that a panel debate on short form vs. long form content did not produce many clear answers.
5. EXPERIENCE
STYLE
MARKUP
Dan Cederholm: Progressive Enhancements
6. Highlights
1. Enriching form elements
Yahoo is rounding corners on submit buttons
2. RGBA
A = Alpha (also awesome?)
3. Drop shadows that don’t hurt
Built in support eliminates loads of work
Dan Cederholm: Progressive Enhancements
7. Highlights
4. Scaling images on hover
Eliminates need for duplicate images (ex: thumbs)
5. Rotation
Interesting opportunities for user-feedback
6. Fade effects
Reduces need to create separate images
Dan Cederholm: Progressive Enhancements
8. “ None of this
stuff matters.”
IE users: A less polished but not
diminished user experience.
Dan Cederholm: Progressive Enhancements
9. News?
1. Add some sexy to your standalone
Experimental projects are a good starting spot
2. Today’s 10% = Tomorrow’s 40%
Hone your style
3. Break up with Flash
E ects might help us relax our death grip on Flash
Dan Cederholm: Progressive Enhancements
38. The Long
& Short of It
A debate about consumption and creation
of content in long vs. short form.
Panel Debate on Content: Short Form vs. Long Form
40. Why?
1. Form is specific to content-type
2. How long should a video be?
3. Short form introduces long form
4. Editorial and marketing
perspectives are very different
Panel Debate on Content: Short Form vs. Long Form
41. AUTHORITY
Is authority inherent in long form?
How is authority established in short form?
Panel Debate on Content: Short Form vs. Long Form
45. XHTML 1.0
Bridge between HTML and XML
Strict code formatting
MIME type problems in IE
Molly Holzschlag: Opera
46. XHTML 2
Not backwards compatible
Effective only on a closed system
Molly Holzschlag: Opera
47. WHAT Working
Group
Web Hypertext Applications
Technology Development Group
Started in 2004
Non draconian error handling
Molly Holzschlag: Opera
48. Highlights
1. Forms 2.0
Required attribute will kick ass, for instance
2. New APIs
HTML 5 specifies scripting APIs and OTHERS
3. Existing DOM interfaces are better
Javascript will be really helpful here
Molly Holzschlag: Opera
