Speeches given on the first day of the Smashing Conference 2014 in Freiburg were once again very interesting and instructive.
Marcin spoke about designing and then understanding the perfect underline.
Finding the perfect underline
"The perfect underline should be visible, but unobtrusive - allowing people to realize what's clickable, but without drawing too much attention to itself. It should be positioned at just the right distance from the text, sitting comfortably behind it for when descenders want to occupy the same space."
Where things get complicated
"Figuring out how to position one underline perfectly and test it on major browsers seemed like a nice, fast evening project."
And then, it happens
"There's something anticlimactic about finishing a long code review. There are no fireworks, no champagne; GitHub doesn't change the UI in any celebratory way to highlight your achievement. After 31 days of discussions, trials and errors, and trying many approaches, both of my great reviewers sent the magic four letters: LGTM."
It is difficult for a 12 column grid to function when you have to optimize it for so many different device-widths. It is better to have a simple grid, even for complex modules.
Design consistency is not about pixels, design consistency is about purpose.
"Responsive Webdesign is more than fitting stuff on screens." - Patty Toland
Responsive web design speed problems:
The second day on the conference was also very inspiring. This year also featured a mystery speaker.
I was honored to be present and listen to Dave Shea. Dave Shea is a Canadian web designer and co-author of The Zen of CSS Design: Visual Enlightenment for the Web.
Dave spoke about a CSS architecture system called Argon. A bloated code base was the problem, whereas the solution was the development of a CSS architecture system. The main principles of Argon are:
Instead of planning pages, now we're asking stakeholders to prioritize and manage a million bits of modular content.
So how do we keep our subject-matter experts from feeling overwhelmed, prevent carousel-obsessed executives from endless homepage arguments, and get the content we need to make design and development decisions?
The answer is in using content strategy as a means to orchestrate, not dictate.
Content on mobile should not be simply adapted only in design to the resolution, but may also be reconsidered. Maybe it makes sense to divide the content into individual chunks.
Content planning has already happened at the beginning of the project and the designer and developer should be involved in it.
Limit time and give workshop participants a form to answer important questions:
Try to be the best and to learn continuously, but the balance with family and leisure time is important.
Sladjana possesses unique talents in regards to style and aesthetic that cast her as a natural in the role of a front-end developer.