Design a letter-based favicon like most big tech companies, or be playful and create an emoji-based favicon. Modern browsers supports SVG favicon. Be creative.
Open source, experimental, and tiny tools roundup
---
This is a list of smaller tools that might be useful in building your game/website/interactive project. Although I’ve mostly also included ‘standards’, this list has a focus on artful tools & toys that are as fun to use as they are functional.
The goal of this list is to enable making entirely outside of closed production ecosystems or walled software gardens.
Open Peeps is a hand-drawn illustration library to create scenes of people. You can use them in product illustration, marketing, comics, product states, user flows, personas, storyboarding, quinceañera invitations, or whatever you want! ⠀
Dave Klein: Interview with Paul Irish, HTML5 expert and community leader (Inspire Magazine)
I think it’s important to publish what you learn. There’s really no school for front-end development. You can’t go to a university for a JavaScript degree or a class about how browsers work. Most of us learn from blogs and Twitter. Early in my career, I learned a bunch of things whenever I worked on a project, but I never told other people about them. So my general advice is to publish what you learn, share with the community, and collaborate on projects that help move the community forward.
Mule Design Studio’s Blog: Presenting Design Like You Get Paid For It
How to present and sell design: 1) Don't wing it — postpone until you're ready. 2) Really sell your design — the idea that 'good design speaks for itself' is a myth. 3) Don't get subjective or allow your feelings to get hurt — tell them to tell you when it doesn't work. 4) Don't embarrass the client — make them look good, be honest, listen to them.
This may be worth looking into. I waffle on whether this sort of thing is ultimately a good decision — you're relying on someone else's framework, it takes a while to learn and master, and once you decide to go with it you're essentially stuck with it. But isn't that the case with any pseudo-framework developed for a website design? I should test this on a little project.
Particletree: Reflections of an Interface Designer
Some rather obvious reflections, but valuable all the same -- the continued appearance of articles like this shows how important these lessons are. On the volatility of web apps, designers, the relationship thereof, and how important the user is.
On starting over. "It's better to have something we're both proud off than to try and salvage the work done so far. Sometimes you have to go all the way through the design process before you realize that you've built the wrong thing."
"The need for these distinctions becomes moot, of course, when no secondary actions are present. Make sure you really need each secondary action on a form and don’t add them indiscriminately."