Hello. This note provides an update on the transition to the new www.ietf.org website, including: - a specific update on some of the issues that have been discussed on this list; - a general update on addressing issues going forward; and - a recap of the website project process. Several site-wide issues raised on this list have been addressed in an update applied today. These include removing the reference to externally hosted javascript and issues with how the site is displayed on smaller viewports such as phones. Some updates have aimed to address accessibility issues raised, and accessibility remains an ongoing focus of the website’s development and editorial processes. Content issues are also being addressed. Tickets already filed via the webmaster@xxxxxxxx mailing list are being resolved as quickly as possible. A publicly viewable version of the queue is available here: https://www.ietf.org/tools/website.html The details of each ticket require a login, but anyone can see the subject line for each open ticket. A site-wide direct link to specific guidance about submitting website feedback has been added here: https://www.ietf.org/contact/website/ Server logs were reviewed after the site went into production. The logs have helped us identify and fix broken links. We will continue to review the logs daily. Since it has been four several years, a review of the new website development process might be useful. There were many opportunities for the community to comment at each stage of the development process. The statement of work [1] for the project was informed by several rounds of IETF community input, including feedback received on this list. Direction for the project was approved by the IESG after consultation with the community. The IAOC received multiple bids, selected Torchbox, and made the announcement to the community at the end of 2014 [2]. The website design was developed based on initial research and feedback sessions conducted with key audiences identified in the statement of work. [3, 4]. Torchbox was onsite at IETF 93 in 2015 to gather in person feedback on the initial design concepts. Screenshots of the initial design were published to the IETF Blog in mid-2016. Further feedback on the new website (online and in person) was gathered from each of the three audiences identified in the statement of work over the course of the past year. Office hours were held at IETF 98 to provide participants a face-to-face opportunity to preview the website and offer feedback [5]. The public beta site was made available https://beta.ietf.org starting in July 2017, and announced on this list [6]. Office hours were held at IETF 99 and IETF 100 to provide participants a face-to-face opportunity to provide feedback. The website site will continue to be updated as feedback is received. One area of focus will be refining and improving search capabilities. This could include being able to search documents in the IETF Datatracker directly from the page at https://www.ietf.org and including more fine-grain search options for IETF participants at https://www.ietf.org/links. In addition, the plan includes reaching out to the other key audiences identified in the statement of work to understand how the site might be further refined to address them. Sincerely, Russ Housley IETF Website Revamp Project Manager [1] Statement of work: http://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf [2] IAOC meeting minutes (See Section 4): https://iaoc.ietf.org/documents/IAOC-minutes-2014-11-12-public.pdf [3] User research: https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf [4] Design brief based on user research: https://iaoc.ietf.org/documents/Torchbox_IETFDesignBrief.pdf [5] Website revamp project update: https://mailarchive.ietf.org/arch/msg/ietf-announce/uGXQbMzNQjSYgnVIke11XeyrIoo [6] Revamp of the www.ietf.org website: https://mailarchive.ietf.org/arch/msg/ietf/bWB2xpxT-WbcuhBBl6Hbrg2juoY