From 2197956109781199f71aa79b03f98a30e86ed839 Mon Sep 17 00:00:00 2001 From: aschechter10 Date: Thu, 23 Jan 2025 18:48:44 -0500 Subject: [PATCH] added all my work --- README.md | 114 +++------------------------------------------------- hobby.html | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++ index.html | 73 +++++++++++++++++++++++++++------ palette.png | Bin 0 -> 325465 bytes server.js | 38 ++++++++++-------- styles.css | 75 ++++++++++++++++++++++++++++++++++ 6 files changed, 277 insertions(+), 137 deletions(-) create mode 100644 hobby.html create mode 100644 palette.png diff --git a/README.md b/README.md index 529450f..80ca555 100644 --- a/README.md +++ b/README.md @@ -1,115 +1,13 @@ -Assignment 1 - Hello World: Basic Deployment w/ Git, GitHub, Glitch -=== - -*DUE: Thursday, January 23 by 11:59 PM* - -First assignment! You will deploy the starting Web site that you will use this term to [Glitch](http://www.glitch.com/). - -Treat this assignment as a chance to get up to speed on Git, GitHub, and Glitch, as well as experiment some with HTML/CSS/JS. If you already know these, great! -However, if you're new to them, spend several hours practicing, experimenting, and reading documentation. Don't just get your website up and done, as -you'll need skills with these tools throughout the rest of the course. - -PAY ATTENTION TO THE NAMING AND URL SCHEME REQUIREMENTS. This is where students often lose points on this assignment. - -Assignment details --- -This assignment requires that your website is both contained in a GitHub repository and hosted in Glitch. There are two ways to do this: - -1. Fork this repo and clone it to your computer, make changes locally on your computer, push the repo onto GitHub, and then import your GitHub repo into Glitch. -2. Fork this repo and then import it directly to Glitch, use the Glitch editor to make changes, and then export your repo from Glitch back to GitHub. -3. Same as #1, but instead of importing from Github to Glitch you just upload the files (or copy/paste) them directly to Glitch. - -## Option 1 - Clone to computer, push to Github, import to Glitch (recommended) - -1. Fork the starting project code in GitHub. This repo contains: - * the server code, `server.js` - * A starting `index.html` file that you will edit as described below - * A package.json file that helps configure Glitch - * This README -2. Edit `index.html` to show the following information about you: - * your name and class at WPI (e.g. class of 2025) Note: Do not put any contact or personal information that you do not potentially want other people outside of this class to see. - * your major(s) and minor(s) - * a list of previous computer science courses that you have taken at WPI - * a table containing your experience with the following technologies and methods (none, some, a lot) - * HTML - * CSS - * JavaScript/Typescript (specify which one) - * SQL (specify which ones) - * MongoDB - * Web Frameworks (specify which ones) - * unit testing -3. Create `hobby.html` to show one of your interests: - * use two of the HTML5 semantic block elements - main, section, article, aside, header, footer - * create a form related to your hobby (such as asking readers to provide information about their interests) that include the following the following form elements - * input text box - * text area - * check boxes - * radio buttons - note that the radio buttons should permit only a single selection! - * a drop down selection list - * labels for each of the elements above - * a submit button with no action (the button does not do anything for now) -4. Using the