Friday Frontend: Jan 12 Edition
Hope you had a great week this week! This was my first week back from the end of year holiday break, and I can definitely feel the positive impact of the time off. It’s good to take some time for yourself every now and then, you come back so much more focused and productive.
KBall from ZenDev
CSS & SCSS
A guide to how to control OpenType variants using CSS. Super cool stuff, and this is one of the most detailed breakdowns I”ve seen in terms of exactly what is accessible via CSS.
I know we tend to emphasize online resource here in this mailing list, but this is a nice list of actual dead-tree books for growing your CSS skills.
An interesting combo post by Rachel Andrew, one of the top CSS Grid Layout folks in the world, this contains both a list of new resources that she’s put together for learning and thinking about Flexbox, as well as some context for how she recommends thinking about Flexbox and CSS Grid and their relationship.
I’m still trying to wrap my head around this attack and all of the implications, and the state of the art seems to be changing daily as browsers and operating system vendors implement patches, but this seems pretty important if you’re using cookie-based techniques for critical CSS.
I like this article because it’s not only tackling some real world problems and walking through how they did it, but it also handles fallback to older browsers and gives you some concrete examples of using a postCSS mixin to handle the varied types of fallbacks needed for different browsers.
Nuxt.js is a framework on top of Vue.js that makes it simple and straightforward to create and deploy not only single page apps, but also universal (server side rendered + SPA post rendering) and static generated sites. I’ve been using Nuxt on one of my projects now for a couple of months and can definitely say it is awesome! If you’re working in or interested in Vue, this is a must see.
Just last month, the new HTML 5.2 spec was finalized as a W3C recommendation. This article does a very nice breakdown of some of the key changes and what they mean to you as a developer.
Folks across the industry are pushing back against the level of control Google has over AMP, and the way they’re using it to grab control. This is a very thoughtful and well-written letter about the problems with the way AMP is currently run, with the ability for anyone to cosign. And early signs are the AMP team is listening. Let’s keep the pressure on!
One of the reasons there is such a concern with AMP is that using it does allow for some key advantages. This is a great case study of how Airbnb has been using AMP, some challenges they ran into, and how they’ve adjusted.
I love this approach to Architecture and development philosophy; circumstances change, tools change, and our knowledge changes, and so our architectures must constantly be changing and evolving as well. Also love the Martin Fowler quote: “The only thing a Big Bang rewrite guarantees is a Big *Bang*.” Hadn’t heard that before but I’m going to start using it.
This is interesting. I’d always thought about Accessibility testing as a very manual process, but this article makes the argument that pieces of it are amenable to automated testing, and shows how to get started.