please, stick to text-mostly. text-overwhelmingly. The current site is
almost perfect in that regard, and it would be a huge shame to wind up with
bloat, flash, movies, images, for appearance sake.
On Thu, Mar 13, 2014 at 2:44 AM, Michael Richardson
<mcr+ietf(_at_)sandelman(_dot_)ca>wrote:
Stephen Farrell <stephen(_dot_)farrell(_at_)cs(_dot_)tcd(_dot_)ie> wrote:
> These are motherhood and apple pie things but just
> in case they got lost in the process..
> Please ensure that the IETF web site is minimally
> intrusive on visitors' privacy. I don't think its bad
> right now (but haven't tried to check) but let's make
> sure we don't go all analytics-mad for no good reason:-)
> In a similar vein, please ensure it renders reasonably
> for those who run without JS/cookies/+NoScript etc.
In particular, if some part of the site requires additional JS, then it
needs
to become obvious that this is the case, and that part of the site MUST be
tolerant of a reload.
A number of sites (most annoyingly, payment processing, for which JS ought
to
be exactly what you don't want), will mysteriously stall halfway through
the
"checkout", because some *new* source of JS is necessary. Often loaded by
some other JS.
This is something people who use NoScript see regularly.
So far, I've not had this problem with ietf.org sites, and I think that
Henrik made a decree (perhaps not so strongly worded...) that all JS files
should come from IETF servers. (Here is a place for ni: urls..)
--
Michael Richardson <mcr+IETF(_at_)sandelman(_dot_)ca>, Sandelman Software
Works
-= IPv6 IoT consulting for hire =-