Subject: [TOOLS-DEVELOPMENT] Status of the Project to Revamp the IETF Website

From: Russ Housley <[email-masked]>
Date: Wed, 4 Oct 2017 12:54:33 -0400

1) All the critical bugs/issues have been addressed by Torchbox.  There are few outstanding issues, but none are blockers to deployment.

2) A handful of pages are awaiting “v1” of content, otherwise the content for the "Top 100” pages is ready for review by the content ‘editors'

A full update is here:  https://docs.google.com/spreadsheets/d/1LCk9Fn2kdeJPNPg5z5yIDmHs8KM_HEKbDS4k2PVLNSo/edit?usp=sharing

Of note: The Secretariat have now provided a model meeting page with childless pages (for IETF 101). The plan is to bring the last 10 pages in alignment with this.

3) There is an open question about where IESG Statements, and Appeals and Responses should live.

The proposal is to move them to the datatracker. This seems technically feasible (but will require some development, perhaps at the next CodeSprint).

ACTION: Ask the IESG whether they agree with this proposal  -- Alexey has the action to raise this with the IESG.

IN THE INTERIM: We will create a set of index pages on the Wagtail website an point to static web pages.

4) Conduct non-IETF participant interviews to review and get feedback on the site. Four (4) interviews have been conduced. The summary is that the new website is much more understandable and appealing. There were a few suggestions about information to provide (notably about meeting registration, including registration for remote participation).  See https://github.com/ietf/www.ietf.org/issues for more details.

5) Prepare for next round of community review.  By 19 October, we will be ready for the next round of community review. I intend to craft an update and invitation to review the website to share with the community. We plan to have ‘office hours’ at IETF 101.

6) Ensure WCAG 2.0 compliance. Torchbox has implemented changes that have improved the situation. We believe the new pages now outperform the old www.ietf.org site in terms of WCAG compliance. However, improving accessibility will continue to be an area of focus for the revamped website, especially as we develop norms for content.

7) Improve data use and load times. The beta.ietf.org website was moved to the CDN used by www.ietf.org, significantly improving load times. We will continue to optimize elements such as images to further improve performance as experienced by the visitor. Of note, the reviewers interviewed did not report load time as a significant issue.

Russ & Greg