Re: pear.php.net look and feel & how do we move towards pear2

Nice. For team: As a noob (to PEAR) what I find most confusing is how scattered the PEAR2 docs are, and the fact that the status of PEAR2 is not clear. For example: - Yesterday someone was sent to wiki.pear.net for information one pear2 directory structure - This demo page references pear2.php.net, but that site actually has very little information past installing - Much of the pear2 documentation is included in the middle of pear1 documentation. - It was never clear to me what the relationship between PEAR2 and Pyrus is: is PEAR2=Pyrus? Does one use the pyrus command instead of the pear command, but they both point to the PEAR1 repository? - What is the status of pyrus? Should I always use it instead of pear? Are there some packages I can only get by using pear? pyrus? - What is the status of PEAR2? Is it the new standard? when do I use PEAR versus PEAR2? Is PEAR obsolete? I have found answers to these questions for myself (sort of, except for the 'now where did I see that documentation'), but if we are selling PEAR2, clearly identifying some of the answers, and clearer navigation to pyrus versus pear documentation migth help 'sell' it. Back to the page design - the answer to some of the PEAR versus PEAR2, pear versus pyrus status questions on teh front page might be nice. On Fri, Mar 26, 2010 at 3:50 AM, Daniel O'Connor <daniel.oconnor@gmail.com>wrote: > Well; I just put this on trunk. > http://test.pear.php.net/ > > Notably: > > 1. There's a big fat advert for pear2 on the front page > 2. The package download and homepages now plug pear2 > > I tried to capture the feel of > https://code.silverorange.com/wiki/PEARWebwithin the current > pearweb; > while also making it super obvious to new users > what PEAR is; how to get it. > > I did this by making everything Scary Dark Green. > > All of the other dynamic content and news is now pushed below the page > scroll. > > > Let the flames begin! >