Re: Site Structure: Header

From: Date: Wed, 21 Oct 2009 20:15:45 +0000
Subject: Re: Site Structure: Header
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.webmaster 
Request: Send a blank email to php-webmaster+get-6247@lists.php.net to get a copy of this message
On Tue, Oct 20, 2009 at 11:06, Burka Daniel <daniel@silverorange.com> wrote: > Further to the discussion about the site structure, I've jumped into > html/css and mocked up a potential header for subpages on the site. I've > been thinking we'd do a similar but different header on the homepage of > PHP.net and then have a consistent and very compact header for all other > pages. > > http://www.whitelands.com/daniel/php/mock1/ > > Notes: > > 1) Header is very compact. Much smaller and less intrusive than the current > PHP.net header. It looks like you are aiming for a fixed width? I find it very annoying when pages only take 1/3 of my screen width.. :( > > 2) Primary links are reduced from 12 to 6. Much easier to scan/parse than > before. > > 3) But... I'm using mega-dropdowns** under two of the menu items. This > allows very quick access to most parts of the documentation and many of the > sections that I've lumped under 'Community'. This could be a nice balance.... > reduce the number of menu items at the same time as giving more ready access > to more areas of the site. Great way to have bunch of links without taking space from the real content, I like it. The only problem with it is I cant do text search on the page of the links without mousing over it first.. I think thats an acceptable drawback though. And combined with the search suggestion Stewart mentioned in another thread, I think it could be very cool. > >     a) I'm really not sure 'Community' is a good name for this. I like the way we can inject sublinks, like for the "Get involved", the bugtracker link can definitely be there, and even the wiki. > 5) Small, compact, simple logo treatment can work at very small sizes. It is very unlikely that we can change the logo, and I think most of the devs would be very much against it. -Hannes

« previous php.webmaster (#6247) next »