> On 10 Nov 2017, at 23:01, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote: > > On 01/11/2017 10:36, Russ Housley wrote: >> I want to share an update on progress on the IETF website revamp project. In particular I’d like to highlight what has been done to respond to feedback from the IETF community received around IETF 99. >> >> A. Provide a landing page dedicated to current IETF participants >> >> A draft is currently posted at https://beta.ietf.org/links/ >> >> That page includes links to: >> - items on the left-side at www.ietf.org (or a subset thereof) >> - information about the next IETF meeting >> - links to functions at datatracker.ietf.org >> >> The goal is to make this page: >> - viewable in a single screen on a desktop/laptop display > > In that, it fails, compared to https://www.ietf.org/content.html : > a) at least 5cm vertical space is wasted with pointless blurb. > b) because of the lack of columns and empty space, it is much > harder to spot individual items. > > On the other hand, it's usable on a smartphone, which the old > page hardly is. > > So there's the basic question: do we want to make the site > harder to use on a laptop or desktop so that it's easier to use > on a smartphone? That goes for pretty much every page on the beta > site, I think, although it seems to be a rather noticeable issue > for this particular page. Do we have an example meeting page in the new “beta” format? Tim > > Regards > Brian > >> - reachable via a short, memorable URL >> >> The current content includes changes implemented based on suggestions received via email after IETF 99. Of course, this page will be updated further based on input from the community. >> >> B. Ensure WCAG 2.0 compliance >> >> Since IETF 99, we have worked with the website developer to improve compliance. This is a requirement of the Statement of Work (https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). We believe that has been accomplished. However, ensuring and improving accessibility must be part of ongoing editorial practices, so it will continue to be an area of focus for the website. >> >> C. Conduct review with other key audiences, especially potential participants and non-participants >> >> Additional interviews with members of the key audiences have been conducted to gather input. In general, response to the beta.ietf.org site was positive. IETF newcomers say that the new site makes it easier to understand what the IETF is all about. Some specific suggestions have been incorporated into the project, and they are included at https://github.com/ietf/www.ietf.org/issues >> >> D. Improve data use and load times >> >> Since IETF 99, the beta.ietf.org site was placed behind the Cloudflare CDN. This has significantly improved load times. Of note, in interviews (see item C above), new or non-IETF participants located in Latin America and Africa did not report load time as a significant issue. However, as the new site moves to production, the editorial process will continue to fine tune how images and other elements are handled to further improve performance. >> >> Next steps: >> >> We are continuing to fine tune content and are aiming to move to production after IETF 100. One significant task remaining is to ensure continuity for important URLs, as specified in the Statement of Work. We expect to tackle that after IETF 100. >> >> We welcome input and suggestions. We held "office hours" at IETF 98 and IETF 99, and we will hold "office hours” at IETF 100. If you will be in Singapore, please take this opportunity to share feedback in person. Details will be posted on a sign around the IETF meeting registration desk. And, of course, questions or issues can always be raised at https://github.com/ietf/www.ietf.org/issues >> >> Sincerely, >> Russ Housley >> IETF Website Revamp Project Manager >> >