Designer News
Where the design community meets.
UX/UI Designer Joined almost 10 years ago
Ean hasn't posted any stories yet.
First off: Why?
So I guess my question is: why not use the better-known Git logo popularized by git-scm? It's licensed under Creative Commons allowing unrestricted re-use and derivative works with credit. If you want to improve tooling, you could just adapt his logo and make a better website to hold it.
Which brings me to...
Licensing?
Your logo doesn't have any explicit license listed, so I can't risk using it elsewhere without asking your permission.
Do you intend to license it under a more permissive license? Which one?
How do you intend to deal with people who make/use similar-but-derivative versions and dilute the brand?
Design
It feels like there's a disjoint between the logo and the font: you've gone very geometric on the logo with very uniform widths and angles, but your font uses odd angles and tapered widths. The dot on that i
in particular is bugging me, it's such a great chance to repeat the square-diamond shape from the logo.
You may want to look at some more geometric base fonts, or go much further away from geometric/digital designs if you want to go that route.
Inevitable comparison to git-scm logo
By contrast with the git-scm version that illustrates the nodes it feels much more generic, I feel like those are a big part of communicating the concepts going on if you're going that route. It's also very similar to that logo. They'd have a solid case to make that you're failing to provide proper attribution in your derivative work of their logo.
When scrolling to the top the inertial bounce often reveals the white <body>
element which is distracting.
This can sometimes be avoided by making the body dark, or by extending the header 50-100px above the top of the page (negative margin) but not on all browsers/OSs.
Some just render a white background no matter what as a shortcut and there's no fixing it.
Could you do this using Github? Make your templates folder into a repo, check in any items you changed and want your team to use, remind them to get latest regularly.
If people aren't super comfortable with command-line you could use something like Sourcetree that makes it a bit more GUI.
Leuchtturm 1917, Dots (layout/UX) and Plain (Illustration)
Really nice paper, comes in a variety of attractive colors, plus a bunch of nice little details.
Includes a folder/pocket in the back and a set of sticker labels in case you have more than one and need to tell them apart or when you archive it. Pages are numbered and the front includes a table of contents if you want to record the position of something particularly important. All the numbers/dots/lines/whatever are printed in a nice medium gray instead of black.
http://www.amazon.com/Leuchtturm-Medium-Notebook-inches-LBL13/dp/B002CV9BBE
Casual but neat. Lots of T-shirts, jeans, polo shirts for the guys. Casual blouses and T-shirts and skirts or jeans for ladies. Hoodies and jackets are popular in the winter. Shorts and sundresses abound in the summer. Flip flops are acceptable.
Okay, so you can make this work for you. The key is that you have to insist you be involved in the design meetings: call in if you have to. If the boss objects, say "So I can be sure to really understand the suggestions being made, and get a chance to ask the right questions while ideas are still fresh." Make it about increasing your utility and value.
Your best friend in these discussions is the question: "Why?"
Whenever someone suggests something that seems off, ask them why. Make them explain the idea. Compare it to their goals, delay if you need to do research. Talk in terms of tradeoffs instead of "good vs. bad". They might be totally crazy, or they might understand their customers in a way you don't.
When suggestions come up, control the situation. When there are good ideas, embrace them. When they have neat ideas that aren't practical, challenge them to find a way to accomplish the same thing under real-world constraints. Offer to work with them because their idea is good. Treat them like smart problem-solving people.
If you treat them as smart and engage them, they'll actually contribute value. If you treat them as dumb, you'll have to fight them.
Yeah, agreed on that. There are things you just don't want to have to speak aloud, or have broadcast to everyone within earshot.
Plus how much more annoying would cell phones be in social situations if they spoke up and interrupted your conversation instead of vibrating in your pocket everytime someone posted an update on Twitter?
I personally think the idea of no UI is a bit weird, because interfacing with various UIs is basically all we do:
To me, the real goal is to make an interface so simple, rewarding and and beautiful that it is a desirable experience in itself. If that can be achieved, it puts your work in the same realm as drawing a picture, having a good conversation, or reading a favorite book.
You wouldn't avoid those interfaces if you could, and that's what truly great UI should strive for.
So in your analogy: I want to make the bridge so well that you take the long way home just so you can walk across it and enjoy the view.
So my initial reaction when I hit your page was "Where is his work?"
It seems odd to hit me with a landing page that doesn't give my anything to really look at, and where the primary buttons seem to be Email and Resume. By the same token, when I get to the end of your portfolio there's no easy action I can take to contact you: I have to go back to the Info page first.
Seems like it'd be nice to just load people right onto your work page, and include the Email and Resume links in your header, with maybe some redundant buttons for those elements at the bottom of your portfolio for the sake of flow?
I mean, that's why I'm at your portfolio: I want to see your work. AFTER I look at your work, I might feel the need to check your resume and contact you.
Your work is great, btw, and I love the site design as a whole.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
I don't think they need to every day. But I'd very much like to hope my architect could lay bricks, and my chef has bussed a table.