Re: PHP-WEBMASTER: /web/php/branches/PROTOTYPE_2010/
| From: | Hannes Magnusson | Date: | Fri, 19 Mar 2010 13:59:11 +0000 |
| Subject: | Re: PHP-WEBMASTER: /web/php/branches/PROTOTYPE_2010/ | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-7655@lists.php.net to get a copy of this message | ||
On Fri, Mar 19, 2010 at 13:36, Paul Dragoonis <dragoonis@gmail.com> wrote:
>
>
> On Fri, Mar 19, 2010 at 10:59 AM, Hannes Magnusson
> <hannes.magnusson@gmail.com> wrote:
>>
>> On Fri, Mar 19, 2010 at 11:33, Paul Dragoonis <dragoonis@gmail.com> wrote:
>> >
>> > So who likes the idea of having recommended results on the search
>> > results
>> > page,
>> > and who likes the ideas of also having some recommended results if the
>> > autocomplete returns 0 results.
>> >
>>
>> Keep in mind that by the time this is finished most browser will have
>> implemented a good chunk of the HTML5 and the DOMStorage specs, so we
>> could push all sorts of data to the client, incrementally adding more
>> stuff to it on every search or whatever we would like.
>>
>
> Realistically we need to create against what technologies are available now
> with an open mind of what will be available to us in future. When XHTML5 +
> DOMStorage becomes a standard in all major supported browsers then we can
> look into refactoring it for new emerging technologies.
It already is (see Jordis reply).
We have no interest in supporting legacy browsers, plus the fact
people using legacy browsers are in no way our target audience.
>> I however consider this discussion premature (and will be very hard to
>> track down in the archives due to misleading subject).
>>
>> We need to work on refactoring the existing content and design a layout
>> for it.
>> What fancy features and functionality we will then provide can be
>> discussed and implemented.
>>
>
> I think the design for the page on http://prototype.php.net is
> good for us
> to move on and focus on other aspects such as interaction with javascript.
Then you misunderstand entirely the reason for the redesign.
We need *content refactoring*. We have bunch of gold in random
sidebars and in deeply nested pages which people simply don't know
about.
We need to reorganize the entire website, not just mock up a random manual page.
-Hannes