Re: PHP.net Site Structure

From: Date: Fri, 30 Oct 2009 07:14:35 +0000
Subject: Re: PHP.net Site Structure
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.webmaster 
Request: Send a blank email to php-webmaster+get-6289@lists.php.net to get a copy of this message
On 11-Oct-09, at 3:09 PM, Burka Daniel wrote:
The structure and organization of the website is one of the areas that I think is most in need of improvement. ... http://www.whitelands.com/daniel/php/sitemap.html
Hi Daniel, I wanted to provide some feedback on your sitemap document. I think that this document could be developed into more of a project overview. With all of the discussions that are taking place, it would make a lot of sense to have a central "live" document to track our plan. Sections: 1. Home I like the approach of having a larger header on the front page. I think that this is particularly important if the header on the other pages is going to be minimal. I thought it might be nice to aggregate news/blog posts from various PHP sites on the front page. 2. Documentation I agree that we should remove the "interstitial" language step. I would suggest that we default to the language detected via the Accept-Language http request header first, then english second. 3. Downloads Currently users have to jump through another page to get the Windows downloads. Should we provide a direct link to the most popular Windows download? 5. Bugs I don't think this warrants a top-level link. I would be inclined to link to this from a number of places such as Community and Help. 6. Community Instead of "Links" perhaps we should refer to them as related sites. As part of "get involved" we need to present easy on-ramps for users. What specifically needs doing (e.g. writing tests, patching open bugs, punting bogus bug reports, etc.) How do they go about doing it (e.g. 1. get svn, 2. make a patch, 3. post it to a mailing list). BTW, the idea of a bounty system for feature requests came up at Zendcon - I did some digging and there are a few sites that tried to provide a bounty system for open source projects (bountyup.com, bountysource.com, opensourcexperts.com, taskmarket.com), and it looks like they are all pretty much dead. I guess it's one of those ideas that sounds good on paper... Components: 1. Search I think that we should remove the drop down. There has been talk of using jQuery. This would make it pretty easy to add a "live search". The question I have is how well will this perform? We might want to do some tests. Segmented results were in my search mock-up, but in hindsight I think it would be a lot simpler to just have the N most relevant results. The search results page could provide options to filter the results further. When you say "function shortcuts" are you referring to the short urls? I'm not sure this falls under search. Thanks, Stew

« previous php.webmaster (#6289) next »