From: Philippe Troin <phil@fifi.org>
To: justindorfman@gmail.com
Cc: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: Logo
Date: Fri, 12 Jul 2019 11:21:55 -0700 [thread overview]
Message-ID: <16e3d1cda40ac09f136a9bd2d0aa94cf2a9e89e9.camel@fifi.org> (raw)
In-Reply-To: <CAEjOAVpEMgo=_uTKpayDDDPGBzw=dB-=jLntXd8fXaSBZ3pnGg@mail.gmail.com>
Justin,
I'll throw in my 2 cents.
First thanks for the work, it looks great.
From all 10 icons in this round, my personal favorite is copy 3.
I like the subdued Z graphic, and the name of the project being clearly
visible.
If I had to change a couple of things, I would try:
* using lower case instead of small caps: this is the way I think most
people see the string "zsh" in their daily life.
* using italic, so that "zsh" slants the same way as the stylized Z,
giving a sense of forward motion.
* Maybe I'd try extending the bottom horizontal part of the stylized Z
and have the string "zsh" or "sh" rendered over this extended bottom
Z leg. Scuse' the ASCII graphics and wrong aspect ratio:
o---,
/
/ zsh
/
`--------------o
This is what I don't like about some other logos:
* For logos 6-10, I don't really see "zsh" initially, just "sh". It
takes an extra step to think about or see "zsh" in the logo. Maybe
making the stylized Z smaller would help here.
* I think number 4 is too dark/heavy.
* I don't like the font on number 5, just a personal taste.
* I don't like the bottom vertical alignment on number 2, it doesn't
feel natural.
* In number 1, I think that "zsh" all lower-case would work better
than the initialed "Zsh", see first bullet above for the rationale.
Thank you again for the great looking logos!
Phil.
On Thu, 2019-07-11 at 19:45 -0700, Justin Dorfman wrote:
> Hey Everyone,
>
> I gave our designer the feedback and this is what he came back with
> https://cl.ly/aca8f4c2ecab
>
> I think the icons are great, but the wordmarks need work. I've been
> playing
> with different fonts and I'm just not happy yet
> https://cl.ly/b92d660678b9
>
> Look forward to your feedback.
>
>
> Regards,
>
> Justin Dorfman
> @jdorfman <http://www.twitter.com/jdorfman>
>
>
> On Tue, Jul 2, 2019 at 9:55 AM Sebastian Gniazdowski <
> sgniazdowski@gmail.com>
> wrote:
>
> > On Fri, 28 Jun 2019 at 12:13, Stephane Chazelas
> > <stephane.chazelas@gmail.com> wrote:
> > > 2019-06-27 16:20:31 -0700, Bart Schaefer:
> > > [...]
> > > > Now that you mention it, I'm curious how orange and black got
> > > > chosen
> > > > in the first place? Is it because zsh was invented at
> > > > Princeton?
> > > [...]
> > >
> > > Sorry for throwing a completely unrelated idea late to the
> > > party, but when the idea of a new zsh logo was first mentioned,
> > > one thing that came to my mind was a "ZSH" made with multicolor
> > > lego bricks to reflect the multi-faced, modular nature of zsh
> > > (and it can be shaped any way you want; playdough would also
> > > work there I guess).
> > >
> > > Maybe not the best image for a shell as lego bricks may convey
> > > some "building" meaning which do not as directly apply to a
> > > shell as to other tools.
> >
> > I would agree that the lego bricks convey the 'building" meaning,
> > which to me appears as a "free your mind" sense, which if shared
> > among
> > other people would be an useful one for Zsh as the message to
> > convey
> > about itself.
> >
> >
> > --
> > Sebastian Gniazdowski
> > News: https://twitter.com/ZdharmaI
> > IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
> > Blog: http://zdharma.org
> >
next prev parent reply other threads:[~2019-07-12 18:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 23:37 Logo Justin Dorfman
2019-06-04 23:56 ` Logo Jérémie Roquet
2019-06-05 0:09 ` Logo Justin Dorfman
2019-06-05 0:13 ` Logo Andrew J. Rech
2019-06-05 0:43 ` Logo Justin Dorfman
2019-06-05 7:56 ` Logo Oliver Kiddle
2019-06-05 15:52 ` Logo Bart Schaefer
2019-06-05 16:50 ` Logo Justin Dorfman
2019-06-06 20:12 ` Logo Peter Stephenson
2019-06-07 0:26 ` Logo Justin Dorfman
2019-06-14 20:55 ` Logo Justin Dorfman
2019-06-15 9:39 ` Logo Jérémie Roquet
2019-06-27 17:13 ` Logo Justin Dorfman
2019-06-27 20:23 ` Logo Bart Schaefer
2019-06-27 20:34 ` Logo Bart Schaefer
2019-06-27 21:13 ` Logo Sebastian Gniazdowski
2019-06-27 21:35 ` Logo Bart Schaefer
2019-06-27 22:51 ` Logo Oliver Kiddle
2019-06-27 23:20 ` Logo Bart Schaefer
2019-06-28 10:12 ` Logo Stephane Chazelas
2019-06-28 19:58 ` Logo Justin Dorfman
2019-07-02 16:54 ` Logo Sebastian Gniazdowski
2019-07-12 2:45 ` Logo Justin Dorfman
2019-07-12 18:21 ` Philippe Troin [this message]
2019-07-12 18:46 ` Logo Bart Schaefer
2019-07-13 12:01 ` Logo Oliver Kiddle
2019-07-15 21:07 ` Logo Justin Dorfman
2019-07-15 21:30 ` Logo Bart Schaefer
2019-07-16 9:55 ` Logo Daniel Shahaf
2019-07-16 10:05 ` Logo Daniel Shahaf
2019-07-19 20:15 ` Logo Justin Dorfman
2019-07-19 21:07 ` Logo Daniel Shahaf
2019-07-19 21:14 ` Logo Bart Schaefer
2019-07-19 21:17 ` Logo Bart Schaefer
2019-07-19 21:30 ` Logo Daniel Shahaf
2019-07-19 21:33 ` Logo Bart Schaefer
2019-07-20 8:58 ` Logo Oliver Kiddle
2019-07-15 20:56 ` Logo Justin Dorfman
2019-07-12 19:12 ` Logo Sebastian Gniazdowski
2019-07-13 12:33 ` Logo Sebastian Gniazdowski
2019-07-13 13:09 ` Logo Bart Schaefer
[not found] ` <CAEjOAVooT9+U8Cp4FrU7Qo95-AzzyFuF-XxDMGFVWuCC5z-7Qg@mail.gmail.com>
2019-06-27 21:38 ` Logo Jérémie Roquet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16e3d1cda40ac09f136a9bd2d0aa94cf2a9e89e9.camel@fifi.org \
--to=phil@fifi.org \
--cc=justindorfman@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).