AMPersand | Ethan Marcotte

Second is the article which led me to Lighthouse in the first place: AMPersand, by Ethan Marcotte. Not much to add to this one, just another voice adding weight to my uneasiness with the idea of AMP and similar projects. Well worth a read if you're interested in the open web.

Few corporations have done as much as Google to elevate the importance of page speed as a design issue, and the work done by the AMP team is no exception. But in my experience, the only voices promoting AMP’s performance benefits are coming from inside Google.

Note: this was originally part of a full article titled "Stickers, Eclipses and Lighthouses" and the 36th post in my New 52 challenge. That article also linked to a (then) new tool called Google Lighthouse, a design collection of achievement stickers for developers, a look at time management, and a critique of data visualisation of future solar eclipses.

Explore Other Notes

Newer

The importance of routine

Fourth on the list is a simple article from Martian Craft outlining "The Importance of Routine". The post is aimed at remote works and is far from news to me, but it is a well-written example of how […]

Older

Learning from Lego with modular design

An interesting look at using padding only on the very lowest element within a hierarchy (as Samantha says, the atoms of your design) and therefore setting it globally. It's a logical approach, though […]
  • Second is the article which led me to Lighthouse in the first place: AMPersand, by Ethan Marcotte. Not much to add to this one, just another voice adding weight to my uneasiness with the idea of AMP […]
  • Murray Adcock.
Journal permalink

Made By Me, But Made Possible By:

CMS:

Build: Gatsby

Deployment: GitHub

Hosting: Netlify

Connect With Me:

Twitter Twitter

Instagram Instragram

500px 500px

GitHub GitHub

Keep Up To Date:

All Posts RSS feed.

Articles RSS feed.

Journal RSS feed.

Notes RSS feed.