Update: IETF Website Redesign

Alexa Morris <amorris@amsl.com> Tue, 20 May 2008 06:01 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAD413A6B9E; Mon, 19 May 2008 23:01:45 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F0CC3A6B8B; Mon, 19 May 2008 23:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.895
X-Spam-Level:
X-Spam-Status: No, score=-97.895 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id II0xyrzeOe0r; Mon, 19 May 2008 23:01:35 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by core3.amsl.com (Postfix) with ESMTP id C25E23A6B95; Mon, 19 May 2008 23:01:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by thunder2.amsl.com (Postfix) with ESMTP id 178CC48141; Mon, 19 May 2008 23:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.amsl.com ([64.170.98.20]) by localhost (thunder2.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6tHOF9GeMb3; Mon, 19 May 2008 23:01:33 -0700 (PDT)
Received: from [192.168.1.103] (adsl-66-126-244-166.dsl.sntc01.pacbell.net [66.126.244.166]) by thunder2.amsl.com (Postfix) with ESMTP id 8744648140; Mon, 19 May 2008 23:01:32 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 19 May 2008 23:01:31 -0700
Subject: Update: IETF Website Redesign
From: Alexa Morris <amorris@amsl.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Message-ID: <C457B74B.4ECDF%amorris@amsl.com>
Thread-Topic: IETF Website Redesign
Thread-Index: Aci6PvMjMaI9kyYyEd2VpgAUURi4Ig==
Mime-version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

We are slowly and steadily moving forward with the IETF website redesign
project.  Many of you rightly expressed concern about the fact that the way
we recruited volunteers for this effort made it impossible for people in
certain time zones to participate. I want to let you know that the next time
we do something like this, we will collect names for a day or two and then
randomly select a number of names from the pool of volunteers.

The website redesign team will be getting together in the next couple of
weeks for a kickoff conference call, and some of the initial actions of the
team will include:

1) review of considerations / design principles, adding or revising as
necessary 
2) creation of a timeline for start and conclusion of the redesign project
3) creation of a process outline, such as:
    - create new site in parallel to existing site, using URL such as
www4.ietf.org
    - get new site running off of datatracker, etc in parallel to ietf.org
    - announce site to community, for general feedback
    - refine site as appropriate
    - announce timeline that sites will exist in parallel, so that tools
team and general community have ample warning to reconfigure bookmarks,
tools etc to run off of new site
    - shutdown old site and move new site to ietf.org

In the meantime, here at AMS we have developed the following to use as a
foundation for this effort, though it may be revised when the website
redesign team meets.

Purpose of the IETF website:

* To provide general information about the IETF to the public
* To house the IETF's Internet-Drafts
* To house the various tools used by the IETF community to further their
  goal to make the Internet work better.
* To provide the IETF community with access to Working Group
  information
* To provide the IETF community with access to IESG information
  - IESG statements
  - Appeals information
* To archive and log various mailing lists, Jabber rooms, etc. used in
  IETF work

Goals for website redesign:

* Improve site navigation
  - Clear Site Map
  - Define what is available on the site
  - Help users find the information they want quickly
  - Make it easy for users to request additional information
* Make it easy for a person who wants to become active in the IETF to
  find the information they need
  - "New to the IETF?" link posted on front page
* Consistent layout and design of pages
* Eliminate redundancy (i.e. avoid having the same information posted--
  rather than linked--in multiple places)
  - When redundancy aids in speedy navigation, *links* can be placed in
    multiple locations to that information, but we should avoid posting
    the same *text* information in multiple places
* Make pages clean and easy to read

Considerations for redesign effort (design principles):

* Web site should follow the W3C guidelines for user accessibility.
  Web Content Accessibility Guidelines 2.0:
  http://www.w3.org/TR/2008/CR-WCAG20-20080430/
* Web site should have stable URLS
  - Once information is posted, that same information can be obtained
    from the same URL over and over.
* Users should be able to navigate the web site with images turned off
  in their browser.  (All images should have ALT text describing the
  content.)
* Pages should load as quickly as is reasonable; minimal graphics
* The new site should not impede the IETF Community from running their
  own tools to scrape information from the site

We will try to keep the community updated as we move along with this project
but, as always, if you have any questions or concerns please feel free to
contact me.

Regards,
Alexa

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>




_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce