Where the design community meets.
Director of UX @ GravityFree, Product Designer Joined over 5 years ago
I'm surprised by the harsh comments on this. I mean I get it, not everyone starts designing from a notebook, but that doesn't invalidate the fact that many designers use notebooks to architect and work up their designs before taking them to the screen. I was a Moleskine user for over a decade, $15 notebooks for 70 pages. When Baron Fig came along they were almost 200 pages for $18 and they had thick hardcovers that last forever. While the Show & Tell notebook doesn't specifically fit my taste, they do make some great notebooks and their dot grid is great for interface design.
Love the work you all have been doing! Congratulations on the release. I love the decisions you've made with the utility classes and the general direction. I'm curious though, I've noticed the XL grid max width is 1140 compared to the LG grid max width from 3.x that was 1170. I'm curious of the reasoning, if there is one, for the thinner width grid.
Haha. I never really thought about the SEO of that article to be honest. It was really just me documenting something I was working on for myself because I found myself always looking up the syntax for media queries. People just kind of ran with it and it's been included in several Sass projects since. But I definitely appreciate all the shout outs and e-high fives. I'm just glad it helped inspire your reworked example. Keep up the great work.
Thanks so much Dillon! Glad it helped you.
Though I will say, the responsive mixin within your docs and code is exactly the code from my blog post on Creating a Dead Simple Sass Mixin to Handle Responsive Breakpoints. I'm glad that code was able to help you, it might be nice to have a link on the docs page and a code comment in the file to credit the concept.
I've been seriously considering making the change too. So you can sync and activate any folder of fonts just like with RightFont? Anything else you love more about FontBase aside from the price?
I think it's really going to depend on the type of product you have. Whether it's an internal product or a customer facing product. I like to ask about scenarios regarding the product... things that start with "tell me about a time when [you did]..." to get them thinking about how they use the product. Sometimes just asking "is there an area where you struggle using the application?" can be helpful. It's also going to depend on what you're trying to learn. Are you trying to improve registrations and onboarding for new users? Then you might want to specifically talk to a group of new users and get them talking about what was going on for them when they decided to start using your product.
So it really does depend. However, just be sure to be a good listener, don't try to explain or solve there problems during the conversation... like, "oh you just need to go to this screen and click on this." Don't do that. Just note it down.
There are a lot of great books out there that address similar issues. You might consider checking out "Just Enough Research" and "Validating Product Ideas."
Definitely not a silly question. These are common questions that everyone thinks about when trying to learn more about their users.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.