Hampton will introduce the conference.
Jeremy Keith (@adactio) recently wrote "I don’t think that Sass is good because it’s an abstraction; I think that Sass is good because it’s a well-designed abstraction. Crucially, it’s also easy to learn." But Sass wasn't always this well designed or easy to learn. The language has evolved considerably since its inception over 7 years ago. In this talk, Chris will talk about the process through which the Sass language is designed and how you can be an essential part of that process.
In a perfect world, we would all be able to design and build applications by simply following best practices; creating intuitive, beautiful interfaces would be as easy as implementing "10 Usability Heuristics" and using logic to fill in the gaps. But, it's never that simple, is it?
We tend to think of usability as a utopian 'middle ground' that serves the average user so well that we must always strive for it first. In reality, though, it's more like one corner of a triangle, accompanied by two very interesting psychological ideas: groupthink and authority.
Backed by data and studies, I'll show you how groupthink can alter the way your users think about and interact with your application—both for better and for worse (see: mob mentality). As well, we'll discuss the role that trust and authority play by looking at ways you can combat groupthink, and even use it to your advantage!
We can create better experiences by understanding the dynamics of our users' community—not just an individual user's persona.
Having recently made the transition from the world of art museums to the world of front-end development and design, I’ve learned that these two disciplines have more in common than one might think at first glance.
There’s lots of talk in our industry about craftsmanship, but I believe we should also strive to build a more artful web. We’ll cover how museums work, what is art anyway, authenticity and fear, the temporal nature of what we do, and learn a little bit of art history along the way.
As developers we have for all too long been developing solutions from the wrong perspective. Starting from the outside in reduces flexibility, kills reusability and typically paints a developer into a corner.
Then throw "It must look good on mobile too!"
SMACSS and BEM are good starts, but what is missing is the full strategy as how to break a design down to it's most basic parts and how to then built that up in a way that is maintainable and scalable.
This talk will cover the common mistakes developers and designers make when starting a new project. It will also cover the one of the more popular solutions for maintaing a scaleable Sass folder structure. and give insight as how to best build a project from the inside out.
GPU is a beast that we don't have much info about. I will talk about how browsers use GPU to render CSS animations, transforms and how you can choose wisely when you try to take advantage of them in CSS and common pitfalls.
LibSass is a new C/C++ implementation of Sass initiated by Hampton and developed by Aaron. Its design goals are efficiency, portability, and zero dependencies – as such, it runs much faster than the canonical Ruby implementation, and can be easily embedded into any platform that can interface with C/C++ or the commmand-line.
This talk will provide an overview of the LibSass implementation and how to use it, as well as a quasi-narrative of the various development hurdles – both technological and social – that arose, and how we overcame them.
If I say "UX," you probably think about personas, wireframes, and design dark patterns, but this talk isn't about that. This talk is about how your choices as developers make or break the user experience of an app.
We're not all lucky enough to have a team of copywriters and coding unicorn designers to help us make our site flawless. Luckily, we're not all as bad off as this error message floating around on Twitter:
"Are you sure you want to cancel this action? Click 'OK' to cancel the current action or 'Cancel' to continue."
Performance, language, clean, commented and modular code, semantics, interactivity, workflow, and testing are all pieces of the puzzle that is a delightful experience. Everyone who works on your site is responsible for the user experience. We'll discuss some real-world examples that you can do in your day to day job to make your app be all, I woke up like this.
\O/ w00t! You eat, breathe, love Sass. You have everyone at your company using it. You even write badass Compass extensions and the Internets luv u. And you've managed to do it all without being a Sasshole.
Yes, Sass is awesome. We love functions, mixins, writing less crappy CSS and finally getting to program as programmers do. What if I told you there's more to Sass than ridiculously easy media queries and harmonious typography? What if I told you that Sass' true power, its true prowess, isn't in its control directives or magical ampersand?
Sass is a visionary. This is a talk about the importance of vision(aries) in the context of creating a better web, better products, and a better world.
Are you worried that your style changes will break the current design in unexpected ways? Do you want to show a designer a page you've been working on, before and after your changes? Do you want to be able to quickly look back at how things looked a month or a year ago?
Modifying styles can be very scary. When was the last time you made one page sparkle only to have another page on the other side of the world unexpectedly break? We need better tools to manage this, and we think we've built one.
Diffux [dɪˈfjuːz] is a tool that generates and manages visual diffs of web pages so that you can easily see even the subtlest effects of your code modifications.
After this presentation, you will know how Diffux can save you time and prevent headaches by helping styling problems not affect your production website.
The web is littered with Ikea-style CSS frameworks and opinionated lowest-common-denominator web design tools. But pre-processors like Sass have opened the door for more flexible toolkits, and a thriving open-source community. You don't need to be a "ninja" with 3 million followers and your own clearfix to contribute. You don't even need a clever new idea — just a willingness to share, interact, and learn. Showing and sharing can help your code and your career.
We'll talk about the complete process of building and maintaining open-source Sass extensions. From concept to documentation, testing, licensing, releasing, and contributing to other projects.