Added screenshots and delete image domain model to readme.

Author: scottfalbo

Portfolio/wwwroot/css/layout.css

@@ -913,7 +913,7 @@ div.technologies-menu-button {
         grid-row: 2/3;
         text-align: center;
     }
-    .right-col img {
+    .right-col img.selfie {
         height: 300px;
     }
     .homepage-container>.popup-toggle-button {

README.md

@@ -118,6 +118,8 @@ Each page on the site has it's own popup admin GUI, visible to authenticated use
 
 The index page admin controls the home page's profile image, title, and intro paragraph.  
 
+![index admin screenshot](/assets/screenshots/index_admin.jpg)
+
 #### Update Image
 
 This form updates the profile photos on each page. It removes the previous file from the blob, uploads the new one, and creates a new record in the database.
@@ -138,35 +140,39 @@ The code page has three separate admin panels.  One for the basic page informati
 The third GUI is what controls the portfolio section of the page.  It has CRUD actions to create, update, and delete projects, as well as add and remove images from projects.
 I've included domain models for the add and remove projects methods. The general page admin is same as the index page. The add and remove image methods will be detailed below under the Art Page section.
 
+![project admin screenshot](/assets/screenshots/project_admin.jpg)
+
 #### Add Project
 
 The add project form takes in a new project title.  Because the title will be used for class names to control the Bootstrap accordion dropdown they need to be unique.  The `CheckProjectTitle` method validates the input.  When the project is created the title is normalized and used to assign several class names for use with dropdowns.  The project is saved to the database with the title and classnames.  Then a list of technologies is attached to the project for display in portfolio view.
 
-![index update model](/assets/code_project_add.jpg)
+![add project model](/assets/code_project_add.jpg)
 
 #### Delete Project
 
 The delete project form sends the project Id to the model. First the join table records for the ProjectImages are removed. Then the respective Image records are removed and the file is deleted from blob storage. Lastly the ProjectTechnology records are removed and then the Project record.
 
-![index update model](/assets/code_project_delete.jpg)
+![delete project model](/assets/code_project_delete.jpg)
 
 ---
 
 ### Art Page Admin
 
 The art page has an admin for the general page content just like the index and code page. The galleries have their own GUI that can add and remove galleries, similar to adding and removing projects from the code page, and add and remove images from galleries.  
 
+![gallery admin screenshot](/assets/screenshots/gallery_admin.jpg)
+
 #### Add Images
 
 The add images form sends an array of IFormFiles to the AddImages handler. Each image resized for gallery view and a copy is made and resized for thumbnail view.  Both file names have the white space stripped and the date and time attached to ensure a unique name in the blob.  Once stored in the blob the filename and blob.uris are used to create and save an Image in the database. Then the image is added to the gallery with an `ImageGallery` join table and the page is refreshed.
 
-![index update model](/assets/gallery_add_image.jpg)
+![add image model](/assets/gallery_add_image.jpg)
 
 #### Delete Image
 
 The delete image form removes the image from the gallery by deleting the `GalleryImage` join table record.  Then the image and thumbnail are removed from the blob by filename.  And finally the image record is removed from the database.
 
-![index update model](/assets/gallery_delete_image.jpg)
+![delete image model](/assets/gallery_delete_image.jpg)
 
 ---