Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloak

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

Adobe recording

Transcription

Action items

Toggle Cloak

Cloak
25 incomplete  Product team () to propose a method for producing artwork in the long run  26 incomplete  The website project team (, , ) 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 27 complete  The website project team (,  ,  )  to deep dive in the Correspondence page in next meeting 28 complete  to explain to Steve about the Correspondence Page and the PD page on the wiki 

...