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
Chris Coyier explores the shifting performance onus in a number of front end features from browser to developer in recent years. Shaun Bent shares an in-depth review of the BBC sport sites CSS. David Gilbertson talks about the wonders of using React and Firebase together. Cristina Silva gives us a good reminder to make sure we are picking solutions that work best for your project’s goals and so much more. Enjoy.
PostCSS has been around since September 2013 and has been part of many developers workflow for a while. For those that haven’t had the time to dig into it and put some time aside to understand what it is and what it can do, this post is for you.
An epic post by Jon Gold that shares his thoughts around merging typographic design and artificial intelligences. Fascinating read. An insightful post by Karri Saarinen that looks behind the scenes of Airbnb’s new design system. Ben Frain explains his procedures for debugging CSS along with a few handy tricks to make the most of your debugging time. Jason Grigsby dives into the nitty gritty of how autofill works, how to build forms that support cross browser autofill and take advantage of new features like scanning cards and so much more. Enjoy.
Cap Watkins reminds us that it is important to look inward into your team to make sure that each person understands the roles of others and that the team is working together. Harry Roberts shares some good adivce on using of !important within your CSS. Boopathi Rajaa discusses some of the gotchas when developing a web application with offline capabilities using service workers and so much more.
The team at Airbnb share an insight into how they scale knowledge across its ever-growing organization. Sarah Drasner compares various animation tools that she’s had experience with and breaks down the pros and cons of each method. The WebKit team are heading in the direction of implementing experimental features unprefixed and putting them behind a runtime flag and so much more. Enjoy.