AIST2220 TechPrac03 Specs

Preamble This is our last assignment that is due before midterm (not an exam, but the last day -- Tue Mar 5 -- you can withdraw from class without a grade penalty). This TechPrac will primarily require you to -- as needed -- be sure your AIST 2220 web site (with requirements as articulated in TP00 thru TP02) is properly deployed with HTML validated, HTML code in a nice format, no missing links, appropriate rendered layouts and suitable content. This is essentially a chance to correct any of these issues from the earlier TechPracs and not only earn points for this TechPrac, I will go back and update earlier scores if you fix the problems.

1. 40 pts - HTML Quiz

   In a browser on the course remote desktop (use Edge, Chrome or Firefox by double-clicking a desktop icon, don't use IE from the task bar) visit and take the W3Schools HTML Quiz. When you finish -- and take the quiz as many times as you like -- open a command window (use Start | cmd {Enter}) and issue the commands date /t and whoami in the terminal. Then window your quiz result next to the command window and take a screen cap of the result [For Example]. Save the image file as HTMLQuiz.jpg (or other image format) and upload it to this assignment in D2L. Week 5 in the Agenda have guidance and reminders of techniques to use.

2. 85 pts - Ensure your site is 'production' worthy

   In this task you make sure your site meets the standard for class. It may help to review comments from TP00 thru TP02 to identify areas where you can make improvement but even if you scored well, be sure that your deployed site meets these criterion. If you successfully correct these issues from the earlier assignments I will go back and update those grades as well. I recommend starting early and reaching out quickly with questions or issues, especially since it can sometimes be a little unclear how to resolve issues that the validator and link checker raise.

   1. Your site's file and folder structure should be like the following with all HTML files using .htm as extension. Note: You may have additional files, the filename upper / lower case doesn't need to match mine, you may have named / located your error HTML files differently, your image files will be different, and you may not have a Default.htm anymore if you deleted it -- no problem. The web.config file is an artifact of setting custom error pages so leave that alone.

      C:\AIST2220SITES\TSTUDENT
      │   AboutMe.htm
      │   CodeDemo.htm
      │   DataTable.htm
      │   Default.htm
      │   Error403.htm
      │   Error404.htm
      │   SynopsesIndex.htm
      │   web.config
      │
      ├───images
      │       Benedict&Clyde.jpg
      │       BenedictAndClyde.jpg
      │       ToddAUCrop.jpg
      │
      └───Synopses
              HTMLBibleCh01.htm
              HTMLBibleCh02.htm
              HTMLBibleCh03.htm
              HTMLBibleCh04.htm
              HTMLBibleCh05.htm
              HTMLBibleCh06.htm
      

   2. HTML files should meet requirements for content and layout from TP00 thru TP02, though you may adjust / remove the colors in AboutMe.htm if you want if they seem a little garish from our practice in TP00.
   3. Every HTML file's code should be formatted for readability (e.g., use VSCode's reformat).
   4. Every HTML file's code should pass validation (e.g., use https://validator.w3.org/nu/).
   5. Every HTML file should have any missing links corrected (e.g., see and use https://validator.w3.org/checklink).

Nothing to upload to D2L for this exercise since I check your deployed files on the server.