Some great advice in here. The document outline matters, folks!
The Best of the Internets
A tale of woe as old as… well, the Web. The Web is mutable. Content disappears, for good and for bad. This is part of the reason projects like Archive.org and Perma.cc excite me so much. It’s also why I chose to use Perma.cc to archive every site referenced in my book.
Edge 16 brings independent rendering to every page on the Web.
An excellent (and exhaustive) look at how how animation can be integrated into style guides and pattern libraries. It includes excellent examples from FutureLearn, Google, Marvel, SalesForce.
Great work Alla!
A good rough guide to beefing up you site’s accessibility. I’m not sure I agree with the timings she allotted for each task as those really depend on the site, but the list is solid overall.
A nice straightforward walkthrough of how to store failed form POSTs to send again when the network becomes available. Ah the joys of Service Worker!
It seems like the Android team and the Chrome team were not on the same page and Android Oreo (a.k.a., Android 8) undermines some critical features of Progressive Web Apps. As Maximiliano is quick to point out, most of these are easily fixable in a software update, so there’s not a whole lot of wailing and gnashing of teeth needed, but you should still be aware of how the experience differs from what users saw on the previous release.
In particular, I am hating the mini-Chrome icon overlay. For normal Homescreen bookmarks, I’m willing to let it go, but if a site has a Web App Manifest, it should look like any other app.
This is great to see! I think
link[rel="canonical"] is not used often enough. I’d love to see all sharing protocols adopt this approach for things like cross-posts, m-dot sites, and more.
This is an interesting proposal. It’s a shame the
map element is already taken.
This is a wonderful walkthrough of how Cloud Four progressively enhanced their site into a Progressive Web App over a six-month period.