Be nice. Or else.
Los Angeles Senior Design Engineer at Noun Project Joined about 5 years ago via an invitation from Hiroaki Y.
The homepage redesign allowed us to direct people in a better way to the parts of the platform people used most (search and collections). We are continuing research on how people use this navigation and will be making improvements as we learn more. But for now we wanted to keep it simple and expandable.
I'm curious, where did you go in the main navigation after "accidentally" finding it. And if you are interested in participating more in our research, please seek me out individually. :D
We are really interested in solving problems that designers have, so researching those problems is a key part of our process.
I'd love to learn about other use cases you may have, and other content types that are important to you. Email me if you would like to participate in our research. :P
Thanks for the question,
I feel that when working with visuals, the file is much less important than the content contained within that file. Obviously Lingo has only just started building our platform, but each visual is much more powerful than a single file.
Content modifiers, such as alternative image cuts, will make those visuals even more powerful. Hopefully replacing the need for duplicates and nesting folders. The idea is when you see the visual you need, you just grab it. It shouldn't matter what application you are using. We found most design teams use a handful of apps. Instead of redefining each designer's workflow, we would build a product that works within how you are comfortable working.
The current supported visuals ( .png, .svg, pdf, etc ) is just the beginning we are already working on expanding that into many other content types. But most importantly it's not so much about the file, but about how you use that content. ( especially with teams! )
I'm a big fan of building micro branding sites full of components, but we all know that maintaining any of those systems is a full time job. Most don't even get the time or resources they deserve. Lingo may not be the center of your brand yet, but it will empower everyone on your team to use the visual content, and it's really easy to start using and maintain.
Now that the platform has been created, the evolution and capabilities of Lingo will move quickly. :)
I'll be checking in throughout the rest of the day, feel free to post any questions you may have. :)
Oh great! I'm excited to meet you.
For those in Los Angeles, join us here
Absolutely! Currently the way apps handle PDF is varied. Luckily with a team like Sketch, they iterate quickly. Hopefully they will focus on how vector content is copied in and copied out more closely.
We have sent them suggestions, and they have already addressed a bunch of importing aspects. PDF is just one way to distribute vector content between apps.
To help any app best support those situations, I suggest sending any oddities you find to our support and we can look at them and address them individually. It also helps to send information to Sketch or whichever app you are using so their engineers can address any problems you may have. Formats like PDF are complex and depending on which app they were created in, what features you used, and even what settings were enabled create much different files.
Hopefully one day we have a better standard, but for now we look for ways to make Lingo as universal and capable as possible.
Simple.Honest.Work. lives on for me as a methodology and mantra in my work. Our team here echoes that too. It's really about making things simple, keeping them honest, and just putting in some good hard work.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.