Ancestors

Toot

Written by fershad on 2025-01-06 at 07:22

As part of a recent website rebuild, I started dogfooding the Grid-aware Websites code we're developing at the Green Web Foundation. This post explains the idea, how it's implemented, as well as tries to work out the impacts grid-aware changes have on my site.

https://fershad.com/writing/making-this-website-grid-aware/

=> More informations about this toot | More toots from fershad@indieweb.social

Descendants

Written by 🖖🏻 David Hund on 2025-01-06 at 07:55

@fershad very interesting writeup, thanks!

=> More informations about this toot | More toots from davidhund@mastodon.cloud

Written by fershad on 2025-01-06 at 12:59

@davidhund thanks David ~

=> More informations about this toot | More toots from fershad@indieweb.social

Written by 🖖🏻 David Hund on 2025-01-06 at 13:54

@fershad At https://fershad.com/writing/making-this-website-grid-aware/#determining-the-status-of-a-users-grid — should the 'above' and 'below' 50% not be flipped in the context of your site changes?

I.e. "'low-carbon' power percentage (i.e. renewables plus nuclear) is above or below 50%" would mean that you want grid-aware 'optimizations' (such as removing elements) to be made when this percentage is below 50% ;-)

=> More informations about this toot | More toots from davidhund@mastodon.cloud

Written by 🖖🏻 David Hund on 2025-01-06 at 13:58

@fershad …but in general it might be preferable to use Progressive Enhancement (PE) and start with the optimized version and 'enhance' the page when low-carbon power is > 50%?

I was also wondering if it would be good practice to filter JS (and CSS?) in the edge functions instead of (in your example) skipping these and filter only HTML. Assuming its JS (and CSS?) that are most client-side intensive…

=> More informations about this toot | More toots from davidhund@mastodon.cloud

Written by 🖖🏻 David Hund on 2025-01-06 at 14:01

@fershad Last random thought is how the client-side optimizations offset the increased power usage of the required Edge Functions.

One optimization might be to abstract this behind an API and have 'cached' responses for locations.

Anyway… I'm rambling: very interesting experiment 👏

=> More informations about this toot | More toots from davidhund@mastodon.cloud

Written by 🖖🏻 David Hund on 2025-01-06 at 14:51

@fershad I just found many of my questions answered at https://www.thegreenwebfoundation.org/news/first-grid-aware-websites-advisory-group-meeting/ 😬

=> More informations about this toot | More toots from davidhund@mastodon.cloud

Written by fershad on 2025-01-15 at 05:31

@davidhund thanks for your feedback & sorry I didn't get back to it sooner. I'm glad our blog post answered many of your questions.

=> More informations about this toot | More toots from fershad@indieweb.social

Written by fershad on 2025-01-15 at 05:31

@davidhund Your comment about progressive enhancement has stuck with me. I took the "remove HTML nodes" approach because it was one that I could quickly implement. It's also the approach I can see people taking when they first try out grid-awareness on sites they own.

However, the idea of starting with a low-impact site & then adding functionality when a user's grid allows for it makes much more sense for a new site/redesign like mine. I've got it on my mind & is something I'm stewing on.

=> More informations about this toot | More toots from fershad@indieweb.social

Written by 🖖🏻 David Hund on 2025-01-15 at 11:25

@fershad Cool and very true: the remove-nodes approach makes sense for existing sites, the PE approach more for new sites 👍

=> More informations about this toot | More toots from davidhund@mastodon.cloud