About-Me

This is a simple website showcasing information about me. View this project here: https://jessicakwalters.github.io/About-Me/

Assignment Overview: Lab for Class 2

Your assignment will be to create an "About Me" HTML and JS project.

Note that as we progress through the week, new user stories will be added to the "About Me" project to guide the development of new features.

User Stories for "About Me" (MVP)

• As a student, I want to create an About Me page as a demonstration of my skills with HTML.
• As an eventual jobseeker, I want to get practice in creating a portfolio page so that I can make myself appealing to potential employers.
• As an eventual jobseeker, I would like for potential employers to quickly learn a few things about me, such as a short bio, my education, an overview of my job experience, and my goals.
• As a fun-loving human being, I want to give the visitors to my About Me page a guessing game that shows how fun-loving and interesting I am, and maybe include things about myself that would not ordinarily appear in a portfolio page.
• As a developer, I want to use markup to structure my index.html page, so the layout is in the order of assembly I prefer, with effective use of the markup possibilities offered by HTML.
• As a developer, I want to carefully design my scripts, so I can understand how to organize and write my code to achieve my goals in interactivity.
• As a developer, I want to create a simple script for my index.html page using JavaScript, so that I can use the browser to send a response to the user
• As a developer, I want to receive and use the user's name, so that the program is personalized to their experience. As a developer, I want to provide five questions to the user, so that they can guess the answers and get to know me.
• As a developer, I want to notify the user after each question, so they are aware whether they were correct or not in their answers.
• As a developer, I want to be able to debug my code by using well structured console messages.
• As a developer, I want to manage my code through an online version control system, so I have the ability to work with others, manage my revisions, and keep a thorough record of my progress.

Technical Requirements for "About Me"

• A new GitHub repo called about_me will be initialized for this assignment (with a README and a license, of course)
• Clone this repo to the root level of your ~/codefellows/201/ directory on your computer.
• Add an index.html file, a style.css file, and an app.js file to your repo, and get the files "wired up together" so to speak.
• HTML, CSS, and JavaScript must be cleanly written with correct indentation and syntax. Look at code examples online and in your textbook, and check out Google's style guides for HTML/CSS and JavaScript. Note that your JS must pass the rules in our linter.
• Your JS file contains a 'use strict' declaration at the top. Always.
• Design a guessing game about you that involves FIVE yes/no questions. Be creative and fun and whimsical. Or not. It's up to you! It's your project!
• For this stage of the buiiding of this project, DO NOT USE FUNCTIONS! We'll refactor later.
• The questions in the guessing game must require a mix of yes/no answers, and user input must accept either y/n or yes/no responses, with either .toUpperCase() or .toLowerCase() used to validate the user input and accommodate users entering all-caps Y/N or YES/NO answers, too.
• Useful and descriptive console.log() messages in the JS are well written and correctly displaying to the browser console for each question of the guessing game.
• Use CSS to style your page as you see fit, to the level of abilities in CSS that you currently have
• Add, Commit, Push process is being followed; evident in GitHub that commits are made regularly, and with good commit messages.

Stretch Goals for "About Me" (not required!)

• Add a series of document.write() statements to print out the questions and responses to your guessing game at the bottom of your about me page.

Assignment Overview: Lab for Class 3

For this lab we will be adding a few things to the work we've done so far. Use the User Stories and the Technical Requirements to make a plan for how to proceed. Assume that all user stories from the previous lab carry over, except for the ones that are modified or are superseded here.

It can be very handy to take notes and sketch things out when you are planning your projects and the code within it.

User Stories (MVP... what you must do as a minimum)

• As a developer, I want to use thoughtful and descriptive console.log() throughout my code to help test my work and assist with debugging.
• As a developer, I want to convert some of my appropriate biographical elements into unordered lists, such as my education summary and/or my work experience.
• As a developer, I want to consider the user experience (UX) of my About Me and guessing game, trying to view it through the eyes of a user. Wait... maybe I should just write a user story for that...
• As an end user of the About Me and guessing game, I want to have an informative, interesting, and fun experience in learning about the developer.
• As a prospective job seeker, I want to consider adopting additional features that I have seen in the 'About Me' projects made by others, so that my 'About Me' can become more thorough and interesting than my original conception.
• As a prospective job seeker, I want to make myself more personable by adding a Top Ten list to the bottom of my About Me page with an ordered list in HTML, for instance, my Top Ten Favorite Movies or my Top Ten Places I Want to Visit, or something along those lines.
• As a prospective job seeker, I was to use CSS to creatively and tastefully style and layout my page.
• As a prospective job seeker, I want to have five yes/no questions in my "about me" guessing game so that I have enough questions to cover a variety of things about me.
• As a developer, I want to add a sixth question to my guessing game that takes numeric input by prompting a user to guess a number (for instance, "What is my favorite number?" or "How many Pokémon did I catch yesterday?"), and indicates to the user whether the guess is 'too high' or 'too low', and gives the user exactly four opportunities to get the correct answer, so that my fancy programming skills are showcased.
• As a developer, I want to add a seventh question to my guessing game that has multiple possible correct answers that are stored in an array. For instance, "Can you guess a state that I have lived in besides Washington?", so that even more of my programming skills are showcased. For now, I will structure this question so that the user has six tries to get a single correct answer, and upon using up those tries OR getting a correct answer, displays a message to the user indicating all of the possible correct answers.
• As a developer, I want to keep a tally of the total number of correct answers given by the user, and at the end of the game, tell the user how well they did with a personalized custom message that includes the number of correct answers and also addresses the user by name, e.g. "You got 4 out of 7 questions correct, Bobbi! Better luck next time."

User Stories (Stretch goals... not required!)

• As a developer, I want to make my code more DRY by putting all of the questions, answers, and responses to the first five yes/no questions in my guessing game into arrays (or even one huge multidimensional array), and modifying the game logic such that a 'for' loop will control the flow from question to question.
• Make the number-guessing question use a random number as its correct answer.
• Move the guessing game to a separate HTML file, list the questions on the page, and then have the answers fill in on the page after the user provides the answers.

Technical Requirements

• Per the user stories, you will need to include in your HTML at least one each of an ordered and an unordered list.
• Use promptfor input and alert for output to the user, unless you are working on the third Stretch Goal.
• Do not use any 'switch' statements in your JavaScript.
• Do not write any functions in your JavaScript.
• Expect that you will probably need both 'for' and 'while' structures for your sixth and seventh questions. But not necessarily.