Week 6 Lab : Build you Portfolio

To Submit this Assignment

• fork this repository (on day 26)
• create a new branch For each lab named Week6DayX-; + <your name> e.g. Week6Day1-amanda
• write your code
• push to your repository
• submit a pull request to this repository
• submit a link to your PR in canvas
• Include a Readme.md (contents described below)

Directions

This lab will span over the course of 4 days. You will be building out your portfolio to showcase your projects and experience. At the end of the week, your final submission should contain the project completed as a whole. This includes completed documentation and tests.

** Everyday's lab is dependant upon what we completed in class. Check back every day for the updated assignment.**

Day 1

• Build out the beginning of your Portfolio site, using Razor Pages architecture
• Create the Models required for your site. This includes
  • Main Porfolio class
  • Interface
  • Database Seed (with initial data)
  • DbContext
  • Services
• Home Page
  • Index.cshtml
• Stylesheet
• Make sure your Startup.cs class is properly configured
• Deploy to Azure. Provide your link in your Readme. (Name it something intuitive like AmandaIversonPortfolio.azurewebsites.net)

Day 2

Continue Building out your portfolio. In this branch, you should complete: - Complete your service class with all the calls to the database completed - Install Bootstrap - Add a new details landing page that shows the details of your 'item' - Decorate your home page and your landing page with CSS - Your home page should should show all the initial data in your database - Details page should show the individual details of the item that was selected - Use Taghelpers where approrpriate - Add a layout page to share a template - Comment, Comment, Comment

Day 3

Continue Building out your portfolio. In this branch, you should complete:

• Add Razor Page for your AddEditPortfolio
• Create a form that will Add/Edit a portfolio item

Day 4

• Complete your Portfolio Site.
• Add Authentication
• Add the capability to upload/save images

ReadMe

A README is a module consumer's first -- and maybe only -- look into your creation. The consumer wants a module to fulfill their need, so you must explain exactly what need your module fills, and how effectively it does so.
Your job is to

1. tell them what it is (with context)
2. show them what it looks like in action
3. show them how they use it
4. tell them any other relevant details

This is your job. It's up to the module creator to prove that their work is a shining gem in the sea of slipshod modules. Since so many developers' eyes will find their way to your README before anything else, quality here is your public-facing measure of your work.

Refer to the sample-README in the class repo for an example.

• Reference

Rubric

• 7pts: Program meets all requirements described in Lab directions

• 3pts: Code meets industry standards

• Readme.md required for submission. Missing readme document and tests will result in a best score of 2/10