[boost] Re: Front page... with new logo.

From: David Abrahams (dave_at_[hidden])
Date: 2004-11-21 11:16:40

Rene Rivera <grafik.list_at_[hidden]> writes:

> http://redshift-software.com/~grafik/boost/index.htm
> Boost C++ Libraries
>
> Hopefully all the bugs are worked out at this point :-)

The problem is that nothing can definitely be called a bug.  This is
a highly subjective process and different ideas will work for
different people.

Thank you for adjusting the text size; it really does look much
better in my extremely common browser.

> About the logo... In keeping with the style it's simple; 

I know you put a great deal of effort into this, but IMO it's too
complicated.  Even though the first one was indeed too Borland-like,
as a logo it functioned much better: it was simple, recognizable, and
impactful.

I also think the left column has become too complicated.  I do like
the dark background, but the dotted lines seem to have multiplied.
Compare with http://luabind.sourceforge.net/boost.png.  The light,
colored section headers don't speak as clearly as those in
http://luabind.sourceforge.net/boost.png (I prefer black but can live
with dark blue -- we chose black for the new Boost docs stylesheet),
and putting them below the dotted line seems "needlessly innovative."
I understand that there may be some logic in it, but people are used
to seeing

    Name of Section                                       XX
    .........................................................

The dashed line acts like an underline, which is logical, and is
reminiscent of a table of contents.

> it's only based on text outlines.  Components are:
>
>      * Solid "Boost" with surrounding template "<>" in outline form.

There is no obvious reason to me that the surrounding "<>" ought to
have a different style from the "Boost" it contains.  A similar
argument goes for "{C++}".  It's also not obvious that those are meant
to be template brackets; they could be #include brackets.

>
>      * The slight perspective shadow of that, with the "{C++}" as part
>        of the shadow.

> The hope is to invoke STL, templates, libraries, and C++. 

IMO it's trying too hard.  My advice: don't try to evoke so many
things.  Say one thing and say it clearly.

One idea that we might start with is enclosed



What that's meant to evoke should be pretty obvious ;-)

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com