MCOM 5321: Production of Digital Media Content

SEMESTER OUTLINE

Week 1: Jan. 15 — Jan. 19: HTML for Formatting

Weekly Goals

  1. Orient yourself with the tools we'll be using in class.
  2. Recognize the utility of learning HTML and CSS
  3. Become familiar with basic HTML tags.
  4. Know how and when to use basic HTML tags including: html, head, title, body, paragraph, headers, lists, tables, link, image, and formatting such bold and italics.
Resources and Assignments

Learning Resources

1. Read McFedries (introductory, less technical) Ch. 1: Getting to Know HTML and CSS

2. Watch Svekis Chapter 1 "Introduction to web development and "How to use this course" (est. 9 min)

3. Watch Svekis Chapter 2 starting with "Introduction to HTML" through "More HTML text formatting" (est. 60 min)

4. Read through the W3 Schools from HTML Home through (and including) HTML Lists.

Tasks for the Week

  1. Use the Blackboard link to join Microsoft Teams by Wednesday (1/15) evening.
  2. Complete the W3 Schools HTML exercises from "Attributes" through (and including) "Lists" by Monday (1/20 at 11:59pm)
  3. Post at least one question to Teams asking for clarification on one of the HTML topics covered so far by Monday (1/20 at 11:59pm).

Week 2: Jan. 20 — Jan. 27: HTML5 for Structure

Weekly Goals

  • Learn the difference between HTML for formatting text and HTML for structuring pages
  • Learn the basics of "semantic" html
  • Successfully construct a webpage that opens in Google Chrome and renders your markup properly.
Resources and Assignments

Learning Resources

  1. Begin by practicing your HTML formatting from last week. (est. 5 min)
  2. Learn about divs and spans as organizing tags (est. 4 min.)
  3. Read about "semantic elements" in HTML (est. 5 min) and practice using it.
  4. Continue working toward building a page by watching the videos from "place holder content" through "HTML tables".

Supplemental Resources

W3Schools
Semantic HTML quick guide
Understanding HTML file paths
Videos
Setting up new projects in Brackets

HOT TIP: Files and folder names should always be lowercase without spaces.

Notice that all files and folder names are lowercase and contain no spaces. This is a convention of web development that you should always stick to. Web browsers are case sensitive. The browser rendering your code interprets things literally. As far as it is concerned, the files mywebsite.html and MyWebSite.html are two different things. And mywebsite.html and mywebsite.HTML are also two different things. Using all lowercase will make your life easier becuase you don't have to remember if you've used uppercase. The browser also does not understand spaces in filenames. When it sees a space it thinks, "this is a whole new thing!" and stops parsing the thing you gave it.

Tasks for the Week

  1. Create a folder on your computer called 5321web and then, inside this folder, create another folder called week02
  2. Open Brackets and, in the menu, go to File ---> New
  3. Save this file as index.html in your "web5321\week02" folder
  4. Create another new file and save it as thirteen-one.html

Your assignment this week comes from "a client" that asks you to format two pages from a U.S. history textbook for use on the web. It's good practice for using the HTML tags you've learned during the first two weeks and also thinking about how a web document should be structured.

  1. Download the week two file and unzip it (instructions). You'll see it has multiple files inside and is disorganized (on purpose). Start by opening README.txt and look at the "client's request".
  2. Copy the image folder into your own week02 folder and copy/paste the text from the two documents into the HTML files you made.
  3. Read through the text and look for any comments {{inside of braces like this}} for specific instructions. The Table of Contents will be oyur index.html page.
  4. Markup the pages with HTML!
    • Make sure to include html, head, title, and body tags in your documents.
    • Format the document using the tags you learned. You will need to use all of the following: paragraph, first and second level headers, unordered and ordered lists, a table, links, image, strong and emphasis.
  5. When you're finished, zip up your new week02 folder (instructions) and upload the .zip file to the Microsoft Teams dropbox (due Mon. Jan. 27th by 11:59pm)

Week 3: Jan. 28 — Feb. 3: HTML5 Review

Weekly Goals

  • Confidently use the basics you learned during the first two weeks
  • Understand the difference between "block" and "inline" elements
  • Recognize where and how to use HTML5 semantic elements to organize your page
  • Build a six-page, self-contained website that expands on the week 02 activity
Resources and Assignments

Learning Resources

Due: Exercise #1

You will be expanding on the textbook formatting with additional page that give you more practice at formatting.

