One of the great things about Eleventy is its flexibility and its lack of assumptions about how your projects should be organized. However, in order to preserve my own sanity, I needed to come up with a default files and folders architecture that made sense to me.

Nous avons deman­dé à Hubert Guillaud, Rédac­teur en chef d’InternetActu et ana­lyste des grands mou­ve­ments et phé­no­mènes qui tra­versent le champ du numé­rique et de la poli­tique, son avis sur la pos­si­bi­li­té d’une poli­tique publique (pro­gres­siste) du numé­rique. « Nous sommes cer­nés par des sys­tèmes néo­li­bé­raux aug­men­tés par le numé­rique et les sys­tèmes numé­riques de gauche sont...

If your site uses native image lazy-loading, check how it's implemented and run A/B tests to better understand its performance costs. It may benefit from more eagerly loading images above the fold.

By combining the powers of real-user experiences in the Chrome UX Report 3 (CrUX) dataset with web technology detections in HTTP Archive 1, we can get a glimpse into how architectural decisions like choices of CMS platform or JavaScript framework play a role in sites’ CWV performance.

Putting images on websites is incredibly simple, yes? Actually, yes, it is. You use <img> and link it to a valid source in the src attribute and you’re done. Except that there are (counts fingers) 927 things you could (and some you really should) do that often go overlooked. Let’s see…

As we have seen, the for-of loop beats for, for-in, and .forEach() w.r.t. usability.

Any difference in performance between the four looping mechanisms should normally not matter. If it does, you are probably doing something very computationally intensive and switching to WebAssembly may make sense.