{"id":11184,"date":"2026-10-13T05:15:47","date_gmt":"2026-10-13T09:15:47","guid":{"rendered":"https:\/\/fouloistech.info\/ma\/?p=11184"},"modified":"2026-10-08T11:19:21","modified_gmt":"2026-10-08T15:19:21","slug":"cs-discoveries-week-8-10-13-2026-lesson-20-project-website-for-a-purpose","status":"publish","type":"post","link":"https:\/\/fouloistech.info\/ma\/2026\/10\/13\/cs-discoveries-week-8-10-13-2026-lesson-20-project-website-for-a-purpose\/","title":{"rendered":"CS Discoveries Week 8, 10-13-2026, Lesson 20: Project – Website for a Purpose"},"content":{"rendered":"
    \n
  1. Objective:<\/strong>\"\"\n
      \n
    1. Students will begin finalizing their end-of-course projects to showcase what they have learned this Quarter.<\/li>\n<\/ol>\n<\/li>\n
    2. 11:50-12:00: Start of Class<\/strong>\n
        \n
      1. W<\/strong>arm-Up:<\/strong>\n
          \n
        1. \n
            \n
          1. Complete this Google Form Quiz on Lessons 1-19.<\/a>\n
              \n
            1. Remember it is open notes, but not open conversation<\/span>.<\/li>\n
            2. Remember to EDIT YOUR ANSWERS<\/span> if you do not get a 5\/5.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n
            3. Warm-Ups are usually a 5 point Independent Work grade if a written response is expected, a 5 point Assessment grade if the Warm-Up is a quiz, or part of a 10 point Notebook Check if they include new vocabulary\/code to enter into student notes. They are due at the start of class and not eligible for late submission or re-submission.<\/em><\/li>\n<\/ol>\n<\/li>\n
            4. 12:00-12:55: Instruction & Student Work<\/strong>\n
                \n
              1. Your checklist and guide from Lesson 19<\/a> were provided to help you. Are you using them?<\/li>\n
              2. Your website will not be finished today, but if you don't spend today on-task it might not get finished.<\/li>\n
              3. All of the video tutorials:\n
                  \n
                1. Headings & Lists<\/a><\/li>\n
                2. CSS<\/a><\/li>\n
                3. Images & More CSS<\/a><\/li>\n
                4. CSS Classes<\/a><\/li>\n
                5. Links<\/a><\/li>\n
                6. Div Tags<\/a><\/li>\n
                7. Pseudo-Classes<\/a><\/li>\n
                8. Making a Zip file on the lab computers<\/a><\/li>\n<\/ol>\n<\/li>\n
                9. Make sure you're only editing code in your website folder, NOT in a .zip file. (The end of class is not the time to learn you've done this wrong.)<\/li>\n
                10. Go over your website to make sure it works properly and ALL THE CODE IS HOW IT SHOULD BE.\n
                    \n
                  1. (Collectively you've all been doing well on the code proofreading quizzes. Transfer that knowledge to your own code.)<\/li>\n<\/ol>\n<\/li>\n
                  2. Review the rubric below to ensure you won't be losing points because you forgot to do something crucial.<\/span><\/li>\n
                  3. SAVE. YOUR. WORK.<\/span><\/strong><\/li>\n
                  4. Use Mr. Smith's instructions for right-clicking on your website folder and compressing it into a .zip file<\/a>.<\/li>\n
                  5. Upload your NEW .zip file to the Week 8 Exit Ticket DAILY.<\/li>\n
                  6. Grading Rubric (2 pts each unless otherwise stated)<\/strong>\n
                      \n
                    1. Purpose<\/strong>: The website has a clear purpose, and each of the 4 pages somehow supports that purpose.<\/li>\n
                    2. HTML<\/strong>: HTML used to add all needed content to every web page correctly.<\/li>\n
                    3. Modularity<\/strong>: All 4 pages use the same stylesheet to apply consistent formatting rules to all web pages.<\/li>\n
                    4. CSS<\/strong>: CSS used to control the HTML content's appearance on all 4 pages correctly.<\/li>\n
                    5. Classes<\/strong>: The site uses classes to create different rules for groups of elements, so elements with the same tag can have different styles according to the class rules.<\/li>\n
                    6. Code Readability<\/strong>: White space and indentation used to make the HTML and stylesheet code consistently well-formatted and easier to read on every page. All pages and images have names that make sense.<\/li>\n
                    7. Proofreading<\/strong>: There are no syntax errors on any HTML page or the CSS code, and the page renders correctly.<\/li>\n
                    8. Copyright<\/strong> (6 pts): All images have been cited, and credit is given to the creators.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n