CSSDay was held in sunny Arizona on December 3, 2016. The conference is geared towards front-end developers who want to dive deeper into advanced CSS topics.
CSS Day 2016 covered a wide range of topics for a one day conference including SVG, animation, color theory, design, layout and more. Throughout the day, a focus on code architecture was a theme. Attendees heard a few different perspectives which were interesting to listen to and compare.
Below are the available videos and slides of each session, including two from our very own OddBirds.
Sarah has become one of the primary voices on web-SVG and animation, leading to her recent SVG Animations book from O’Reilly.
(video unavailable)
John’s talk was a case study looking into the benefits of switching from jQuery to CSS for web and mobile applications.
(video unavaliable)
The organizers and volunteers did a great job bringing the community together.
Helping to plan CSSDay with my friends as a conference by developers, for developers, has been one of the most rewarding and exciting things that I’ve been able to do in my career. I’ve met so many amazing and talented people along the way. It has been an experience.
—Brad Westfall
This was the second year Brad Westfall organized this event. We are very thankful for conference organizers like Brad and his team, who post videos of the sessions, making this knowledge accessible for those who could not join us live.
As always, we would love to discuss the content covered in these videos shared from CSS Day 2016. Send us a message via Twitter.
We don’t have to choose between px and rem for spacing
There are many articles and established CSS best-practices that rely on determining the correct or best units to use. Now that comparison functions are well supported in CSS, we don’t have to choose.
It’s time to stop spreading this out-dated practice
Setting the box-sizing model to border-box is one of the few remaining CSS ‘resets’ used across most projects. But there are two common approaches, and the more popular choice will cause more problems than it solves.
What do all the numbers in our clamp() do?
There are multiple tools that can help create a fluid font-size calculation for CSS – generally expressed as a clamp() function combining em (or rem) with vw (or vi) units. But the results are difficult to understand at a glance, so I wanted to visualize what’s going on…