Jeremy Keith

Hydration

https://adactio.com/journal/16404

The layered approach of progressive enhancement echoes the separation of concerns in the front-end stack: HTML, CSS, and JavaScript—each layer expressing more power. But while these concepts are related, they’re not interchangable. Separating out the layers of your tech stack isn’t necessarily progressive enhancement. If you have some HTML that relies on JavaScript to be useful, then there’s no benefit in separating that HTML into a separate payload. The HTML that you initially send down the wire needs to be functional (at least at a basic level) before the JavaScript arrives.

• older link:
  OneDevice, a smartphone that makes sense
• newer link:
  Deep dive CSS: font metrics, line-height and vertical-align

---

Related contents with similar topics

1. 

   Remy Sharp

   Please disable JavaScript to view this site

   • Nicolas Hoizey
   • 30 November 2020
   • JavaScript, progressive enhancement
   • 3 reactions

   Most of the web sites I visit on an average day require JavaScript to allow me to navigate the site fully. At least once a week there will be a web…

2. 

   Kitty Giraudel

   N26 and lack of JavaScript

   • Nicolas Hoizey
   • 9 March 2020
   • JavaScript, React, progressive enhancement, User-Agent
   • 2 reactions

   Great article where Kitty shows how React helps providing N26 clients the features they're looking for even if they unfortunately have JavaScript…

3. 

   Harry Roberts

   What if?

   • Nicolas Hoizey
   • 10 December 2018
   • progressive enhancement, JavaScript

   If you’re going to build an image loader that hides the whole page until all images are ready, you must also ask yourself what if the images don’t…