Read all of the instructions before starting!

  1. Duplicate your Week 02 folder and rename it Week 03. This way you have a backup.
  2. In your new Week 03 folder, go through my feedback and update your code [this video will help you stay organized]
  3. Download this week's files and copy them into your new folder alongside last week. Make sure your table of contents file is named index.html
  4. Watch this week's assignment example/explanation video.
  5. Look at the example.html page you downloaded and follow any directions you see in the comments.
  6. Using your page for Chapter "13.1 An Awakening of Religion and Individualism", structure the content of that page based on the "example.html" file you downloaded. (Don't worry about bolding key words this time.)
  7. Then do this for each of the textbook chapters. It will seem tedious but it's good practice.
    Every page should contain the following semantic elements:
    • <header>
    • <nav>
    • <main>
    • <article>
    • <section>
    • <footer>
  8. When you're finished all five chapter, you should then fill in the URLs for the links that go between pages.
  9. Open your index page in your browser and make sure you can navigate back and forth between all of the chapters with the navigation links!
  10. ZIP your new week03 folder for submission.

Exercise #1 is due to the Teams dropbox Monday Feb. 3rd by 11:59pm

Week 4: Feb. 4 — Feb. 10: CSS3 for Styling

Weekly Goals

  1. Demonstrate understanding of cascading style sheets (CSS) by styling standard HTML elements and creating custom classes
  2. Recognize the value of external stylesheets and how to properly include them in a website
Resources and Assignments

Learning Resources

Tasks for the Week

You should be able to complete the CSS practices exercises from "Selectors" through "Tables". Make sure to ask at least one question in Microsoft Teams.

Week 5: Feb. 11 — Feb. 17: Project #1

During this week, you will be constructing a four-page website based on a product or service that you like. Your job is to design the product a new website that focuses first and foremost on a solid structure, proper use of HTML elements, and that is visually styled using CSS.

This site will serve as the foundation for the next couple of weeks, when you will continue to iterate on it.

This is the first of three 30-point graded projects this semester.

Resources and Assignments

Project Process

  1. Decide on the product or service
  2. Go steal content from that product's site (or anywhere it may be available)
    • Use existing copy when available, write new if needed
    • Collect images for later use
  3. Organize your content into four pages: index, product details, customer reviews, and purchase.
  4. Build your home page first and worry about the other pages after
  5. Format these pages properly using HTML
  6. Apply styles using an external CSS file
  7. Run your code through the W3 validation service to catch any errors [video explanation]
  8. Zip up your folder and submit it to Teams

Project Requirements

  • Four HTML pages linked together with a menu.
    • All the pages should use the same HTML structure
    • All images in an images folder
    • Documents must use at least: <main>, <header>, <footer>, <article>, <section>, <nav>
  • Required HTML elements:
    • paragraph
    • headings (at least h1, h2, h3)
    • table
    • ordered list
    • unordered list
    • <nav> block
    • links out to other websites that open in a new tab
    • links within your website
    • five images including one figure with caption
    • one YouTube video embed (if there isn't one avaiable, just choose a similar product as a placeholder)
    • strong/emphasis where appropriate
    • at least one use of <span>
  • Use an external stylesheet
  • Create four custom classes as you deem necessary

The ultimate goal is to show me that you understand document structure and visual styling and are ready to move onto page layout. I'm not particularly interested in the content you choose, just your code!

Submit to Teams by Feb 17th at 11:59pm.

Week 6: Feb. 18 — Feb. 24: Layouts and Usability

Weekly Goals

  • Understand the fundamental principles of usability when applied to the web
  • Be able to recognize page layouts and visual design choices as hierarchies of behavior
  • Critique websites that do not adhere to principles of interface usability

This is a reading week with a reading response exercise (12 points) due Sunday to Teams.

As author Steve Krug writes in the preface, the original edition of this book was quite out of date with regards to its examples. Even the 2013 edition that you're reading seems old if you're just looking at just visual design alone. But the core of the book—designing with the user in mind—is perennially relevant.

It looks like a lot of reading, but honestly it goes much more quickly than the estimated reading time on the website indicates. Your goal is to internalize fundamental principles of usability so that not only can you make stuff with that in mind, but recognize examples that either demonstrate or violate these principles.

Resources and Assignments

Learning Resources

Read Krug: Preface, Introduction, Chapter 1–7, Chapter 10-13.

Then read this article from Smashing Magazine (sponsored by Adobe) about using grid layouts on the web.

A number of y'all asked about colors, so I recommend reading "A Simple Web Developer's Color Guide" by Laura Elizabeth on Smashing Magazine. We'll use it more in future weeks.

Due: Exercise #2

Seek out two websites—one that does navigation and user experience well and one that does it poorly—and write 300 words a piece about them using Krug's principles. Paste the link to the site and your commentary into the #help with design channel in Teams by Sunday at 11:59pm. Then reply to one other person's link in Teams by Monday at 11:59pm.

Note: Please do not use Amazon, Apple, TTU.edu, or social networks (including Pinterest) as your examples. Also, don't use web interfaces for applications like Spotify, Netflix, or similar services.

Week 7: Feb. 25 — March 2: Designing Layouts with CSS

Weekly Goals

  • Understand units of measurement for screens
  • Understand the CSS box model
  • Manipulate HTML elements using the layout capabilities of CSS
  • Recognize (and critique) the "holy grail" layout
  • Revise your Project 1 Product websites using the "holy grail" layout
  • Determine an appropriate color scheme for your site
Resources and Assignments

Learning Resources

The core of this week's instruction comes from McFedries who has a great chapter on layouts. We will be using this book for the next two weeks. We will be using the "float" method (as opposed to flexbox or grid).

Chapter 11 Learning Page Layout Basics

Svekis, unfortunately, doesn't have a great demo for page layouts. The following videos will be helpful to see learn some of the code behind McFedries, though.

  1. Measures and Properties
  2. CSS Spans and DIVs
  3. CSS Float Images
  4. CSS Float Elements
  5. CSS Box Model

Starting next week, we'll be looking at how these methods for doing layout will allow you to adapt your website for different sized screens.

Additional Resources

Due: Exercise #3

The goal of the week is to take your Product site from week 5, revise it with the feedback you received, and employ the "holy grail" CSS layout to make it function and look more like a modern website.

(Note: we will use another )

  1. Duplicate your Product site into a new week07 folder.
  2. Make revisions based on the feedback you received.
  3. Make revisions to content organization based on the Krug book
  4. Apply the "holy grail" layout to your site using CSS
  5. Choose a color palette for your site based on the Color Workflow and include those colors in your css
  6. Make sure everything looks nice and functions properly!

When you are finished, zip the week07 folder up as usual and submit it to the Assignment dropbox on Teams.

Week 8: March 3 — March 9: Responsive Design

Weekly Goals

  • Understand the importance of responsive web design
  • Recognize the difference between float, flexbox, and grid approaches to layout
  • Learn the utility of color-blocking a layout during the design phase
  • Construct a color-blocked demo website using flexbox
Resources and Assignments

Learning Resources

  1. Watch Kevin Powell on Floats, Flexbox and Grid (26 min)
  2. Read the Interneting is Hard tutorial on using flexbox
  3. Website not working? Download this PDF and the image files.
"How To"

What's Due?

Follow the instructions on the Interneting is Hard tutorial and complete the example. Make sure to test how it looks on different devices using the inspect tool. This is an ungraded activity but will demonstrate that you're prepared to work on project #2.

When you are finished, zip the completed responsive-design folder and submit it to the Assignment dropbox on Teams.

Weeks 9-11: March 10 — March 30: Project #2 Spring Break

Weekly Goals

You are beginning a three week development period to build a mobile-first multipage portfolio that uses flexbox to be device-size responsive.

To make things a little interesting (and because you can always go back in and fill it with real information later) you will be creating a "fake" portfolio of fictional accomplishments in your dream job. Have fun with it!

Assignment Description
Your website will consist of three pages:
  1. Biographical sketch (index.html)
  2. Neatly formatted resume or curriculum vitae
  3. Photo gallery (with captions) page featuring your six greatest accomplishments
Requirements:
  • Responsive design for phones, tablets, and web browsers
  • A flexbox structure that expands to the Holy Grail on wider screens
  • Horizontal navigation that collapses to vertical (or "hamburger icon") on narrower screens
  • one external CSS file for all HTML elements used
  • A resume/cv formatting using definition lists
  • Images and video that support your fictional accomplishments

By the end of these weeks, you should be able to:

  • Build a full mobile-responsive website using flexbox and @media queries
  • Understand the value of paper sketching
  • Use the inspector to test your site's responsiveness
  • Recognize the importance of asking your peers for help to solve problems

Let's Get Started

  1. Watch the paper sketching video How to wireframe a website | CharliMarieTV (YouTube 04m50s)
  2. Explore flexbox starter templates (so that you can use one!)
  3. Using definition lists

Tasks for Week 9/10

  1. Determine your fictional dream job and outline your accomplishments
  2. Paper sketch your site
    • Begin by imagining the mobile version first
    • Which elements are consistent across all pages?
    • What will need to change on the different pages?
  3. Begin to color block-out (placeholder content only) your index page using a similar method to the Interneting is Hard flexbox exercise
  4. I highly suggest you paste your color-blocked index.html and style.css into a codepen and submit this work-in-progress to the #sharing your work channel in Teams by Monday March 30 at 11:59pm. Submissions received before the deadline will be reviewed more quickly to give you more days to work on the final version.

Tasks for Week 11

  1. Finalize your layout
  2. Collect content and write copy that will go on the site
  3. Determine your color palette
  4. Complete the build of your site
  5. Submit zip file named "lastname-portfolio.zip" to Teams Assignment by April 3rd at 11:59pm.

Weeks 12/13: March 31 — April 13: Designing Interfaces

Goals

  • Build on the foundations of Don't Make Me Think within the context of mobile apps
  • Recognize the importance of designing with an audience in mind
  • Recognize that users are human beings and not just an abstract concept
  • Understand the significance of organizing information

Learning Resources

Read Chapter 1. Designing for People and Chapter 2. Organizing the Content: Information Architecture and Application Structure from Designing Interfaces, 3rd Edition by Aynne Valencia-Brooks, Charles Brewer, Jenifer Tidwell

(Helpful tip: you can download the O'Reilly app for iOS and Android and read the chapters in offline mode.)

Due: Exercise #4

Using the structure of the two chapters from Designing Interfaces, analyze an app you use regularly (excluding social media apps). Put yourself in the shoes of the designers who built the app to answer the questions of context and goals. Then, go through the list of patterns and discuss each. (If a pattern does not apply, explain why.) 600–800 words.

  1. Context: Who is your audience?
  2. Goals: What are they trying to do?
  3. The Patterns: Cognition and behavior related to interface design
  4. Information Architecture: How is information organized and categorized to be understandable?

Once you have finished, post your analysis and at least two relevant screen shots (annotated with arrows/circles/highlights or text to help us see what you're referring to) into the #design-analysis channel in Teams. Due Tuesday April 14th by 11:59pm.

Week 14: April 14 — April 20: Tools for the Design Process

Weekly Goals

  • Recognize the significance of the prototyping process
  • Survey prototyping software
  • Consider the utility of HTML/CSS as a prototyping tool

Learning Resources

What's Due?

Nothing this week.

Week 15: April 21 — April 27: App Design

For the last weeks of the semester, you will be creating a mockup of an app the demonstrates how a user would go about accomplishing a single, specific task.

Weekly Goals

  • Employ fundamentals of user experience and interface design into a directed critique of an existing app.
  • Identify areas for improvement

Learning Resources

Mobile Interfaces from Designing Interfaces, 3rd Edition by Aynne Valencia-Brooks, Charles Brewer, Jenifer Tidwell

What's Due?

This project will be based the interface and interactions readings you've completed over the past couple of weeks. You will be again critiquing an app that you have used that hasn't met your expectations or needs in some way. You can either change some aspect of an existing task or create a new one that solves a problem. (Please do not choose a shopping app or any other type of "add to cart" workflow.) This should be different from the app that you critiqued in week 13.

To begin, spend some time figuring out a specific task that illustrates what you would like to improve about the app. Think about how your interactions cause the interface to change.

Ex: Do you go to the next page/screen? Does new information get called into the current screen you're on? Does a menu slideout or a date-picker pop-up? Do you pass information into the next page?

Your goal is to identify five to six "steps" in an interaction. Each step should be represented by a screenshot you can take while using the app. For this week, you should take the screenshots and annotate what the user is doing in each while adding your critique. (An easy way to do this would be to drag the screenshots into a Word document and type in your annotations but, really, whatever works for you.)

Exercise #5 is due Monday April 27th to the Teams Assignment Folder.

You can look ahead to next week for the assignment itself.

Week 16: April 28 — May 10: Development Period

Final Project Description

Use a sequence of HTML pages to demonstrate the new sequence of interactions you propose to improve the app you critiqued during Week 15.

You do not need to do all of the work of re-creating the interface of the existing app. Instead, this will serve as a mockup that allows user to click from one screen to the next according to the designer's instructions to pretend how it would work (a method known as a Wizard of Oz demonstration).

You will be providing instructions of what the user (aka: me) should click on to move through the app.

In this kind of demo, you build actual webpages but don't implement every part of it. For example, you would include the HTML element for a search bar if the user should be searching for something, but when they click the icon, it actually just takes them to the next webpage that has the results hard-coded on the page. The search icon would just be <a href="step2.html"><img src="searchicon.png"></a>

You do not need to recreate the whole of the app. I encourage you to use parts of screenshots of the original app and to colorblock the layout. HTML/CSS, in this case, is just a prototyping method that lets you quickly build something interactive that's properly sized for a mobile device.

You will be using a skeleton project that provides the visuals of a phone interface as a constraint for your design. You will be designing for this single display size (fixed width but allowed to scroll). Download the iphone interface .zip file (and delete the placeholder content)

For example the user starts on the home screen of Password Manager app and wants to update the email address used to login to a few of their favorite websites:

  1. index.html → user sees a huge list of logins but wants to change three of them
  2. step2.html → shows how the search filter will bring up a login and add that there's a ➕ icon to add it to a "saved" list
  3. step3.html → skip to the third search; "saved list" now has three items in it and an "edit" button
  4. step4.html → page showing batch editing tool
  5. step5.html → confirmation page showing changes

Project #3 Due May 11

Submit to Teams Assignment folder by 11:59pm May 11th.