Your teaching team

Wave here.

Contacting your instructors

A friendly how-to

Andrew and Alfredo are available via:

• Email at ac.ufs@h_werdna and ac.ufs@namrehs_oderfla
• Our Discord course chat (sign-up on Canvas)

Office hours

Please send an email or message indicating you'll be attending.

Email rules

Chat conduct

Please treat our online interactions the same way you would in-person interactions.

If you have concerns about anyone's conduct at any point, please direct message or email Andrew.

Illness policy

If you are ill, stay home. You are able to watch the lecture recording later, and follow-up with Andrew or Alfredo to arrange an alternative time for critique.

If you will be ill for a prolonged period of time (more than a week) please email Andrew to arrange accommodations.

If one of the teaching team is ill, we will notify you via Canvas and course chat before 8:30am on the day of the lecture or lab.

Lectures

What to expect

Our lectures will involve a fair bit of talking, but not always by your instructor. Lectures include:

• Explanation of theory and practice
• Discussion
• Code tutorials

Labs

What to expect

Labs will be some activities but a lot of critique. It is your opportunity to get project feedback.

Workload

A reminder that this course expects about 2-5 hours of work outside of lecture and lab times.

If you ever have concerns with workload please email Andrew.

Canvas

Our main course-site

Andrew opens up Canvas and briefly introduces it here.

Projects

1. Process — 10% (Individual)
2. Company — 30% (Group)
3. Portfolio — 30% (Individual)

70% of your grade.

Readings

Fee-free!

Readings are available entirely digitally.

Canvas has PDF copies of all readings.

Quizzes

Those terrifying things

Reading reflections will be taking place for reading quizzes.

There are seven reflections available, and you are only required to complete two. Reflections are due before the following lecture.

You may complete up to three reflections and have the lowest grade dropped.

The coding quiz will be discussed closer-to.

20% of your final grade.

Group Work

A quick note

Project 2 (Company) will be done in groups. Contracts and/or evaluations will be used to clarify expectations and outcomes between teammates.

Remember, you are responsible for your own work.

Coding and other exercises

Code exercises are practice for the web-coding you are doing in the course.

10% of your final grade.

Exercise rules

1. You can use online resources, course materials, your TA, and lab-mates for support.
2. You must cite any knowledge that is not yours in a comment in the code.
3. If work has been copied without citation the exercise grade will be zero.

Plagiarism

This course has a zero tolerance policy for plagiarism on projects. If you are found presenting work that is not your own or resubmitting old work without notice, you will receive a failing grade on that project. No exceptions.

Late or problematic submissions

Late submissions receive 10% per day late.

Problematic submissions — i.e. we can't open the URL or the wrong files were submitted — receive an immediate 20% off plus late penalties on the resubmission.

Concerns with grades

Please notify Andrew of any grading concerns within 10 days of the grades being released. This can include just getting some further feedback and/or wanting to have something regraded.

Course overview questions?

If you have any questions that linger about the course overview, please feel free to email Andrew or ask during our lecture time.

The ever-changing demands of the web

Oh, how things change!

Our goal here is to give the theory, fundamentals of coding for web and an understanding of how to develop your skills beyond this course.

This course is biased towards building accessible and fully responsive websites.

IAT-235 and IAT-339

For those students who have taken IAT-235 more recently, you may find the first couple weeks a bit repetitive. This is intentional.

Do keep track though, as things may have changed.

Web toolkits

Prepped and ready to go

Available on Canvas are links to programs for your first 'web toolkits'. They should contain:

• Cyberduck (an FTP client)
• Google Chrome (a web browser)
• Visual Studio Code (a code editor)

Google Chrome

Why?

Google Chrome happens to be a relatively standards-compliant browser, and hence we have focused our interests on using it.

Coding applications

VS Code, Atom, Sublime Text, Bracket, Notepad++, etc

We are working with code-only applications in this class, as you need to understand the code to be an effective web designer.

I will be teaching using Visual Studio (VS) Code.

No Illustrator, Photoshop, Figma, or Sketch mockups permitted

We will not critique designs that use mock-up tools. We are going to work purely in-browser for when we start designing and critiquing things.

This is to get you into the habit of working within the medium.

No frameworks until the final project

For P1/P2, you are required to generate your own code. In the final portfolio project, you will be allowed to work with existing frameworks should you so choose.

This is to ensure you are practicing the development.

Why no React, Angular, etc?

Even if working with React, Angular (and other JavaScript libraries or frameworks) you still need to understand HTML and CSS to accessibly define the content, and style it.

I recognize there is more demand for JavaScript, but we will not be able to go into significant depth within this course.

The Document-Object Model (DOM)

Our standard in delivering HTML

This week you will be building your first HTML pages, this involves the DOM, which put simply is a collection of objects (ie. navigation, headings, paragraphs) that resemble the document it is modelling.

Semantics

We want to pick the most appropriate HTML element to define the content, not the most stylistically appropriate element.

Semantic markup

Telling the computer the pieces

HTML elements are (most frequently) comprised of an opening, and closing tag — i.e. <p></p> — using triangle brackets and a forward-slash to denote that they are HTML elements and not content.

Oops, this code did not quite load. Please view it at https://codepen.io/andrewhaw/pen/cd0509d108d9292b031bc4b78d14a596

Semantic Markup

Markup should help us understand the content.

Oops, this code did not quite load. Please view it at https://codepen.io/andrewhaw/pen/cca86d1438b4958efddeb5178290d02b

Common Coding Errors

Since we will be starting some scripting this week, please keep an eye out for:

• Typoess: This is handz downe teh most commmon prublem.
• Forgetting brackets: Not ending or closing an element will lead to
• Forgetting to save: The file won't be able to update if not saved.
• Files and folders matter: The naming of files and folders (and where you put them) is very important.

Having coding concerns?

Let us know!

Let us know sooner rather than later that you are having concerns with coding.

We can often answer code questions in the chat as long as you provide a link to the webpage.

Why We Style Guide

Style guides help us to:

• Document our design
• Test cross-browser
• Avoid duplicates
• Create a common language
• Work in teams

Mailchimp Style Guide

Let's take a look at the The MailChimp Style Guide.

Break-time

Runaway! Runaway...

See you in five minutes.

Please make sure you have:

• VS Code (or similar code editor)
• Google Chrome
• Today's tutorial starter kit

Next week's lecture

Styling the Webs

Thinking about our websites as modular components and the fundamentals of styling websites.

Lecture recordings will typically become available the day after the lecture.