Logo per project?

[David Blevins]

I know there’s a whole bunch of work going on for potential new logos.  Wanted to throw something out.  It’s inherently hard to scale, but IMO is worth it.

For the project pages in tomitribe.io we basically made a logo style, such that many project logos could be created:

  - https://tomitribe.io/projects

I know from a marketing perspective the standard view is “gee that’s hard, we couldn’t create one for every project, it’s not worth it”

Pragmatically, we wouldn’t need to do them for all repos.  Just when something gets really cool and we want it to stand out.  A reward or sign of achievement.

From a developer perspective, it’s one of those things we can’t do.  Completely out of reach for 98% of anyone with a coding brain.  As a result when our little repo and piece of code gets a neat little logo and piece of identity, it’s an indescribable thrill and sense of pride.  It truly fosters creativity and emotional attachment and even though we may have written 80% of the code it now feels “more real” and legitimate.

I’m curious if I’m totally alone in such perceptions or if other developers have had similar thrills when a unique logo gets applied to their code.

-- 

David Blevins

http://twitter.com/dblevins
http://www.tomitribe.com

310-633-3852

[Mike Croft]

Sounds like a great idea. It looks great for tomitribe.io too, although they're all different projects, there's a lot of cohesion there and it's obvious that it's all coming from the same brand.

One thing we could do is pick up on one of the logo redesign ideas, which was to create a slightly modified font - using that font with a consistent colour palette seems like a good low-effort way to keep things nice and uniform :-) 

[Kevin Sutter]

As long as we don't have to include marketing in the decision process...  Sorry, not trying to be snide.  But, looking at the long process to get a modified logo approved for MicroProfile, I would hate to have to go through the same process for each component.  But, having a separate "badge" for each component looks kind of cool.  And, as long as we are consistent with the colors and fonts of our approved MP logo, then we could allow each component to come up with their own "badge".  I like the idea.

--  Kevin

[Mark Little]

+1 in general and +1 on your “As long as …” comment ;)

--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/73bca622-054f-439a-bd99-58db793448c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

---

Mark Little

mli...@redhat.com

JBoss, by Red Hat

Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork.
Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873
Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA)

[Emily Jiang]

I second the idea. Logo or no logo should be optional.
Emily

[Heiko Rupp]

Am Freitag, 16. Juni 2017 00:57:20 UTC+2 schrieb David Blevins:

I know there’s a whole bunch of work going on for potential new logos.  Wanted to throw something out.  It’s inherently hard to scale, but IMO is worth it.

For the project pages in tomitribe.io we basically made a logo style, such that many project logos could be created:

I think it could be good to go a slightly different route and always use the same base logo (like the MP one) and then add/modify it.

While on the tomitribe page it is obvious that they follow the same style, I am not sure if people can recognise the style as being tomitribe when they see one logo alone on a random page

 

[John Clingan]

I'm mixed on Heiko's idea. As a young project needing recognition, and to support his point, I like the idea of putting effort behind a recognizable pattern to drive MicroProfile awareness.  On the other hand, I think that would break brand guidelines (linking back to the "I would rather ..." comment :-) ).

Perhaps a middle ground is to have project logos share the brand guideline one, two, and for color palettes and badge L&F.

[csaa...@redhat.com]

Another idea would be to make the logo for each sub-project be the MicroProfile logo (soon to be revamped) with the name of the sub-project next to it or right under it in the same style as the logo but in smaller font.

[John Clingan]

That’s not bad.

--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/817dddc9-fe57-4fa9-bb57-08a768348daa%40googlegroups.com.

[Heiko Rupp]

Am Freitag, 23. Juni 2017 02:22:55 UTC+2 schrieb csaa...@redhat.com:

Another idea would be to make the logo for each sub-project be the MicroProfile logo (soon to be revamped) with the name of the sub-project next to it or right under it in the same style as the logo but in smaller font.

Yes, that sounds good (and is somewhat what I had in mind )