Re: PHP.net Update
| From: | Hannes Magnusson | Date: | Sun, 04 Oct 2009 18:19:58 +0000 |
| Subject: | Re: PHP.net Update | ||
| References: | 1 2 3 4 5 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-6046@lists.php.net to get a copy of this message | ||
On Sun, Oct 4, 2009 at 19:19, Stewart Lord <stewey@ambitious.ca> wrote:
> On 4-Oct-09, at 8:56 AM, Hannes Magnusson wrote:
>>
>> It would be nearly impossible to get the rest of the developer
>> community to agree on new logo.
>> I'd say the first priority if to build a content tree, what should be
>> where and why. We have massive amount of info on the website (not
>> including the manual) but it looks like people have a hard time
>> finding it.
>>
>> -Hannes
>
>
> Hi Hannes,
>
> Thanks for the quick reply!
>
> A content tree sounds like a good place to start. Typically I use the site
> for the manual, downloads and new release information. I think that those
> should be front and center. I don't have much exposure to the other content.
> Did you have any ideas for how to organize the content at the top-level?
We have events and conferences, quick reference tips, where to get
help, mailinglists, how to contact 'us'..
All of these pages are missing tons of info though, and we also lack
an very important page: "how to contribute" :(
There is a sitemap available on http://php.net/sitemap.php
but not
even that contains all webpages or hidden gems.
I have no idea how do organize it or how to present all this :]
You are damn right though, the manual and download/release info is the
most important things and we really need to do something with the
download page.
The manual pages is a bit more problematic. We can't do very much
there other then adjust the CSS and improve the TOC/manual notes. The
actual markup of the _manual_ pages (excluding notes, TOC, and
everything around it) is pregenerated as you can see by clicking 'view
source' on any manual page.
> Regarding the logo and identity. You are 100% correct. We could never get
> everyone to agree. But, we can't let that stop us ;) A fresh logo/identity
> is truly needed.
I don't agree that a new identity is needed at all. The currently logo
is quite "famous" and I don't consider it to be awful enough that the
top priority should be to replace it.
Don't get me wrong, I'd love to brush it up a bit, but creating a
totally new one is not something I think we can do, nor is it "within
our rights" :]
> What if we presented several logos to the community and let them decide? I
> believe that the community identifies with our mascot. I think that a well
> designed elephant logo could be a big hit with the community.
Unsure how I feel with making the mascot into the logo.. I'd much
rather prefer to brushup the current one a little.
> If we really wanted to involve people, we could take submissions from the
> public and offer prizes to the winner and second/third, etc.
We don't have any prizes to offer unless we get some company to
sponsor it.. That could quickly turn into political nightmare though
:]
-Hannes