•   Terri Agnew:Welcome to the Website Revamp Project on Monday, 06th October at 20:30 UTC

    Heidi Ullrich:Hi All

    Dev Anand Teelucksingh:darn - droppped

    Terri Agnew:@Dev, Adigo is dialing back out to you

    Dev Anand Teelucksingh:thanks

    Heidi Ullrich:Could Community be "At-Large Community"?

    Heidi Ullrich:on first glance, it looks great!

    Dev Anand Teelucksingh:back

    Terri Agnew:Dev is back on audio

    Dev Anand Teelucksingh:Indeed - visually, irrespective of the IA

    Heidi Ullrich:Would like to see the Policy activities more prevalent

    Dev Anand Teelucksingh:I like search in front and center

    Heidi Ullrich:+1 for the newcomers

    Heidi Ullrich:How do people quickly get to the Policy development page?

    Anthony Niiganii (MBE):How much work would it be to add a increase or contract font size function?

    Anthony Niiganii (MBE):contrast

    Heidi Ullrich:Apart from the numbers, how do people see the actual policy statements? Same with the Webinars, Beginner's Guides, Podcasts and Online courses..It seems like the numbers are emphaized rather than the actaul work.

    Dev Anand Teelucksingh:the Outreach, Capacity sub headings probably could be increased in size

    Dev Anand Teelucksingh:@Anthony - wouldn't the zoom (Ctrl + / Ctrl - ) work

    Anthony Niiganii (MBE):yes that's true, not always the case for those with visual impairment and screen readers

    Dev Anand Teelucksingh:maybe a tab group could be done for the policy pipeline

    Olivier Crepin-Leblond:usually one can zoom in & out like Dev says

    Anthony Niiganii (MBE):sometimes the zoom bunches all the text together and becomes readable

    Anthony Niiganii (MBE):home looks great

    Dev Anand Teelucksingh:a simple example of tab groups http://blixt.org/media/a/1/tabs-hover/page3.html

    Heidi Ullrich:homepage looks great, indeed.

    Anthony Niiganii (MBE):other than the text size function, it looks good so far. 

    Heidi Ullrich:We might need to see if the Capacity Building Webinars could be put under ICANN LEARN

    Heidi Ullrich:and then a link to ICANN LEARN is put on the homepage...

    Heidi Ullrich:could discuss this in LA...

    Heidi Ullrich:In fact, the all of those four activities could be on ICANN LEARN

    Dev Anand Teelucksingh:Also, thinking the events/calendar needs under At-Large work

    Dev Anand Teelucksingh:** Reminder in 15 minutes **: Pre ICANN 51 Briefing WebinarThe agenda and call details are available at: https://community.icann.org/x/vRbxAgAdobe Connect: https://icann.adobeconnect.com/atlarge-briefing-session/

    Dev Anand Teelucksingh:well, then the badge could be displayed indicating the number of announcements

    Dev Anand Teelucksingh:http://getbootstrap.com/components/#badges

    Anthony Niiganii (MBE):I have to step away from the meeting, just informed I have a pipe leaking in my basement and need to go get that fixed right away.  Talk to you all later. The site is starting to look great.

    Dev Anand Teelucksingh:maybe a word cloud

    Dev Anand Teelucksingh:could also be used

    Heidi Ullrich:Good luck, Anthony!!

    Heidi Ullrich:So this is automatic or will Ariel need to update this as she does the Correspondence page?

    Heidi Ullrich:and these will all be available in the 6 UN?

    Heidi Ullrich:@Steve, are the ICANN.org pages translated like that?

    Heidi Ullrich:with Language services automatically translating them?

    Heidi Ullrich:That would be ideal!

    Heidi Ullrich:is that using the website tool you mentioned?

    Heidi Ullrich:so whichever way, at-Large staff won't need to send the EN to be transltated?

    Heidi Ullrich:Great!!

    Heidi Ullrich:Could the graphic to the ALAC policy process be used?

    Olivier Crepin-Leblond:I'm not fond of the Z when looking at having compact policy pages

    Olivier Crepin-Leblond:the Z is just explanatory

    Heidi Ullrich:So under Get Involved?

    Steve Allison:Under About there would be a page on How Policy Advice works

    Heidi Ullrich:Also, where are the ALAC members and links to the WGs?

    Heidi Ullrich:There is a need to list who the ALAC leaders are

    Heidi Ullrich:Who are the members of the ALAC

    Dev Anand Teelucksingh:and those from previous years as it changes every year

    Heidi Ullrich:correct, Dev

    Heidi Ullrich:perfect, Steve. Good location

    Heidi Ullrich:if it is called "At-Large community" ;)

    Heidi Ullrich:When will we be able to see the color version?

    Heidi Ullrich:Sorry All, I need to drop off

    Steve Allison:I dont have a date for the color version yet

    Steve Allison:i will let you know when i do

    Dev Anand Teelucksingh:take care all

   

   

