Web Tutorials

<yatil> https://www.w3.org/WAI/EO/wiki/EOWG_F2F_November_2016/Tutorial_Discussion

Eric: ... Created tutorials update page and done the updates from comments, mostly from Shadi
... open issue is the basic styling section. I suggested to move it to a separate page, but not eveyone agreed. Do we want to have a wireframe of the carousel to provide a throuogh line based on wireframing.

Sharron: +1 to wireframe

Robert: Would it be a working example, fully functioning with all of the recommendations? Or a static wireframe?

Eric: I have envisioned a static example.

Shadi: What is the purpose of the wireframe, what exactly are you suggesting?

Eric: Images of the components of a working carousel as a point of reference for the person reading the tutorial. On the concepts page as an intro.

Robert: Or on the structure page.

Eric: Feedback has been good, quite constructive.
... leaning toward having a separate styling page although it could be interwoven.

Shadi: I would suggest that if we go with a wireframe (which I like as a way to point to different parts) it be broken out separately after the three main sections - Working Example or something

<yatil> https://w3c.github.io/wai-tutorials/carousels/full-code/

Shadi: wireframed illustration and then working example, and then source code

Chris: My experince says styling is a separate topic and will be attendedby a different person. It makes sesne to have it on a separate page.

Shadi: OK I am coming more to that point of videw. Just want to make sure we don't go too far away from the core lesson in accessibility.

<shadi> +1 to that suggested resolution

RESOLUTION: Eric to propose a separate Styling page that is very specific to Carousels and accessibility.

<rjolly> +1

Sharron: +1

<yatil> +1

<Chris_Langston> +1

<shadi> +1

Shadi: Like the way the navigation highlights the content pages with numbering. Anyway to accent that even more?

Eric: Maybe make the pattern clear to the redesign group and not spend the time to tweak designs right now.
... good, I have made my notes, I think this Tutorial discussion can be concluded, next is page Structure.

<yatil> https://www.w3.org/WAI/EO/wiki/EOWG_F2F_November_2016/Tutorial_Discussion#Page_Structrure

Eric: At this point, we have done less organizational thinking so we can look at the structure of this. Shadi has suggested that we break this up, and has posted to the wiki.

<shadi> https://www.w3.org/WAI/EO/wiki/EOWG_F2F_November_2016/Tutorial_Discussion#Proposal_from_Shadi_.28for_lively.21_discussion.29

Chris: I have concern about the potential for confusion between In-page navigation and site navigation. People may not make that distinction.

<shadi> +1 to quick turn-arounds

Chris: but I think it is a good idea to break it up and allow people to find and use what they need.

Eric: and it would allow us to complete short focused tutorials more quickly.
... not sure that this is the right approach to do that, especially because we have the three topics that are so similar. Maybe re-think how we refer to them.

Shadi: Agree and the idea is to cross reference tutorials that suport each other.

Chris; How do these relate to the actual guidelines which always come up first in search?

Eric: if we institute smart search, it may be better.

<shadi> +1 to more wireframes

Chris: When I raise a concern for one or the other of the designer/developer group, the other side checks out. I worry about how these tutorials try to serve both masters and could alienate the other side of this equation.

Eric: Yes it is a hard thing to do.

Sharron: and on this topic, it is not as clear which belongs to what camp.

<shadi> https://www.w3.org/WAI/gettingstarted/tips/designing.html#use-headings-and-spacing-to-group-related-content

Chris: Have had success with serving same content to different groups with different landing pages to make it seem customized.

Eric: Something for consideration as we redesign site. For the current wireframe however, we might want to explore it on new tutorials first and then add it to the older tutorials in the future.

Shadi: Do we know anyone who can help?

Robert: I am willing to help.

RESOLUTION: Page Structure tutorial will be broken into smaller, more specific units.

Sharron: +1

<yatil> +1

<rjolly> +1

<Chris_Langston> +1

<shadi> +1

<Brent> +1

Sharron: and what do we want those smaller, more focused elements to be?

Eric: it is here https://www.w3.org/WAI/EO/wiki/EOWG_F2F_November_2016/Tutorial_Discussion#Proposal_from_Shadi_.28for_lively.21_discussion.29

<shawn> be prescriptive - not descriptive:

<shawn> "most websites have a region" -> "if your website has a region, then..."

robert: expose the code itself on a separate page

This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/an/on/
Succeeded: s/atteneded /attended/
Succeeded: s/especailly/especially/
Succeeded: s/eric @@@@/we might want to explore it on new tutorials first and then add it to the older tutorials in the future./
No ScribeNick specified.  Guessing ScribeNick: Sharron
Inferring Scribes: Sharron
Present: Chris Eric James Robert Shadi Sharron Shawn(11:00)
Found Date: 14 Nov 2016
Guessing minutes URL: http://www.w3.org/2016/11/14-eo-minutes.html
People with action items: