Search the guide

Group Assignment Checklist

Deadlines and Hand-in boxes

You will need to upload one copy of the website for each of the units that grade the content directly on the website (see instructions in the next heading).

Please also make sure that you add a link to your website in the Brightspace comments.

First opportunity
Second opportunity

Instructions for creating deliverables

  • Deliver the actual website by using GitHub pages (see details in Part 1 of the guide).

  • A copy of the repository as a zip file must be posted on Brightspace (see links above).

    This is done by going to your GitHub repository and clicking on “Code” then “Download ZIP”. Please rename your zip file according to the convention below:

    coursenumber_academicyear_classnumber_groupnumber_assignmentname

    Example: PRJ4_2324_class2_group3_website.zip

Content of the website

The website should be structured to offer access to all the following information (which can be spread in one or multiple pages/screens, depending on students’ design choices):

  • A highly visual landing page
  • The brand’s vision and values
  • The 4/5 pieces of copy developed within the Content unit of the project.
  • Information about the brand’s products and/or services
  • Contact information and links to relevant social media
  • Material used for assessment, as part of the corporate page

Audience and Purpose

The website must be designed with your target audience in mind. As a showcase website, it must appeal to the clients of the brand. After visiting this website, future clients must be interested by the brand and willing to buy your products.

Justifications

Justifications for the different units should be delivered directly in the website, as part of a page titled corporate.html, which doesn’t need to be matched with your crowdsourcing audience.

You can create the justification webpage based on the template at buas-media-interactive.github.io/prj4-group-template

Assessment criteria

Please note that the assessment criteria below only cover the Production unit. Check the project brief for other units.

Pre-requisite: A link to a publicly visible GitHub-hosted website, a link to the repository, and a copy of the repository as a zip file are posted on Brightspace.

Deliverable Assessment criteria Weight Description of levels of attainment
Excellent Sufficient Insufficient

Elements assessed directly via

Website

 Visual qualities

25%

of production unit

 Information is grouped and hierarchized in a way that is outstandingly self-explanatory and that helps make sense of complex content. Content is grouped, hierarchized and clearly structured, with only few inconsistencies in terms of navigation and structure. The structure of content is either confusing, unclear and/or inconsistent.
Uses grids, margins, alignments, contrast and font sizes to achieve an outstandingly clean, professional and legible look and feel. Uses grids, margins, alignments, contrast and font sizes to achieve an clean, professional and legible look and feel. Page elements are not properly aligned, lack contrast, are difficult to read, and/or are inconsistent.
The website is designed with both desktop and mobile in mind, adapts to the affordances of different devices and makes the best use of screen surface at all sizes. The website is responsive and looks well designed at all sizes. It can be that either the mobile or desktop version is “leading” and looks better. The website loses functionality, is illegible and/or looks poorly designed at certain screen sizes.
The website uses a variety of visual elements and design principles in a complex and/or original way to communicate, reinforce the text copy and create a very distinctive atmosphere. The website uses a variety of visual elements and design principles to communicate, reinforce the text copy and create a branded atmosphere. The website makes limited use of visual elements and/or these visual elements add limited value to the message of the website.
Technical qualities

25%

of production unit

 All file management described in the guide are strictly adhered to, with all necessary assets located in correctly named folders and all unused assets removed from the final delivery. All file management best practices are followed with a maximum of 5 deviations from the guide, inconsistencies or unused files left in the repositories. More than 5 instances of bad file management practices that deviate from the guide.
Pages are technically complex and follow all good practices: use of appropriate semantic tags, headers, title tags, links to libraries, and proper code identation. Code contains no errors. Either the page is very technically complex but deviates occasionally from best practices or the page is very simple but follows all best practices. Code contains a maximum of 2 errors across the whole website when checked in the W3C validator. Code is either hard to read, deviates strongly from good practices and/or has many coding errors.
All images are properly resized and compressed for an optimized balance between image quality on one hand, and loading speed and sustainability on the other hand. The best format (JPEG, PNG, SVG) is selected based on the type of content. More than half of delivered image assets are optimized for loading speed and use the proper file format. No image is bigger than 1MB. A majority of images are not optimized and/or at least one image is bigger than 1MB

Elements assessed through

Justifications

 Website justifications

25%

of production unit

 Lists and justifies all design choices: the colour scheme (with colour codes), font choices, user interface elements (grids, carousels, menu organizations etc.), the organization of the navigation and content (e.g. how content units are distributed across pages) in detail, by using the vocabulary of (UX) design and relating all choices with insight about the target audience. Lists and justifies all design choices: the colour palette, font choices, UI elements, the organization of the navigation and content, with justifications and some use of UX vocabulary. Many design choices are absent and/or do not use the vocabulary of design in their justifications.
Outstandingly relates the design elements and their justifications with the purpose of the website as part of marketing, the vision and mission of the brand, and the elements developed in the lean canvas. Most design elements are at related to content from at least 2 of the other units of the course. Many design elements are not related to content from other units of the course.
Testing report

25%

of production unit

 Thoroughly describes a testing protocol that was conducted at a high level of quality, with participants that match the target audience, clear testing tasks and goals that include identifying whether the website fulfils its communication purpose. Testing is well described, with at least 4 participants and clear goals and tasks. Testing goals might slightly deviate from the communication goals of the website and participants might slightly deviate from the target audience. Testing is poorly described, or described in a way that shows that it is superficial.
Provides an exhaustive list of findings uncovered from testing, both positive and negative, grouped in a hierarchized and logical way in order to clearly indicate which issues have the strongest impact on the usability of the website. Provides a clear list of findings that are grouped in an actionable way. Findings are unclear, vague, poorly grouped and/or not actionable.
Provides a list of (potential) improvements that is clearly based on a critical analysis of findings by students. The improvements are explained with excellent clarity. Provides a list of improvements based on findings from testing. The improvements are based on students’ reflections and not only on testing participants’ suggestions. List of improvements is very short, superficial, and/or not clearly based on an analysis of findings.