From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Gevik Babakhani <gevik(at)postgresql(dot)nl> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Redesigning postgresql.org |
Date: | 2015-02-03 10:07:11 |
Message-ID: | CA+OCxozf3Msamhqbg6mYeryEdpbU1abRstN6Q2BaJS-4=ES60w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Tue, Feb 3, 2015 at 9:59 AM, Gevik Babakhani <gevik(at)postgresql(dot)nl> wrote:
>
>>
>> I think you misunderstood that a little. If Javascript is disabled,
>> the site should gracefully fall back to a mode where the content is
>> still readable and usable, but not necessarily as nicely.
>
> I was implying the same :)
> JS will become very important when presenting the website on a mobile/touch device. I am thinking out loud here, but not all functionality of the website would be needed (or maybe even make sense) on a touch device.
Right - and even if a tablet with JS disabled falls back to the
standard desktop design, I consider that to be OK - that's the users
problem; if they want the responsive layout, turn JS on again. If not,
get the default site with no bells and whistles.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2015-02-03 10:41:16 | "current" docs vs. search rankings |
Previous Message | Gevik Babakhani | 2015-02-03 10:01:14 | Re: Redesigning postgresql.org |