This repository contains the activities and assignments required to complete the final course of the Front End Certificate program. All assignment submissions and quizzes/discussions will be done through Canvas.
Follow these steps to get your initial setup started
- Visual Studio Code - Editor/IDE
- Hyper Terminal - Modern Terminal
- Oh My Zsh - Zsh framework
- Adobe XD - Design Tool
- Create a new repository that will hold your final course project, name it whatever you'd like
- In this repo, click on the
Settingstab at the top right, then theCollaboratorstab on the left. Search forbrycebensonandClovisIto add as collaborators - For assignment 01 you will create a
documentsfolder in the root with a.txtor.mdfile within, containing the course proposal - As the course progresses, work for the course final will be done/migrated here
- Within this html300 repo, click the
forkbutton the the top right to fork a copy to your personal GitHub - You will be taken to your forked repo, it should say 'forked from...' under the title
- In your newly created fork, click on the
Settingstab at the top right, then theCollaboratorstab on the left. Search forbrycebensonandClovisIto add as collaborators - Clone the fork to your local machine
- Navigate to your fork's root folder in terminal (e.g.
cd ~/Sites/uw/html300) - Make sure you are on your master branch,
git checkout master - Run
git remote add upstream git@github.com:UWFront-End-Cert/html300.git - Verify with
git remote -v, should have bothoriginandupstream
- To keep your fork in sync with any changes to the original, we'll use upstream to fetch and merge with our forks
- Run
git fetch upstreamto get the latest code from all branches - Now make sure you're on master with
git checkout master - Now merge the upstream version of master with your fork's by running
git merge upstream/master - You shouldn't run into conflicts, but if you get errors or conflicts, run
git statusto see which files need to be updated, and usinggit add --allafter resolved to add them to be staged
- Start by checking out your local master branch and fetching/merging upstream at the beginning of each module so you know you're up to date
- Create a branch for your week's assignment. You can create and checkout a new branch with
git checkout -b branch-name - Each lesson will usually have two folders,
activityandassignment. Feel free to work on the activity within your assignment branch - The
activitywill often havestarterandsolutionfolders, this is to help illustrate the starting/ending point for each - The
assignmentfolder will have the starter files and instructions required to complete - Once completed, open a new Pull Request. Within the PR, set the base to be YOUR forked master branch, and the compare branch is whatever that week's assignment branch is
- In the Reviewer's section, click into the box and add
brycebensonandClovisIas reviewers - note you will have needed to invite us as collaborators to your fork first - Now, do NOT merge or close the Pull Request -- just add us as reviewers
- Copy the direct link to the pull request page, and paste that into the submission box in Canvas
- Check the
README.mdfiles found in the root of eachassignmentfolder for instructions, links for tools, and any required information. Consult the rubric within Canvas for the grading scale breakdown - When you open a pull request, you may keep pushing commits to that assignment's branch as they will automatically update the PR -- no need to close and re-open a new one
- Please use the Canvas discussion boards if coming across issues or problems with assignments so all folks have visibility
- Each week there will be a quiz available to take, please flag up any issues if questions aren't being assessed correctly