• Dev Anand Teelucksingh:It was shown at the end of last call

    Dev Anand Teelucksingh:https://community.icann.org/download/attachments/5112175/ALAC_Policy_Advice_Chart.jpg

    Dev Anand Teelucksingh:Re: http://www.circleid.com/topics/ is an interesting taxonomy ideas that could be used

    Heidi Ullrich:Sept. ARticles:

    Heidi Ullrich:ALAC Policy Development Activities from mid-August to early-SeptemberAlan Greenberg Selected as next ALAC ChairAt-Large Community Comprises 179 At-Large StructuresSeptember Monthly At-Large RALO RoundupAt-Large Website Revamp Project Begins

    Dev Anand Teelucksingh:The Policy Summary is great work, btw

    Heidi Ullrich:@Ariel, I think the Policy Updates are quite clear for outsiders/newcomers.

    Heidi Ullrich:I would hestitate adding a process that involves extra staff work to update this.

    Heidi Ullrich:or make it more clear

    Dev Anand Teelucksingh:Or even Latest News

    Dev Anand Teelucksingh:https://community.icann.org/display/atlarge/At-Large+Mailing+Lists

    Dev Anand Teelucksingh:was my attempt

    Dev Anand Teelucksingh:Correspondence could be renamed to "Policy Advice"

    Heidi Ullrich:LOL, Olivier!

    Heidi Ullrich:I heard this morning that Jobs believed it was more important to sell dreams rather than products ;)

    Steve Allison:let's do that

    Heidi Ullrich:So, it is good to dream big!!

    Dev Anand Teelucksingh:look at the line for the apple phone https://twitter.com/thomasmarkjay/status/512908074081062912/photo/1

    Dev Anand Teelucksingh:;-D

    Heidi Ullrich:but their shares are falling a bit  - here is why : http://bgr.com/2014/09/16/why-is-apples-stock-price-falling/

    Heidi Ullrich:Good idea, Steve

    Heidi Ullrich:I support that

    Heidi Ullrich:Could they also call into the session with you during the ICANN Meeting?

    Steve Allison:yes, i will encourage them to do so

    Heidi Ullrich:Thanks

    Heidi Ullrich:Please send us their names once they confirm

    Heidi Ullrich:and email addresses

   

Discussion about the Correspondence Page

Intended Purpose of the Correspondence Page: 

• To serve as an outward facing, comprehensive depository of the published work of the ALAC 
• To encourage the visitors to intuitively discover the work of the ALAC 
• To link to appropriate pages in the Policy Development wiki space so that it encourages visitors to get involved in the ongoing work of the ALAC 

Issues about the Correspondence Page: 

• Misleading title of the page — the Correspondence page mainly contains Statements and only a few announcements and emails. 
• Ineffective classification for the Statements — regions and RALOs are repetitive, and there is no keyword or taxonomy to describe issues/topics. 
• Poor search capability within the page and the website — this is a consequence of the ineffective classification for the Statements. 
• Inconsistent formatting for some Statements, including the numbering of translated documents.
• Tendency to loose visitors’ interests:
1. It takes multiple clicks to get to the Statement;
2. The long-winded staff introduction section takes away the attention from the readers;
3. There is no context or background about what the Statement is 'in response to’; 
4. It is not clear ‘why’ the readers should care about them. 
• No helpful links to the At-Large wiki workspace for those Statements in the Policy Development page — otherwise, interested visitors can be directed to appropriate pages and participate in the making of the ALAC Statements.

Improvement Ideas: 

• Create a taxonomy landing page that details the key issues/topics which the ALAC has been working on: 
  • The background materials about those issues/topics need to be clear, interesting, and relevant to the Internet end-users; 
  • It may be worthwhile to rewrite the policy chapters on the Beginner’s Guide; 
  • We need to frame the issues/topics to show the readers ‘why they should care’; 
  • The taxonomy landing page can effective link to the ALAC Statements that address those topics, help readers keep track of the ongoing work of the ALAC around those topics, create pre-natal discussions and facilitate ‘call to action' (e.g. to make it easier for readers to comment on the current draft Statement on those topics). 
• Redesign the way to publish the ALAC Statements: 
• Each published ALAC Statement should be broken out into the relevant components so readers can quickly assess what they wish to learn: context summary, summary of statement (or any other supporting documents), name and affiliation of the penholder, key dates related to the making of the Statements, related Statements, etc. 
• Those components need to be arranged in a logical and effective order, with the most interesting component at the top (e.g. the ’Staff Introduction' paragraphs describing the process of the making of the ALAC Statement need to be summarized and put in a less prominent area). 
• Explain the Policy Development process on the website in a clear and engaging manner: 
  • We need to emphasize that anyone from the community can be the penholders and anyone can comment on the draft Statements; the policy development process should be a bottom up process initiated by RALOs. 
  • We may need to build certain platform or mechanism on the website to help community members to participate in policy development easily. Wiki is a good platform for working on the actual Statement, but the wiki isn’t helpful in facilitating discussion around whether the ALAC should have a Statement in response to Public Comment request. 
• Upgrade the search functions within the Page
• We may need to include issue/topic keywords and drill down filtering (faceted search?). 
• The search capability needs to be complex enough for seasoned members to find documents. 
• Although the mission Statement for the ALAC is very broad and the community members have few common denominators, we need to clearly state the ALAC mission statement, emphasize and frame the ‘end-user’ key point, and display it in an obvious place on the website. In that way, we can show how the work of the ALAC (e.g. ALAC Statement) ties to its mission.  

Other Requirements: 

• At-Large Staff need to have the capability to manage content on the website without going through web-admin. 
• Translation requirement — it may be a future requirement to translate important static content on the website, but at a minimum, all ALAC Statements must be translated and properly archived on the site. 

• At-Large Website Redesign Preliminary Requirements

• At-Large Website Redesign Project Steps

• Community interview questions:
  • Final master interview guide
  • Draft interview guide
  • Additional questions
• Community interview transcripts:
  • Gunela Astbrink
  • Adela Danciu & Yuliya Morenets
  • Alan Greenberg & Yrjo Lansipuro
  • Sylvia Herlein Leite
  • Cheryl Langdon-Orr
  • Evan Leibovitch
  • Holly Raiche
  • Manuel Schneider
  • Dev Anand Teelucksingh