Standards for Deliverables
Throughout our time together I will ask you to follow some basic standards for your deliverables.
These include such as using consistent padding and margins, max amount of words per line, font size + leading, naming conventions, etc.
Generally speaking, these apply to design, digital and development courses. I will explain all of them.
Please assume these are always in effect, unless specifically stated otherwise by me.
The list is updated regularly, so please check before delivering work.
Layout
You must align your work, to the pixel.
Your work should have equal margins and padding, appropriate to the task at hand.
You must always use a grid, where applicable.
Your grids should be 12-columns.
All “long” rows of text must average about 12 words in each line For thinner column of text, each line should have about 5 words.
Typography
No more than 2 font families per project.
Chosen fonts should have a variety of styles within (e.g., Regular, Bold, Italic, Bold Italic, Light, Medium, Extra Bold, Condensed)
Chosen fonts should complement each other (serif/sans; thin/thick), etc.
Fonts should not be too small, nor too big. (Study your surroundings, see how visual arts professionals handle this.)
Your font size and leading aka line height must have a proper relationship.
General
Don’t use colors that clash with their background.
Always design with your audience in mind to meet your goals.
Avoid adorning your work with anything unnecessary: ornamentals, colors, shapes and so on.
Aim for 8 – 9 pieces of content in the information hierarchy of each item.
Use tastefully the sundry aspects of visual hierarchy as you learn them.
Imagery
Always use 300 dpi for print projects.
Always use 72 dpi for digital projects.
Images may be found using JSTOR on MC’s library.
Video
Aim for videos that are horizontal rectangles, such as your phone when viewing it in landscape.
Stock videos can be found here: https://www.pexels.com/videos
Audio
Sound should be at average level, not too much nor too little.
Stock Audio can be found here.
Development
When asking for help in a timely manner you will provide screenshots, error messages and specific details as to what is wrong. How far do you get until the code breaks?
Best Practice: Naming Conventions for files and folders on macOS (OSX) and Windows (PC)
When naming files and folders on both macOS and Windows, consistency and clarity are key.
It’s best practice to use lowercase letters and hyphens (-) or underscores (_) to separate words, such as project-files or project_files, rather than relying on spaces which can lead to compatibility issues in some systems and scripts.
Avoid using special characters like ?, *, /, \, :, <, >, |, or "—these are either disallowed or problematic, especially on Windows.
Keep names concise but descriptive, so the content is easily identifiable at a glance.
A good convention is to include dates in the YYYY-MM-DD format (e.g., report-2025-05-27) for chronological sorting and clarity.
When working across systems, be mindful that Windows file names are not case-sensitive by default, whereas macOS (depending on file system) may treat File.txt and file.txt as the same or different files.
To stay safe, use all-lowercase names unless there’s a clear and controlled need for camelCase or PascalCase, which can add readability for longer names in coding environments.
For versioning, include version numbers like v1, v2, or v1.0.3 at the end of the file name before the extension, such as design-concept-v2.pdf.
Avoid redundant or vague names like new, final, or latest, which can lead to confusion—use specific descriptors and maintain a changelog when appropriate.
Overall, following these naming conventions helps with file searchability, prevents system conflicts, and improves collaboration, especially in shared or cross-platform environments.
Copyright
As a design and development student, when incorporating copyrighted materials (like logos, brand images, artworks, or photos you didn’t create) into your school projects, it’s important to acknowledge those sources appropriately—even if the work is for educational purposes and qualifies as fair use.
Sample Copyright Disclaimer for Student Work:
“This project was created for educational purposes only and is not intended for commercial use. Some images, logos, or materials used in this work are copyrighted by their respective owners. These materials are used here under the principles of fair use for academic critique, commentary, or learning purposes. All rights to third-party content remain with the original copyright holders.”
Misc
Each assignments must be done in accordance with its specific guidelines.
You will always have a fresh backup of your work. Crashed or lost drives cannot be accepted as an excuse when deliverables are due.
Work with typos or grammatical errors can be accepted.
Think:
Spare is good.
Don’t repeat yourself (DRY)
If being tired is getting in the way, then stop! and come back with fresh eyes and ears.








