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

On Dec 29, 2010, at 11:15 AM, Stewart Lord wrote: > 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. People choose Documentation because they desire documentation, so I don't see a problem with it being large although I've not tested it with different screen dimensions. However, I do think we need to make it easier to find extensions. Currently we have "Function Reference" which categorizes extensions, but this isn't perfect nor can it be. I'm not suggesting we simply throw the alphabetical listing in there, but somehow we need to make it easier to find/search extensions alphabetically. Regards, Philip