From: Petr Baudis <pasky@suse.cz>
To: David Baldwin <baldwindavid@gmail.com>
Cc: git@vger.kernel.org
Subject: Git Branding Overview, Re: Git.or.cz Experimental Design
Date: Fri, 18 Jul 2008 12:39:18 +0200 [thread overview]
Message-ID: <20080718103918.GO10151@machine.or.cz> (raw)
In-Reply-To: <5fb1d2400807022011w7f8d79dbk68a64dc1b8b01d98@mail.gmail.com>
Hi,
On Wed, Jul 02, 2008 at 11:11:02PM -0400, David Baldwin wrote:
> Hello Petr:
> I hope you are doing well. I was looking at the git.or.cz site tonight and
> thought it could perhaps use a little freshening up from a design
> standpoint. Therefore, I messed around with the default stylesheet and the
> home page a bit and made a logo. You can take a look at the experimental
> design at this address...
> http://baldwindev.com/git.or.cz/
>
> It's really just a few little changes. If you're interested in implementing
> any of this into the current site, feel free to grab the changes from my
> github git repository. You can see the few text changes in the diff...
> http://github.com/bilson/gitorcz_redesign/tree/master
I'm not sure if this is really an improvement on the current state,
but then again, the current state pretty much matches my idea and maybe
others will agree that your proposal is better. Thus, it's better to
show this to the Git community at large. :-)
If you or anyone is shooting for a re-design, I would suggest to
somehow relate to the current "Git brandings" in use:
http://git.or.cz/git-logo.png
http://henrik.nyh.se/uploads/git-logo.png
If you think you have a cooler logo, that's fine too, but then it's
again better to present it explicitly, I believe. The latter is used
especially within mSysGit, the former is used more widely - at the
current homepage, as Gitweb logo, and in various modifications like
http://git.nyh.se/git-favicon.png
http://members.cox.net/junkio/git.png
http://unfuddle.com/images/screens/source.big.jpg
(top left ;)
--
Petr "Pasky" Baudis
GNU, n. An animal of South Africa, which in its domesticated state
resembles a horse, a buffalo and a stag. In its wild condition it is
something like a thunderbolt, an earthquake and a cyclone. -- A. Pierce
next parent reply other threads:[~2008-07-18 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fb1d2400807022011w7f8d79dbk68a64dc1b8b01d98@mail.gmail.com>
2008-07-18 10:39 ` Petr Baudis [this message]
2008-07-20 21:21 ` Git Branding Overview, Re: Git.or.cz Experimental Design Matt Graham
2008-07-20 21:44 ` Jakub Narebski
2008-07-20 22:36 ` Petr Baudis
2008-07-20 21:50 ` Martin Langhoff
2008-07-21 10:59 ` Michael J Gruber
2008-07-21 11:20 ` Johannes Schindelin
2008-07-21 12:20 ` Michael J Gruber
2008-07-21 17:23 ` Jakub Narebski
2008-07-21 20:03 ` Matt Graham
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=20080718103918.GO10151@machine.or.cz \
--to=pasky@suse.cz \
--cc=baldwindavid@gmail.com \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.