Re: svn: /web/php/trunk/ images/shade.png include/header.inc include/layout.inc js/common.js js/jquery.hoverIntent.minified.js styles/structure.css
styles/theme.css
| From: | Stewart Lord | Date: | Wed, 29 Dec 2010 19:15:30 +0000 |
| Subject: | Re: svn: /web/php/trunk/ images/shade.png include/header.inc include/layout.inc js/common.js js/jquery.hoverIntent.minified.js styles/structure.css styles/theme.css |
||
| References: | 1 2 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-9949@lists.php.net to get a copy of this message | ||
On 2010-12-29, at 12:31 AM, Hannes Magnusson wrote:
> On Wed, Dec 29, 2010 at 08:25, Stewart Lord <stewartlord@php.net> wrote:
> I probably should have read the commit message before clicking on
> "Documentation".
> Hooooly.. you weren't kidding about the *high*impact lol :D
>
>
> I think these changes look great.
> I must admit though, I got a bit scared when I first hit the
> Documentation menu..
> Maybe the massive contrast is something you get used to.. lets see :D
>
> -Hannes
Haha, glad you like it.
I agree the documentation menu is massive. We could try to trim it down somehow. One idea I had is
to cap each section at around five entries and add a 'more...' link. The more link could
simply take the user to the parent category (e.g. 'Function Reference' or
'Security'. Or, it could expand in place if we wanted to get fancy.
Alternatively, if there is was some 'priority' information in the doc toc, we could css
hide items of lower priority.
Stew