Re: pear.php.net look and feel

Hey thanks Jani! So; HTML and CSS work, specifically on pear.php.net. One big problem is http://pear.php.net/ and http://pear2.php.net/ are at the moment completely apart. There are no/few links between the two, no common content, no hints. If you are design inclined, I would suggest thinking about a small textual enticement towards pear2 for the upper right hand side of the sidebar on pear.php.net. It should fit in with the current pearweb design; but also be just different enough to be easily noticable. Wording could be along the lines of "Find out about the next version of PEAR". The second half of this would be improvements to the current pear2.php.netindex page. Right now it has one goal in life - get you to install pyrus quickly; with the assumption that you already know what it is; why you want it; etc. Think about how you can retain the "install pyrus" instructions, so it's dead simple to do so; *while explaining what it is and why it's great*. I would suggest something along the lines of *Pyrus is the next version of the PEAR installer - more advanced, built from the ground up for PHP 5.3, with the aim of bringing you a robust suite of libraries suited for your PHP 5 needs. *I'm sure others on this list could also chip in with a good elevator pitch :) The third half, because I like having 150% of anything, would be adding pyrus installation instructions under pear installation instructions - http://pear.php.net/package/DBA/download ... but only if the package is compatible. That means: PHP 5 as a package dependency, and package 2.0 (ie: no flashing horrible deprecated warning). Finally; for extra bonus points - Take the package homepages, and think about ways to make pyrus compatibility more obvious. IE: http://pear.php.net/package/HTTP_Request2 - should be just fine to install with pyrus. http://pear.php.net/package/Inline_C - is icky, old, and incompatible - pyrus turns its nose up at it. Let me know if any of these are of interest to you. Re: > I might suggest a request app. All developers should have a vote of what > could/should be the next release/package. It might work :) > We've already got something a bit similar in http://pear.php.net/pepr/ ; which works pretty well. If you wanted to look at ways to make it more user friendly or enticing; *while explaining we <3 unit test coverage and clean code*; that would be awesome. Or if you've got very different ideas on how this presents to users (ie: front page links again); those are welcome too :)