Adding any kind of tracking to any project always seems to be an afterthought. Generally just before launching, a stakeholder puts their hand up and states that we need to track everything…. Usually resulting in lots of frustrating mutterings from all developers involved.
Another big week in the web design world. Gregory Ciotti, part of the marketing team at Help Scout, delves into the psychology of colour. Matt Mullenweg was interviewed at WordCamp Europe. Alex Bachuk wrote a great getting started piece for Redux and so much more.
A quick introduction into using any Google font within your website.
The screencast looks at how you go about selecting fonts on font.google.com. Adding them to your website and then using them inside your stylesheet.
const plus compare
let and finally understand when to use the spread operator.
Jonathan White sees valid points to both sides of the debate about whether designers should learn to code or whether developers should learn to design. Learn how to set up HTTPS quickly and for free on your WordPress site. A detailed post all about CSS display layouts by Chen Hui Jing and more. Enjoy.
Google’s Rob Dodson recently ran into difficulty adding proper keyboard support to some components he was building and shares his ideas on how to resolve things. The team at Facebook blogged about the ins and out of how they keep their CSS quality high. Scott Jehl came across a better way to improve handling browser-or-network conditions in more fault-tolerant ways. Google Fonts had na massive redesign and more. Enjoy.
Working within a team or solo can adjust the development priorities but one that should always be high on the agenda is producing the best code possible.
Working on a clean, well organised codebase is bliss. It’s enjoyable and productive. Working on an unorganised codebase is annoying to say the least. It’s often frustrating, painfully slow to change and test anything and invites laziness.
Thankfully as CSS developers we have a handy tool called Stylelint that can help us avoid the unorganised situation.
Jan Lehnardt looks into Progressive Web Apps and where things are headed. Jon Gold shares the theory behind declarative tooling with a nice transition into information about his new tool René that he just released. John Moore Williams puts forward the point that many style guide’s on the web these days are missing, voice, tone and editorial guidelines. Bill Jordan has compiled a detailed, common sense how to guide to steer software development managers in the right direction in caring for their employees with best results and lots more. Enjoy.
This post by Marcelo Somers looks at the good and bad parts of writing functional CSS.
I loved writing really clever, powerful CSS classes. I argued for it because of “ease of developer consumption.” My goal was that a developer could add a single class to an element and it would automagically do everything for them. Basically, the opposite of functional CSS.
3 months into a functional approach to CSS architecture, I’m addicted. The times I’ve used the old monolith approach, it’s become a tedious challenge in jumping between files constantly. I think I’m convinced, but I’m still trying to rationalize scalability issues as my functional codebases grow and evolve.
I’m a massive fan of functional CSS and would highly recommend experimenting.
jQuery 3.0 is now released! This version has been in the works since October 2014. We set out to create a slimmer, faster version of jQuery (with backwards compatibility in mind). We’ve removed all of the old IE workarounds and taken advantage of some of the more modern web APIs where it made sense.
In a nutshell:
- Deleted oldIE code
- Slim version (removes ajax/effects)
- Promises/A+ Deferred
What are you waiting for! Go and update your version of jQuery