-
·
Let’s Encrypt And Making HTTPS A Normal Website Decision
A practical article about Let’s Encrypt in 2015 and why easier certificates changed how small websites could approach HTTPS.
-
·
WordPress 4.4 And Responsive Images Becoming A Default Expectation
A 2015 WordPress article about responsive images, REST API infrastructure and why media handling was becoming part of the CMS rather than a theme afterthought.
-
·
AMP And The Mobile Web Performance Problem Becoming Harder To Ignore
A practical 2015 article about AMP and why the announcement reflected a wider frustration with slow, heavy mobile pages.
-
·
Bootstrap 4 Alpha And Rebuilding A Shared Front-End Base
A 2015 reflection on Bootstrap 4 alpha and why the more interesting discussion was the need to rebuild shared front-end systems once real projects had exposed their limits.
-
·
ECMAScript 2015 And Writing JavaScript With A Longer View
A practical 2015 article about ES2015, and why the new JavaScript features mattered most when they made larger codebases easier to understand over time.
-
·
HTTP/2 And The Performance Conversation Changing Shape
A practical article about HTTP/2 in 2015, and why front-end performance work was starting to move beyond simply reducing the number of requests.
-
·
Service Workers And The First Serious Conversation About Offline Web Pages
A 2015 reflection on service workers, offline behaviour and why web pages needed to start thinking more carefully about unreliable networks.
-
·
AngularJS 1.3 And When Two-Way Binding Needed More Discipline
A practical look at AngularJS 1.3, richer client-side interfaces and why two-way binding needed structure once applications started becoming more serious.
-
·
HTML5 Becoming Official And What That Meant In Real Projects
A practical look at HTML5 becoming a W3C Recommendation in 2014 and why the moment mattered even though developers had already been using many parts of it for years.
-
·
Gulp And Keeping Front-End Build Steps Readable
A practical look at why Gulp-style build tasks became attractive in 2014 as front-end projects needed repeatable asset processing without becoming harder to understand.