06 November 2014
Agenda
- Provide feedback on the ICANN 51 website revamp presentation & review community input (10min)
- Review the wireframes of 'What We Do,' 'Get Involved,' and the general content pages (30min)
- Identify potential gaps in wireframes (10min)
- Discuss the next phase: Brainstorm content development strategy (35min)
- AOB (5min)
Adobe Connect Chat
Terri Agnew:Welcome to the Website Revamp Project on Thursday, 06th November at 20:00 UTC
Heidi Ullrich:Do we need more time for item 3?
Heidi Ullrich:@Steve, to what extent are we able to revise the wireframes with the current vendor/current b udget?
Ariel Liang:Stie maps & wireframes: https://community.icann.org/x/zCXxAg
Ariel Liang:welcome Laura
Alan Greenberg:The issue of info being statis with long times since the last activity is that it will give the impression that we are not doing anything.
Alan Greenberg:These new pages are good.
Heidi Ullrich:The current content needs polishing
Laura Bengford:@Heidi, we will be able to update wireframes
Heidi Ullrich:I'm not being critical :) I'm being constructive !
Laura Bengford:This is really good feedback
Heidi Ullrich:Are the colors on the map the population?
Ariel Liang:Colors come next
Heidi Ullrich:perhaps the regions could be identified by color
Ariel Liang:Vendor is working on the Style guide
Heidi Ullrich:so blue for EURALO?
Ariel Liang:we will surely consider using the RALO colors
Alan Greenberg:Not sure that "consider" is sufficient.
Heidi Ullrich:Would the intern only shepherd the process of getting the content or actually prepare the content?
Alan Greenberg:In my mind, actually write. We need someone with technical background and a journalism student or something like that.
Olivier Crepin-Leblond:I agree with Alan
Alan Greenberg:There are lots of really good technical writers around. Problem is that they earn a lot of money doing it.
Dev Anand Teelucksingh:apologies for missing this meeting - a previous meeting went way overdue - I'll review the recording and/or slides for comment
Olivier Crepin-Leblond:does Dev have any question regarding the wire ramen?
Dev Anand Teelucksingh:not yet
Dev Anand Teelucksingh:I'll review them later and offer comment - yes thanks
Olivier Crepin-Leblond:auto correct on iPad turns. frames to ramen :-)
Laura Bengford:thank you everyone.
Dev Anand Teelucksingh:bye all
Audio Recording
Transcript
06 October 2014
Adobe Connect Chat
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
25 September 2014
19 September 2014
Adobe Chat
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
Adobe Recording - Due to AC tech issues during call this is a partial recording
Audio recording - Full recording
18 September 2014
12 September 2014
Action Items
- Olivier Crepin-Leblond, Dev Anand Teelucksingh, Anthony Niiganii to do the following:
Could you distill the historical or current issues/topics being worked on at At-Large into a Top 5 Categories (ex: WHOIS, Privacy, IDNs, ICANN Strategic Planning, IANA Transition)? Some issues/topics may be directly associated to a large ICANN issue area such as Strategic Plan, wheres others are independent (and could be connected to many ICANN topics) such as Privacy. It’s fine if you can identify more than 5 top categories.
Key Takeaways
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:
- It takes multiple clicks to get to the Statement;
- The long-winded staff introduction section takes away the attention from the readers;
- There is no context or background about what the Statement is 'in response to’;
- 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.
Adobe Chat
Kathy Schnitt: Dear all, Welcome to the Website Revamp Project on Friday 12th of September at 16:00 UTC
Kathy Schnitt:Welcome Ariel and Dev
Ariel Liang:Just FYI - everybody is here. Anthony sent his apologies
Dev Anand Teelucksingh:looks like my mic isn't working
Dev Anand Teelucksingh:on the call
Ariel Liang:http://atlarge.icann.org/correspondence
Heidi Ullrich:If a new format is being considered, perhaps the Board Resolution page might serve as a model: https://features.icann.org/resolutions
Dev Anand Teelucksingh:http://www.jquery-bootgrid.com/Examples#data
Olivier Crepin-Leblond:translations of these statements are not up to date. 2013 only yields 3 translated documents
Olivier Crepin-Leblond:this is a huge amount of translations missing. I do not know whether they were undertaken and missing from the list, or whether the translations were not done
Heidi Ullrich:Here is the note to the G8 : http://atlarge.icann.org/correspondence/correspondence-20may11-en.htm
Olivier Crepin-Leblond:Here is the note to NTIA:
Olivier Crepin-Leblond:http://atlarge.icann.org/de/node/25511
Heidi Ullrich:http://atlarge.icann.org/correspondence/correspondence-14dec11-en.htm
Heidi Ullrich:that is the note to the NTIA
Heidi Ullrich:+1 Steve
Olivier Crepin-Leblond:Heidi your pointer are to the US Congressman
Heidi Ullrich:we need greater searchability
Heidi Ullrich:ah, sorry
Heidi Ullrich:that was the letter I was referring to
Olivier Crepin-Leblond:also -- note that some of these summaries are wrongly formed, and the actual statement is missuing!
Heidi Ullrich::(
Olivier Crepin-Leblond:I used Google to find the letters
Olivier Crepin-Leblond:wow -- the one to NTIA NOI is actually even missing. There is the Staff intro & no link to the Statement itself, apart from a link to the workspace where we built it....
Dev Anand Teelucksingh:http://www.jquery-bootgrid.com/Examples#data is an example of interactive search
Heidi Ullrich:I agree that broad topics are needed
Heidi Ullrich:Dev, Matt and you developed a page where the impact on end users was spelled out
Heidi Ullrich:@Ariel, that might be a good solution for a start
Heidi Ullrich:@Ariel, please look at the Beginner's Guide to ALAC Policy
Heidi Ullrich:It has this kind of summary text on the main topics, I believe
Heidi Ullrich:Chart: https://community.icann.org/download/attachments/5112175/ALAC_Policy_Advice_Chart.jpg?version=1&modificationDate=1373387404000&api=v2
Steve Allison:Thank you
Dev Anand Teelucksingh:Phone connection lost, but listening via AC audio
Dev Anand Teelucksingh:Good idea
Dev Anand Teelucksingh:This was great
Dev Anand Teelucksingh:Thanks everyone - take care
Ariel Liang:Thank you all!
11 September 2014
Adobe Chat
Terri Agnew:Dear all, Welcome to the Website Revamp Project on Thursday 11th of September at 16:00 UTC
Olivier Crepin-Leblond:OUCH -- that hurts!
Olivier Crepin-Leblond:Bounce Rate 50/70% ???
Dev Anand Teelucksingh:Ouch indeed
Anthony Niiganii (MBE):It sometimes take me awhile to find what I need and just end up jumping to Google to search
Heidi Ullrich:Will the Seasoned community members use the wiki as their primary source?
Anthony Niiganii (MBE):lol why me? lol
Ariel Liang:people like you are a primary audience
Anthony Niiganii (MBE):thanks...yea I can agree with that
Heidi Ullrich::)
Ariel Liang:@Heidi - yes, so that's why they are secondary audience
Ariel Liang:primary ones don't really know about the wiki or know how to use the wiki
Heidi Ullrich:Thanks, Ariel
Ariel Liang:so the website is a main platform for us to communicate with them
Ariel Liang:no problem
Heidi Ullrich:How are they making an impact - we could have a spotlight for that
Dev Anand Teelucksingh:Well, primary ones can find the wiki if they use Google search
Heidi Ullrich:they should be using the Dashboard...
Ariel Liang:but it is not an effective landing page for the community
Ariel Liang:newcomers will get confused how to use it
Heidi Ullrich:@Ariel, I agree the dashboard is confusing for newcomers
Dev Anand Teelucksingh:agreed, a redesign is needed for wiki, the wiki needs to have a menu/section for newcomers that discover the wiki page where they can go to next
Heidi Ullrich:What is a wireframe
Ariel Liang:wireframe is similar to the structure of a website
Ariel Liang:http://en.wikipedia.org/wiki/Website_wireframe
Heidi Ullrich:Thanks!
Heidi Ullrich:When would new content be developed? Many of the pages are out of date...
Steve Allison:we can do some of this in tandem. My hope is that during the design work, we can concept on what topics should be written at least to support the designs/wireframes so that we can present a polished product, and then over the long term we can discuss a strategy to consistently develop new content
Laura Bengford:We can also may leverage some of the Getting Started / newcomer guides from icann.org
Steve Allison:Thanks Laura. I think we're thinking the same. Some of that content is the most comprehensive for newcomers
Heidi Ullrich:Good idea, Laura
Heidi Ullrich:There is likely up to date info on the wiki as well
Laura Bengford:Maybe leverage events or the calender filtered for ALAC.
Heidi Ullrich:Thanks very much Ariel and Steve!
Anthony Niiganii (MBE):thanks Ariel and Steve
Dev Anand Teelucksingh:indeed, much food for thought
Heidi Ullrich:The Board Resolution page might be a model to follow for ALAC Policy Advice: https://features.icann.org/resolutions
Laura Bengford:Depending on the artwork required could be by UX designer or graphic designer. Usually they are one offs as needed.
Anthony Niiganii (MBE):great question Olivier about the look and feel
Laura Bengford:Also photos can be used.
Heidi Ullrich:Photos will personalize it
Heidi Ullrich:we also have some great graphics already developed we could use
Dev Anand Teelucksingh:I think there are other synergies and similiarlies with other ACs (SSAC, GAC, RSSAC)
Dev Anand Teelucksingh:ACs generate correspondence for eg
Anthony Niiganii (MBE):just taken it in
Laura Bengford:+1 on the synergies
Ariel Liang:agree with Steve - need to identify what are the most important content for updates
Ariel Liang:and then figure out the ways for update
Steve Allison:Laura can you talk about accessibility and translation
Laura Bengford:We can work on Accessibility in tandem with Accessibility WG and tools developed. Also translation
Ariel Liang:http://atlarge.icann.org/correspondence
Anthony Niiganii (MBE):I agree with Laura, and this is something that should be brought up with the Accessibility WG as there is discussion about developing checklist for virtual participation, in whatever form that may take
Heidi Ullrich:+1 Laura and Anthony
Heidi Ullrich:I agree that the Accessbility WG - with the TTF - could advise on this point
Heidi Ullrich:Ariel and All - please take a look at the board resolution page: https://features.icann.org/resolutions
Anthony Niiganii (MBE):unfortunately I am not available to participate tomorrow., and will catch up with the recording.
Ariel Liang:@Heidi that's a good example!
Dev Anand Teelucksingh:re: board resolution page, the categories is the idea, however correspondence can have multiple "tags" - gTLDs, IDN
Anthony Niiganii (MBE):I can see that many people who come to the site first do not see a "welcome greeting" that is important to foster community engagement
Anthony Niiganii (MBE):that could be why some many jump
Heidi Ullrich:Good point, Anthony
Heidi Ullrich:Great job, Ariel and Steve!!! Also, thanks to the community web team!! We selected the right people!
Laura Bengford:Great meeting, thank you everyone!
Anthony Niiganii (MBE):I will prepare some thoughts tonight that can be shared with everyone.
Heidi Ullrich:Thanks, Ariel
Heidi Ullrich:Anthony, I meant!
Heidi Ullrich:I write "Thanks, Ariel" so often ;)
Anthony Niiganii (MBE)::) it's ok...Ariel is a team member anywhere
Ariel Liang:hahaha
Ariel Liang:thanks Heidi
Anthony Niiganii (MBE):Ekosani Everyone! Kinanaskomitinawa!
Ariel Liang:Thank you bye bye
Heidi Ullrich:bye!
Dev Anand Teelucksingh:Take care all
Steve Allison:Thanks all. bye
Action items
- Product team (Steve Allison) to propose a method for producing artwork in the long run
- The website project team (Dev Anand Teelucksingh, Olivier Crepin-Leblond, Anthony Niiganii) to review the questions from the target audience and identify key activities and information about the At-Large community to be presented on the new website in the near future meeting
- The website project team (Dev Anand Teelucksingh, Olivier Crepin-Leblond, Anthony Niiganii) to deep dive in the Correspondence page in next meeting
- Ariel Liang to explain to Steve about the Correspondence Page and the PD page on the wiki
22 August 2014
Action Items
- Steve Allison to speak with Chris Gift and Laura Bengford to:
- 1) Understand and set realistic goal for the website revamp project based on current
- 2) Identify vendor for the website (possibly Column Five?)
- Steve Allison to review the community interview transcripts and summary posted on this page.
- Steve Allison to review the At-Large Beginner's Guides: 1) Participating in At-Large, 2) Policy Advice in ALAC, 3) At-Large Structure
- Ariel Liang to review the At-Large website page by page and identify the problems of the site in a specific manner
- Ariel Liang to start drafting the project background, current situation, and objective section of the project charter
- Ariel Liang to brainstorm possible community survey based on the interview questions
- Ariel Liang to review materials of Column Five: Capabilities & Process Review
08 August 2014
Agenda
- Introduction
- Review of the Budget
- Review of the Timeline
- People involved and work breakdown
- Project management
- Extent of At-Large community involvement
Action Items
- Ariel Liang and Laura Bengford to review the interviews and identify potential themes for the website (the themes will be part of the project charter).
- Ariel Liang and Laura Bengford to set up a work session and complete the first draft of the project charter.
- Ariel Liang to inform Dev and Olivier about the making of the project charter and later ask them to comment on the draft.
- Laura Bengford to figure out the requirement of project management and try to identify a person from the web team to be the project manager (possibly Kyle?).
- Heidi Ullrich to identify the 3rd community member to be on the task force.
