ah teaches web design & development (The Interwebs lecture)
An overview of the course, some fundamentals when thinking about design on the web, and an introduction to semantic markup. Lecture slides will be made available on the day of the lecture (Sept 15).
Your teaching team
Contacting your instructors
A friendly how-to
Andrew and Mohammadreza are available via:
Please send an email or message indicating you'll be attending.
Please allow up to 2 business days for responses.
We do not provide design critique via email or chat. Please arrange a meeting or attend office hours for design critique.
To make our responses faster, please include the following in your email:
- Your full name.
- The course number (IAT-339).
- A clear question.
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.
If you are ill, stay home. You are able to watch the lecture recording later, and follow-up with Andrew or Mohammadreza 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 class.
The lecture+lab experiment
We are testing out this lecture+lab combo this term.
It is meant to provide more direct instructor engagement as well as more supported work time. Please let us know if things are going wrong.
What to expect
Our class will involve a number of activities:
- Explanation of theory and practice
- Code tutorials
- Open work time
Knowing this class will be unable to move from Friday evenings, what can help make this class a more palatable use of your Fridays?
A reminder that this course expects about 2-5 hours of work outside of class time.
If you ever have concerns with workload please email Andrew.
Our main course-site
Andrew opens up Canvas and briefly introduces it here.
- Process — 10% (Individual)
- Company — 30% (Group)
- Portfolio — 30% (Individual)
70% of your grade.
A quick note
Project 2 (Company) will be done in groups. Contracts, reflection and/or evaluations will be used to clarify expectations and outcomes between teammates.
Remember, you are responsible for your own work.
Readings are available entirely digitally.
Canvas has PDF copies of all readings.
There are seven reflections available, and you are only required to complete two. Reflections are completed within the class time and submitted before the end.
You may complete up to three reflections and have the lowest grade dropped.
10% of your final grade.
Details of the coding quiz will be discuss closer to it, but it typically focuses on your ability to think through a problem with code.
10% of your final grade.
Coding and other exercises
Code exercises are practice for the web-coding you are doing in the course.
10% of your final grade.
- You can use online resources, course materials, your TA, and lab-mates for support.
- You must cite any knowledge that is not yours in a comment in the code.
- If work has been copied without citation the exercise grade will be zero.
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.
You are welcome to use AI tools unless specified in a project, quiz or exercise brief, and with the following conditions:
- You must state how you generated the result you are working with (i.e. prompt, which tool, etc)
- You must develop the idea further — an AI generated result cannot be your final submissions
- You must be able to make an effective case for why the AI tool enhanced or improved your work
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 with me, you may find the first couple weeks a bit repetitive. This is intentional.
Do keep track though, as things may have changed.
Prepped and ready to go
Available on Canvas are links to programs for your first 'web toolkits'. They should contain:
Firefox or Chrome
The developer tools in Firefox and Chrome are reasonably easy to access and have the features we need for the term.
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?
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.
See you in ten minutes.
Please make sure you have:
- VS Code (or similar code editor)
- Firefox or Chrome
- Today's tutorial starter kit
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.
We want to pick the most appropriate HTML element to define the content, not the most stylistically appropriate element.
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.
Markup should help us understand the content.
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.
Time to code
Please open up this week's "starter package"
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.