Last week I went to AKQA in London to give a brown-bag presentation on progressive enhancement. I took this chance to vent some of my ideas on the subject and counteract some of the criticisms I heard about the need for enhancing web solutions progressively.
I’ve come up with the following “Seven rules of progressive enhancement”:
- Separate as much as possible
- Build on things that work
- Generate dependent markup
- Test for everything before you apply it
- Explore the environment
- Load on demand
- Modularize code
Instead of explaining them here, I’ve used a longer train ride to write up an article on the subject explaining the details of all the “rules” and examples of why and how to use them: Pragmatic Progressive Enhancement.
The article is licensed with creative commons, so you are very much invited to use and remix it to your needs.
I will upload my slides together with a video of the presentation once I got the material and checked if the video quality is good enough for publication.