Improving the workshop: Coaches Notes

[gsambrotta]

• Add Html Comments right to the start of the workshop (people want to keep track of what they are doing)
• Explain "path/to/your/file.css" Most people saved file in the same directory but tried to write the whole path anyway. (lot of people copied the whole folder path from your computer desktop i.e. "C:/Users/nameuser/Desktop/filename.html") -Very beginning we need to explain how open a file, where to save, how to open the file in the browser.
• Charset: Show them what it does. (for example umlaut without charset, show what's the output and go on with the explanation)
• In the css-section, when we explain how to style the image, link back to the html part(in case they jump thought the material)
• Explain better the inspector tool. (Maybe later?). Lots people were confused from it.
• FF inspector: Network part doesn't work properly
• Don't call the div #page-title. People confuse it with actual title in the head.
• Tell people to not click on the address bar and press enter, but rather refresh
• People have problem to understand the fluid nature (width in %) of the portfolio template. < section > jumps below the < aside > when the browser window is to narrow

[mbesser]

Don't call the div #page-title. People confuse it with actual title in the head.

We could use no IDs at all. Only classes. Keep it as simple as possible and introduce best practices in the very beginning of their learning :grin: (disclaimer: i'm not dogmatic in the id-vs-class issue, i just think there is no need to use an ID in that case)

[projectgus]

Thanks @gsambrotta & @mbesser. Really appreciate getting feedback from what worked and didn't work in the workshop sessions. :)

I've had a go at addressing most of the things you mention. Remaining are:

"People have problem to understand the fluid nature (width in %) of the portfolio template. < section > jumps below the < aside > when the browser window is to narrow"

Haven't gotten to the portfolio chapters yet (someone else may have the time!)

Also haven't gotten to @mbesser's comment on ids vs classes. I fundamentally agree, but classes & ids aren't really introduced until the first portfolio chapter. I think this would probably be the best place to explain why you'd want to preference classes over IDs (better there than in the opening chapter when id="first-heading" - formerly #page-title - is just a simple example of an HTML attribute, before we've talked about CSS at all.)

Will be interested to hear what the others think as well. Thanks again for the feedback.

Angus