If you are a designer in open source: What do you wish you learned earlier about being a designer in open source? //jd
If you are a designer in open source: What do you wish you learned earlier about being a designer in open source? //jd
@opensourcedesign It is more of a general thing, mostly boiling down to inherent power dynamics, the inequality that comes with the fact that designers are two steps more separated from any decision making compared to coders.
It is the fact that you have to rely on a projects ability to handle that whole design/code thing in a productive manner. Projects rarely are equipped to do that.
1/2
@opensourcedesign So the separation is: Opposed to a coder experience you can't just offer a contribution through a merge request.
There are no designers for review, no guidelines or rules, nor designers in general β but there are lots of voices and opinions.
What ironically adds to the separation is a perceived "equality", in the sense of "always appreciating all kinds of contributions" β ignoring the facts above and the reality that designers don't use git, β¦
2/2
Explaining which parts of a mockup are placeholders and which parts are the intended design.
It drives me crazy when I post a mockup intended to show some element such as the layout, to have developers knock back the whole concept based on some detail that wasn't even intended to be kept in the final version, such as the color scheme, or placeholder text.
"No, I'm not actually suggesting that lorum ipsum be your new slogan..."
I find that often early drafts that are intended to indicate possible directions of further development, get axed because they don't look polished yet, but spending time on polishing the wrong concept is fundamentally a waste of time.