The Headless Web is a web where the user rarely ever interacts with a web page in a web browser. Instead, the user experience is still expressed in HTML and executed with JavaScript but you might just visit a web page once to build a long term relationship with it. |
|
Writing a great Pull Request takes time. It can be a scary proposition going in. Did I implement something relevant? Will they like my changes? Will the PR meet their expectations? How much scrutiny can I expect? |  |
|
rel="noopener" prevents opened pages tampering with the original page, but it also has a performance boost.
|
|
Making a site work on HTTPS should be easy, but it’s not. The older your website, the harder it is to make the transition — but why? Steve takes you through a 9 month journey, on how they moved a production website to HTTPS; overcoming a 20-year-old website and its many tiers to get that green padlock, and what actually happens when you make such a breaking change. |
|
The sw-offline-google-analytics library gives you everything you need. It leverages IndexedDB to replay Google Analytics requests when a network connection is available to your visitors. I’ve already set it up for Pony Foo!  |
|
This article walks through the in’s and out’s of building a progressive app using an application shell architecture. Using Service Workers, this application uses offline functionality including offline Google Analytics! |  |
|
This job never came with a manual. If you’re like me, you got into the business of building websites writing bad teenage poetry or photoshopping crude posters for your band. Eventually, you learned the skills to put your creation on the Web and became addicted to the thrill of instant self-publication. |
|
This article cracked me up as a kid. Then I could never find it again, because I didn’t know the author nor its exact title. It’s now up on GitHub!  In the interests of creating employment opportunities in the Java programming field, I am passing on these tips from the masters on how to write code that is so difficult to maintain, that the people who come after you will take years to make even the simplest changes. |
|
Have you ever wondered why Netflix has such a great streaming experience? Do you want to learn how they completed their homepage plus other UI layout redesigns through A/B testing? If so, then this article is for you! |
|
Mathias touches on the reasons why we automate tasks, and poses a number of questions. How and when do you decide whether something is worth automating? The “time spent over time gained” metric is easy to calculate, but how do you define the happiness of colleagues? How much is speed worth in your organisation? |  |
|
|
It uses 31 runnable examples to show you the important parts of new JavaScript syntax. Many of my readers and workshop attendees complained that modern JavaScript syntax looks weird at first. They could understand what I was saying, but couldn’t read the code. So I built this cheatsheet to fix that. 
Comments