The due date of the combined 4835 + 4840 final assignment is the day of your team presentation.
The project will be a website promoting or supporting your PWA project. On the same day that you present your PWA, your team will also present this website.
Here is a discussion of some outstanding previous student group projects.
Technical Details
- The site must be at a live URL.
- It must be fully responsive.
- It must be tested on actual devices.
- It must use Grid and/or SASS.
- It must use a WordPress theme written by the team.
Child themes are not sufficient. - All code must be well-commented and organized.
- It must not overuse plugins.
Content Details
Important: in keeping with the idea of content management, it must be possible for someone without technical knowledge, other than current competence in WordPress, to be able to enter, modify or update site content.
Someone from the Marketing department or Human Resources should be able to publish on an organization’s website without having to beg a developer for assistance, in other words.
Additional Content Details
- All significant text and image content must be placed in the site via the WordPress dashboard.
- All text must be written by the team. No lorem ipsum. No copied text.
- All art must be created by the team, or come from open sources.
- If open sourced imagery is used, links to each of those images must be put in a page which has a link in the footer of the site. The text of that link must be image credits.
- The source website must explicitly state that your usage is permissible under its license terms. Your usage here is personal/educational, not commercial.
Hand In Procedure
The project must be handed in by the team project manager to the Group Project hand-in folder in Brightspace WMDD4840.
Included in the files handed in by the project manager must be the following:
- a Duplicator archive of the live site: test that it is installable.
- a file named team.txt listing team members and their positions.
- a file named url.txt containing the live url of the project.
Peer Assessments
Finally, each team member must write a single page assessing the contribution of each member of the team, including themselves.
Each team member will separately hand in their team assessment to the group project folder in Brightspace.
This file must be a text file named peer-evaluation-your-name.txt. If you need to include images in your evaluation, you may hand in a pdf (named the same way but with a pdf extension).
No Microsoft Word files please.
Things I Will Look For While Marking
Portfolio-Ready Text:
Get help with proofreading, if necessary. If you’re in doubt about how well-written a piece of text is, get classmates to look over it, or talk to me. Spellcheck. Grammar check. Do not leave this to the last minute.
Responsive Strategy:
Does the site work regardless of device? Be sure to test your designs on real devices.
UX:
Is the site layout sensible? Is it consistent? Is there a hierarchy of content implicit in its organization? Does the UI of the site follow common conventions?
Typography:
Does the typography support the content? Does it contribute to the brand? Is it appropriate for the type of site? Is it easy to read at all screen widths?
Color:
Does color add to or subtract from the message of the site?
Accessibility:
Is your site accessible to as wide a range of people as possible? Are there barriers to people with weaker vision or color deficits, for example?
Images:
Do images help tell the story of the site? Are the images sized appropriately? Even though we often use images in exercises that are bigger than they should be, do this assignment as a real, production site. Here is a list of places you can find open source images.
Alignments:
A significant part of design is making sure things align. Make sure that this is taken care of. Few things make any kind of design work look sloppier than bad alignment.
Code:
Does the HTML and CSS validate? Is the code well-organized, using SASS partials, variables, nesting, ete? Is it concise? Would it be easy to revise? Is the code commented? Is it semantic? Are class names logical and flexible? Would it be easy for new team members to understand how you’ve built the site?
Browser and Device Support:
The site should work well in the latest browsers, on desktop or mobile devices.