It’s that time of year again: graduation, when students transition away from the classroom to what will hopefully be a long and successful career in their chosen industry. I recently said goodbye to some of my own website design and development students. Instead of teaching lessons in design principles or responsive websites, I spent our final evening together answering their questions. One of those questions was, “What is the best career advice you’ve ever received?”
At the time, I didn’t have an answer. I could think of many instances when someone helped me solve a particularly complex design challenge or a complex CSS issue or helped me navigate a delicate client situation, but I wouldn’t consider those “best career advice” moments. After thinking about it for a week or so, I came up with four pieces of advice that I received early in my career and that were invaluable to me as I was getting started in this industry but that are just as relevant and useful to me today.
Z-index is an inherently tricky thing, and maintaining z-index order in a complex layout is notoriously difficult. With different stacking orders and contexts, keeping track of them as their numbers increase can be hard — and once they start to spread across CSS files, forget about it! Because z-index can make or break a UI element’s visibility and usability, keeping your website’s UI in working order can be a delicate balance.
Optimizing your website assets and testing your design across different browsers is certainly not the most fun part of the design process. Luckily, it consists of repetitive tasks that can be automated with the right tools to improve your efficiency.
When interacting with mobile devices, users have little patience for confusing interfaces or unnecessary steps that impede their progress. As designers, we must understand the role of momentum in effective user interface design and create experiences that keep our users moving forward.
Think about the act of checking email on a mobile device. This is probably one of our most efficient interactions with our phones; we do it while crossing the street, between conversations and even (for the dangerous few!) while driving. Every distracting bit of user interface (UI) that could get in the way of checking our email has been stripped from the design, making it a streamlined process that we love doing.
This year has brought a number of changes in the conference scene around the world. Quite a few established conferences have taken their last bow, and a whole bunch of new conferences have appeared — and I'm not just talking about the Smashing conferences! There's even a conference for developing applications of the not-yet-released Google Glass.
Many exciting conferences have already featured some of the industry's most illustrious speakers in the first half of 2014, however, there are quite a few more to come! Take a look at today's round-up of conferences taking place this year from June onwards, and remember, since most events are a bit light on the design aspect, it may be a good idea to visit those conferences that focus specifically on visual and artistic technologies.
To help you tap the full potential of Marionette, we've prepared an entire eBook full of useful hands-on examples which is also available in the Smashing Library. — Ed.
In this series on Backbone.Marionette, we’ve already discussed Application and Module. This time, we’ll be taking a gander at how Marionette helps make views better in Backbone. Marionette extends the base View class from Backbone to give us more built-in functionality, to eliminate most of the boilerplate code and to convert all of the common code down to configuration.
I highly recommend that you go back and read the articles about Application and Module first, if you haven’t already. Some things may be mentioned in this article that refer to the previous articles, and this is part of a series about Marionette, so if you wish to learn about Marionette, you should read the whole series.
Fireworks extensions are of two main types: commands and command panels. If you find yourself repeatedly performing a tedious task, you could write a command to automate the process and save yourself a lot of time. Alternatively, if you are missing a particular feature that would improve your workflow, you could write a more complex extension — a command panel — to implement it.