-
·
Progressive Web Apps And The Web Trying To Behave More Like Apps
A 2016 article about Progressive Web Apps, offline behaviour and the idea that the web could offer some app-like qualities without giving up URLs and reach.
-
·
Yarn And The Problem With JavaScript Dependency Installs
A 2016 article about Yarn, dependency installs and why repeatable JavaScript tooling became important as front-end projects grew larger.
-
·
Vue 2.0 And The Appeal Of A Smaller Front-End Framework
A 2016 reflection on Vue 2.0 and why a lighter, approachable framework felt attractive for projects that needed structure without a large application platform.
-
·
AMP And The Trade-Offs Behind Faster Mobile Pages
A practical look at AMP in 2016, why faster mobile pages were appealing and why the technical trade-offs needed to be understood before implementation.
-
·
Bootstrap 4 Alpha And Waiting For Front-End Tools To Settle
A 2016 article about Bootstrap 4 alpha releases, the move towards more modern front-end assumptions and why alpha tools need caution in client projects.
-
·
jQuery 3.0 And Moving Away From Old Browser Workarounds
A practical reflection on jQuery 3.0, browser support and the slow move away from the compatibility workarounds that shaped front-end development for years.
-
·
WordPress 4.5 And The Small Editing Improvements That Matter
A 2016 article about WordPress 4.5 and why small improvements to editing, responsive previews and theme logos mattered in day-to-day CMS work.
-
·
Let’s Encrypt And The Moment HTTPS Became Easier To Justify
A 2016 reflection on why free, automated TLS certificates changed the practical conversation around HTTPS for ordinary business websites.
-
·
CSS Custom Properties And The Problem With Repeating Yourself
A practical look at why CSS custom properties felt useful once front-end projects started carrying repeated colours, spacing values and interface states across larger websites.
-
·
PHP 7 And Why Old Server Assumptions Needed Revisiting
A practical reflection on PHP 7 in 2015, and why faster server-side performance meant developers needed to revisit old assumptions around hosting and legacy code.