Skip to content

ltw-webdev-5/portfolio-design-and-content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

summary time deliverables
Basically finish your portfolio website. All the content should be real. All the text should be real.
10 hours
Lots of files, lots of images, Jekyll

Portfolio design & content

Overview

Put all the final content, images and design into your portfolio. The whole website should be done—except for JavaScript. Make it perfect.

Some details & things about the website to consider:

  • It should be completely responsive between 320px – ~2500px.
  • Only real images and real text.
  • The design, logos, typography, etc. should be complete.
  • Every single portfolio piece should be final.
    If they’re incomplete because you’re still working on them in another class put as much in as absolutely possible.
  • Add in all the accessibility features we’ve discussed in the past.
  • Performance isn’t too big of a concern—we’ll be spending time on that later. But don’t put massive RAW graphics on your website. I don’t want to have to wait 10 minutes for it to download.
  • There should be no broken links anywhere on the website.
  • ABSOLUTELY NO JAVASCRIPT!!—your site should be fully functional without it, we’ll add it in later.

Critiques

We’ll be performing critiques to get a grade for this project. More details below, in the “Hand-in” section.

There will be two weeks where critiques can be performed: Week 11 or Week 12. Pick whichever week works best for you.


Browser testing

In class, week 11, we will be doing lots of peer testing—most of the website needs to be complete by then.

Each person will be assigned a browser or validator and will be required to test everybody’s websites.


Marking rubric

Below is the rubric of expectations for this project. You will be assigned a letter grade based on your standing within the rubric.

0 points 1 points 2 points 3 points
Pages & images Barely started Missing lots of pages & images Has most of the pages, some placeholder images All pages exist and are well done with complete imagery
Personality & design Bland, boring, just another graphic designer Fairly generic, visual design could be pushed more Quality layouts and unique, personable content & design Unique and recognizable as you, with engaging, personable content & design
Image quality Only placeholder images Some portfolio piece images Lots of images but low quality High quality portfolio images — and lots of them
Accessibility No considerations Added some alt attributes, nothing else Just the basics: alt attributes, roles Accessibility is well considered and tested
Text content Fake content only Some real content, some fake All real content but with lots of errors Real content, well written, no grammar or spelling errors
Responsiveness Not responsive Works on some screens Responsive but with lots of awkwardness Looks great on all screen sizes
Code quality Barely started Indentation is barely existent, lots of validation errors, very poor semantics Decent indentation, just a couple validation errors, decent semantics Well indented, fully valid, good semantics

Copy & paste this code for your GitHub Issue ➔


Hand in

  1. Upload the assignment to GitHub and make sure it works on Netlify
  2. Make sure the Netlify URL is somewhere on the GitHub repo’s page
https://some-fun-name-thing.netlify.com

Get critiques & grade yourself

To receive a grade on the interactive wireframes you’ll need to:

  • Get 3 peer critiques
  • Fill out the rubric
  • Write a personal performance rationale
  • Get the teacher’s critique
  • Determine a grade

3 peer critiques

Select 3 of your peers and get them to critique your project ➔

Also consider performing usability tests ➔

Fill out the rubric

Using the rubric above, copy the code to a GitHub Issue, attached to your repository, and select the appropriate grade for each section.

Sum the values of the rubric & put that at the bottom of the Issue.

Personal performance rationale

As a GitHub Issue, attached to your repository, write a short-ish rationale explaining how well you did completing your project:

  • What did you do well?
  • What did you do poorly?
  • What could be improved?
  • What problems did you run into?
  • What complications did you overcome?
  • Does the website communicate the right message?
  • Is the website usable?

Teacher critique

Meet with the teacher in class and get a critique of your project.

Determine a grade

Using all the above information, assign yourself a grade that reflects everything you’ve completed.

Discuss this grade with the teacher—if it’s fair & honest the teacher will assign the grade immediately.

About

Basically finish your portfolio website. All the content should be real. All the text should be real.

Resources

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

 

Packages

No packages published