Hi, > On 1 Nov 2017, at 10:49, Stewart Bryant <stewart.bryant@xxxxxxxxx> wrote: > > Hi Russ, > > I must say I still prefer the original in terms of utility, clarity and information density. I must say I agree. It certainly should be possible to lay out the links page so that you can see where to go at a glance, rather than feeling you have to read the page line by line. > I am not sure if the font being used is mandated, but I find it far less crisp, almost blurry compared to the smaller font of the original. I find such lack of crispness on web pages irritating and when I see it I am distracted by wondering if there is a technical failure in my system. People like 4K for a reason, and I see no reason why this preference would not be carried over to web pages. > > Whilst I understand the need to provide an accessible interface I don't see why there cannot simply be a parallel high efficiency interface as well. I would second this request. As per the discussion at IETF99, I accept that www.ietf.org is essentially conceded to IETF ‘comms and marketing’, but there’s no reason we can’t have alternative well-laid out index pages as well. There’s much of course that can be done simply by only using the datatracker and tools pages, which have gone from strength to strength over recent years. > A useful addition to both the original and to this would be a direct link to id-nits right next to (well right before) the submit tag. One other point is that I don’t think I’ve yet seen what a meeting page would look like in the new “glossy" format. Under the new system, what would https://www.ietf.org/meeting/100/index.html look like? If it’s https://beta.ietf.org/how/meetings/upcoming/100/, that’s not really comparable, yet. That’s a really useful, and clearly laid out, page for finding info at meetings. I assume there’s a change coming, as meeting pages fall under www.ietf.org. Thanks, Tim > > - Stewart > > > On 31/10/2017 21: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 >> - 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 >