Progressive
Enhancement Practice
ytian@thoughtworks.com
Why PE?
Separation of Concerns
Data - Structure
Presentation - Style
Behavior - Event
Why PE?
KISS
/
PE’s goal
/ Universal
/ Usability
/ Maintain
/ Communication
Practice
Mapping requirement to right layer
HTTP Restful, the web way
HTML/XHTML Structural data format
CSS Visual enhancement
Javascript Behavior enhancement
Http layer
What’s restful? The web way.
Use right request method
Use right HTTP response CODE
Use the useful HTTP headers
Resources centric URL?
Form model and Post redirect-back
Http layer
Web site should be a restful app
Human readable website is also a
computer readable API provider
(x)HTML is a valid structural ATOM
feed format
Web page is a composite
representation of domain model
(x)Html layer
Choose tag semantically
HTML Tag
HTML5 friendly?
HTML5 Name Class
(x)Html layer
Microformats
open protocal
markup conventions
semantic way
easy to parse
easy to validate
CSS Layer
reset css
css selector
css class
micro formats class
id javascript
This is a slides about progressive enhancement. It more
This is a slides about progressive enhancement. It doesn't answer what is progressive enhancement, instead it talks about how to do progressive enhancement in practice. Then you will know why you need to do progressive enhancement. In my mind PE is not a buzz word, actually it's the Web's way. We should rediscover what's right way to build web. If everything is in correct layer, this best practice called progressive enhancement. Then you got a robust system which can work in different environment and can be access by both human and computer. less
0 comments
Post a comment