diff --git a/README.md b/README.md
index 3945c152..bb6c45ba 100755
--- a/README.md
+++ b/README.md
@@ -1,93 +1,30 @@
-Assignment 2 - Short Stack: Basic Two-tier Web Application using HTML/CSS/JS and Node.js
-===
-
-Due: September 16th, by 11:59 PM.
-
-This assignment aims to introduce you to the concepts and practice involved in creating a prototype (i.e. not deployment ready) two-tiered web application. The baseline aims of this assignment involve creating an application that demonstrates the use of several specific pieces of HTML, CSS, JavaScript, and Node.js functionality.
-
-Baseline Requirements
+# Assignment 2 - Short Stack: Basic Two-tier Web Application using HTML/CSS/JS and Node.js
---
-Note that there is a very large range of application areas and possibilities that meet these baseline requirements. Make your application do something useful! A todo list, storing / retrieving high scores for a very simple game, have a little fun with it.
-
-Your application is required to implement the following functionalities:
-
-- a `Server` which not only serves files, but also maintains a tabular dataset with 3 or more fields related to your application
-- a `Results` functionality which shows the entire dataset residing in the server's memory
-- a `Form/Entry` functionality which allows a user to add, modify, or delete data items residing in the server's memory
-- a `Server Logic` which, upon receiving new or modified "incoming" data, includes and uses a function that adds at least one additional derived field to this incoming data before integrating it with the existing dataset
-- the `Derived field` for a new row of data must be computed based on fields already existing in the row. For example, a `todo` dataset with `task`, `priority`, and `creation_date` may generate a new field `deadline` by looking at `creation_date` and `priority`
-
-Your application is required to demonstrate the use of the following concepts:
+https://a2-hezi-k.glitch.me
-HTML:
-- One or more [HTML Forms](https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms), with any combination of form tags appropriate for the user input portion of the application
-- A results page displaying all data currently available on the server. You will most likely use a `
` tag for this, but `
` could also work and might be simpler to work with.
-- All pages should [validate](https://validator.w3.org)
-
-CSS:
-- CSS styling of the primary visual elements in the application
-- Various CSS Selector functionality must be demonstrated:
- - Element selectors
- - ID selectors
- - Class selectors
-- CSS positioning and styling of the primary visual elements in the application:
- - Use of either a CSS grid or flexbox for layout
- - Rules defining fonts for all text used; no default fonts! Be sure to use a web safe font or a font from a web service like [Google Fonts](http://fonts.google.com/)
-
-- CSS defined in a maintainable, readable form, in external stylesheets
-
-JavaScript:
-- At minimum, a small amount of front-end JavaScript to get / fetch data from the server; a sample is provided in this repository.
-
-Node.js:
-- An HTTP Server that delivers all necessary files and data for the application. A starting point is provided in this repository.
-
-Deliverables
----
+## WPI Football
-Do the following to complete this assignment and acheive a base grade of 85%:
+WPI Football seeks to address the need of organising pick up football in WPI. Currently the system is set up on messenger. Someone will send a message asking to play and people respond accordingly. However the system can be confusing and convoluted. I would really like to develop this website further. As a starter, I wanted to create a system where other players can check eachother out and see simple things like their name and their stats. I wanted to make this on a separate page however I could not figure out how to do this with the sever. You can see the commented out code in the respective files. I would like to make this more robust and let people add more stats or even profile pictures. For now a user is able to put in their username, password and some basic stats and this is displayed in a table below. However, I think this has a lot of potential.
-1. Fork the starting project code (make sure to fork the 2020 repo!). This repo contains some starter code that may be used or discarded as needed.
-2. Implement your project with the above requirements.
-3. Test your project to make sure that when someone goes to your main page, it displays correctly.
-4. Deploy your project to Glitch, and fill in the appropriate fields in your package.json file.
-5. Ensure that your project has the proper naming scheme `a2-yourname` so we can find it.
-6. Modify the README to the specifications below.
-7. Create and submit a Pull Request to the original repo. Label the pull request as follows: a2-gitusername-firstname-lastname
+One other future I could not figure out was how to delete an entry, with a button. However, I think I need to spend more time on this.
-Acheivements
----
-
-Below are suggested technical and design achievements. You can use these to help boost your grade up to an A and customize the assignment to your personal interests. These are recommended acheivements, but feel free to create/implement your own... just make sure you thoroughly describe what you did in your README and why it was challenging. ALL ACHIEVEMENTS MUST BE DESCRIBED IN YOUR README IN ORDER TO GET CREDIT FOR THEM.
-
-*Technical*
-- (10 points) Create a single-page app that both provides a form for users to submit data and always shows the current state of the server-side data. To put it another way, when the user submits data, the server should respond sending back the updated data (including the derived field calculated on the server) and the client should then update its data display.
-
-*Design/UX*
-- (5 points per person, with a max of 10 points) Test your user interface with other students in the class. Define a specific task for them to complete (ideally something short that takes <10 minutes), and then use the [think-aloud protocol](https://en.wikipedia.org/wiki/Think_aloud_protocol) to obtain feedback on your design (talk-aloud is also find). Important considerations when designing your study:
-
-1. Make sure you start the study by clearly stating the task that you expect your user to accomplish.
-2. You shouldn't provide any verbal instructions on how to use your interface / accomplish the task you give them. Make sure that your interface is clear enough that users can figure it out without any instruction, or provide text instructions from within the interface itself.
-3. If users get stuck to the point where they give up, you can then provde instruction so that the study can continue, but make sure to discuss this in your README. You won't lose any points for this... all feedback is good feedback!
-
-You'll need to use sometype of collaborative software that will enable you both to see the test subject's screen and listen to their voice as they describe their thoughts. After completing each study, briefly (one to two sentences for each question) address the following in your README:
+## Technical Achievements
-1. Provide the last name of each student you conduct the evaluation with.
-2. What problems did the user have with your design?
-3. What comments did they make that surprised you?
-4. What would you change about the interface based on their feedback?
+- **Tech Achievement 1**: This single-page app utilizes a combination of forms and tables so that a user can submit data, and the app will display both the data and the result of the derived field. The form includes a username, password, nickname, preferred foot, and position.
-*You do not need to actually make changes based on their feedback*. This acheivement is designed to help gain experience testing user interfaces. If you run two user studies, you should answer two sets of questions.
+### Design/Evaluation Achievements
-Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
----
+- **Student Interview 1**:
-## Your Web Application Title
-Include a very brief summary of your project here. Be sure to include the CSS positioning technique you used, and any required instructions to use your application.
+Student Name: Lindberg Simpson
+Problems: No problems mentioned when using the site
+Comments: The user didn't have any issues using the website. They did comment that it would be nice fot the entry forms to be aligned.
+Changes to be made based on feedback: In future I will make sure that the forms are aligned. I usually like to focus on looks but this time I didnt have time to do that. So I will spend some time making it look nice
-## Technical Achievements
-- **Tech Achievement 1**: Using a combination of...
+- **Student Interview 2**:
-### Design/Evaluation Achievements
-- **Design Achievement 1**:
+Student Name: Akul Argawal
+Problems: No problems mentioned when using the site
+Comments: he user didn't have any issues using the website either. They did mention that it would be cool to display the football positions and display their peoples names.
+Changes to be made based on feedback: The user seemed to be interested in having more of a graphical interface which I will try implement.
diff --git a/node_modules/mime/CHANGELOG.md b/node_modules/mime/CHANGELOG.md
new file mode 100644
index 00000000..968fabec
--- /dev/null
+++ b/node_modules/mime/CHANGELOG.md
@@ -0,0 +1,268 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
+
+### [2.4.6](https://github.com/broofa/mime/compare/v2.4.5...v2.4.6) (2020-05-27)
+
+
+### Bug Fixes
+
+* add cli.js to package.json files ([#237](https://github.com/broofa/mime/issues/237)) ([6c070bc](https://github.com/broofa/mime/commit/6c070bc298fa12a48e2ed126fbb9de641a1e7ebc))
+
+### [2.4.5](https://github.com/broofa/mime/compare/v2.4.4...v2.4.5) (2020-05-01)
+
+
+### Bug Fixes
+
+* fix [#236](https://github.com/broofa/mime/issues/236) ([7f4ecd0](https://github.com/broofa/mime/commit/7f4ecd0d850ed22c9e3bfda2c11fc74e4dde12a7))
+* update to latest mime-db ([c5cb3f2](https://github.com/broofa/mime/commit/c5cb3f2ab8b07642a066efbde1142af1b90c927b))
+
+### [2.4.4](https://github.com/broofa/mime/compare/v2.4.3...v2.4.4) (2019-06-07)
+
+
+
+### [2.4.3](https://github.com/broofa/mime/compare/v2.4.2...v2.4.3) (2019-05-15)
+
+
+
+### [2.4.2](https://github.com/broofa/mime/compare/v2.4.1...v2.4.2) (2019-04-07)
+
+
+### Bug Fixes
+
+* don't use arrow function introduced in 2.4.1 ([2e00b5c](https://github.com/broofa/mime/commit/2e00b5c))
+
+
+
+### [2.4.1](https://github.com/broofa/mime/compare/v2.4.0...v2.4.1) (2019-04-03)
+
+
+### Bug Fixes
+
+* update MDN and mime-db types ([3e567a9](https://github.com/broofa/mime/commit/3e567a9))
+
+
+
+# [2.4.0](https://github.com/broofa/mime/compare/v2.3.1...v2.4.0) (2018-11-26)
+
+
+### Features
+
+* Bind exported methods ([9d2a7b8](https://github.com/broofa/mime/commit/9d2a7b8))
+* update to mime-db@1.37.0 ([49e6e41](https://github.com/broofa/mime/commit/49e6e41))
+
+
+
+### [2.3.1](https://github.com/broofa/mime/compare/v2.3.0...v2.3.1) (2018-04-11)
+
+
+### Bug Fixes
+
+* fix [#198](https://github.com/broofa/mime/issues/198) ([25ca180](https://github.com/broofa/mime/commit/25ca180))
+
+
+
+# [2.3.0](https://github.com/broofa/mime/compare/v2.2.2...v2.3.0) (2018-04-11)
+
+
+### Bug Fixes
+
+* fix [#192](https://github.com/broofa/mime/issues/192) ([5c35df6](https://github.com/broofa/mime/commit/5c35df6))
+
+
+### Features
+
+* add travis-ci testing ([d64160f](https://github.com/broofa/mime/commit/d64160f))
+
+
+
+### [2.2.2](https://github.com/broofa/mime/compare/v2.2.1...v2.2.2) (2018-03-30)
+
+
+### Bug Fixes
+
+* update types files to mime-db@1.32.0 ([85aac16](https://github.com/broofa/mime/commit/85aac16))
+
+
+### [2.2.1](https://github.com/broofa/mime/compare/v2.2.0...v2.2.1) (2018-03-30)
+
+
+### Bug Fixes
+
+* Retain type->extension mappings for non-default types. Fixes [#180](https://github.com/broofa/mime/issues/180) ([b5c83fb](https://github.com/broofa/mime/commit/b5c83fb))
+
+
+
+# [2.2.0](https://github.com/broofa/mime/compare/v2.1.0...v2.2.0) (2018-01-04)
+
+
+### Features
+
+* Retain type->extension mappings for non-default types. Fixes [#180](https://github.com/broofa/mime/issues/180) ([10f82ac](https://github.com/broofa/mime/commit/10f82ac))
+
+
+
+# [2.1.0](https://github.com/broofa/mime/compare/v2.0.5...v2.1.0) (2017-12-22)
+
+
+### Features
+
+* Upgrade to mime-db@1.32.0. Fixes [#185](https://github.com/broofa/mime/issues/185) ([3f775ba](https://github.com/broofa/mime/commit/3f775ba))
+
+
+
+### [2.0.5](https://github.com/broofa/mime/compare/v2.0.1...v2.0.5) (2017-12-22)
+
+
+### Bug Fixes
+
+* ES5 support (back to node v0.4) ([f14ccb6](https://github.com/broofa/mime/commit/f14ccb6))
+
+
+
+# Changelog
+
+### v2.0.4 (24/11/2017)
+- [**closed**] Switch to mime-score module for resolving extension contention issues. [#182](https://github.com/broofa/mime/issues/182)
+- [**closed**] Update mime-db to 1.31.0 in v1.x branch [#181](https://github.com/broofa/mime/issues/181)
+
+---
+
+## v1.5.0 (22/11/2017)
+- [**closed**] need ES5 version ready in npm package [#179](https://github.com/broofa/mime/issues/179)
+- [**closed**] mime-db no trace of iWork - pages / numbers / etc. [#178](https://github.com/broofa/mime/issues/178)
+- [**closed**] How it works in brownser ? [#176](https://github.com/broofa/mime/issues/176)
+- [**closed**] Missing `./Mime` [#175](https://github.com/broofa/mime/issues/175)
+- [**closed**] Vulnerable Regular Expression [#167](https://github.com/broofa/mime/issues/167)
+
+---
+
+### v2.0.3 (25/09/2017)
+*No changelog for this release.*
+
+---
+
+### v1.4.1 (25/09/2017)
+- [**closed**] Issue when bundling with webpack [#172](https://github.com/broofa/mime/issues/172)
+
+---
+
+### v2.0.2 (15/09/2017)
+- [**V2**] fs.readFileSync is not a function [#165](https://github.com/broofa/mime/issues/165)
+- [**closed**] The extension for video/quicktime should map to .mov, not .qt [#164](https://github.com/broofa/mime/issues/164)
+- [**V2**] [v2 Feedback request] Mime class API [#163](https://github.com/broofa/mime/issues/163)
+- [**V2**] [v2 Feedback request] Resolving conflicts over extensions [#162](https://github.com/broofa/mime/issues/162)
+- [**V2**] Allow callers to load module with official, full, or no defined types. [#161](https://github.com/broofa/mime/issues/161)
+- [**V2**] Use "facets" to resolve extension conflicts [#160](https://github.com/broofa/mime/issues/160)
+- [**V2**] Remove fs and path dependencies [#152](https://github.com/broofa/mime/issues/152)
+- [**V2**] Default content-type should not be application/octet-stream [#139](https://github.com/broofa/mime/issues/139)
+- [**V2**] reset mime-types [#124](https://github.com/broofa/mime/issues/124)
+- [**V2**] Extensionless paths should return null or false [#113](https://github.com/broofa/mime/issues/113)
+
+---
+
+### v2.0.1 (14/09/2017)
+- [**closed**] Changelog for v2.0 does not mention breaking changes [#171](https://github.com/broofa/mime/issues/171)
+- [**closed**] MIME breaking with 'class' declaration as it is without 'use strict mode' [#170](https://github.com/broofa/mime/issues/170)
+
+---
+
+## v2.0.0 (12/09/2017)
+- [**closed**] woff and woff2 [#168](https://github.com/broofa/mime/issues/168)
+
+---
+
+## v1.4.0 (28/08/2017)
+- [**closed**] support for ac3 voc files [#159](https://github.com/broofa/mime/issues/159)
+- [**closed**] Help understanding change from application/xml to text/xml [#158](https://github.com/broofa/mime/issues/158)
+- [**closed**] no longer able to override mimetype [#157](https://github.com/broofa/mime/issues/157)
+- [**closed**] application/vnd.adobe.photoshop [#147](https://github.com/broofa/mime/issues/147)
+- [**closed**] Directories should appear as something other than application/octet-stream [#135](https://github.com/broofa/mime/issues/135)
+- [**closed**] requested features [#131](https://github.com/broofa/mime/issues/131)
+- [**closed**] Make types.json loading optional? [#129](https://github.com/broofa/mime/issues/129)
+- [**closed**] Cannot find module './types.json' [#120](https://github.com/broofa/mime/issues/120)
+- [**V2**] .wav files show up as "audio/x-wav" instead of "audio/x-wave" [#118](https://github.com/broofa/mime/issues/118)
+- [**closed**] Don't be a pain in the ass for node community [#108](https://github.com/broofa/mime/issues/108)
+- [**closed**] don't make default_type global [#78](https://github.com/broofa/mime/issues/78)
+- [**closed**] mime.extension() fails if the content-type is parameterized [#74](https://github.com/broofa/mime/issues/74)
+
+---
+
+### v1.3.6 (11/05/2017)
+- [**closed**] .md should be text/markdown as of March 2016 [#154](https://github.com/broofa/mime/issues/154)
+- [**closed**] Error while installing mime [#153](https://github.com/broofa/mime/issues/153)
+- [**closed**] application/manifest+json [#149](https://github.com/broofa/mime/issues/149)
+- [**closed**] Dynamic adaptive streaming over HTTP (DASH) file extension typo [#141](https://github.com/broofa/mime/issues/141)
+- [**closed**] charsets image/png undefined [#140](https://github.com/broofa/mime/issues/140)
+- [**closed**] Mime-db dependency out of date [#130](https://github.com/broofa/mime/issues/130)
+- [**closed**] how to support plist? [#126](https://github.com/broofa/mime/issues/126)
+- [**closed**] how does .types file format look like? [#123](https://github.com/broofa/mime/issues/123)
+- [**closed**] Feature: support for expanding MIME patterns [#121](https://github.com/broofa/mime/issues/121)
+- [**closed**] DEBUG_MIME doesn't work [#117](https://github.com/broofa/mime/issues/117)
+
+---
+
+### v1.3.4 (06/02/2015)
+*No changelog for this release.*
+
+---
+
+### v1.3.3 (06/02/2015)
+*No changelog for this release.*
+
+---
+
+### v1.3.1 (05/02/2015)
+- [**closed**] Consider adding support for Handlebars .hbs file ending [#111](https://github.com/broofa/mime/issues/111)
+- [**closed**] Consider adding support for hjson. [#110](https://github.com/broofa/mime/issues/110)
+- [**closed**] Add mime type for Opus audio files [#94](https://github.com/broofa/mime/issues/94)
+- [**closed**] Consider making the `Requesting New Types` information more visible [#77](https://github.com/broofa/mime/issues/77)
+
+---
+
+## v1.3.0 (05/02/2015)
+- [**closed**] Add common name? [#114](https://github.com/broofa/mime/issues/114)
+- [**closed**] application/x-yaml [#104](https://github.com/broofa/mime/issues/104)
+- [**closed**] Add mime type for WOFF file format 2.0 [#102](https://github.com/broofa/mime/issues/102)
+- [**closed**] application/x-msi for .msi [#99](https://github.com/broofa/mime/issues/99)
+- [**closed**] Add mimetype for gettext translation files [#98](https://github.com/broofa/mime/issues/98)
+- [**closed**] collaborators [#88](https://github.com/broofa/mime/issues/88)
+- [**closed**] getting errot in installation of mime module...any1 can help? [#87](https://github.com/broofa/mime/issues/87)
+- [**closed**] should application/json's charset be utf8? [#86](https://github.com/broofa/mime/issues/86)
+- [**closed**] Add "license" and "licenses" to package.json [#81](https://github.com/broofa/mime/issues/81)
+- [**closed**] lookup with extension-less file on Windows returns wrong type [#68](https://github.com/broofa/mime/issues/68)
+
+---
+
+### v1.2.11 (15/08/2013)
+- [**closed**] Update mime.types [#65](https://github.com/broofa/mime/issues/65)
+- [**closed**] Publish a new version [#63](https://github.com/broofa/mime/issues/63)
+- [**closed**] README should state upfront that "application/octet-stream" is default for unknown extension [#55](https://github.com/broofa/mime/issues/55)
+- [**closed**] Suggested improvement to the charset API [#52](https://github.com/broofa/mime/issues/52)
+
+---
+
+### v1.2.10 (25/07/2013)
+- [**closed**] Mime type for woff files should be application/font-woff and not application/x-font-woff [#62](https://github.com/broofa/mime/issues/62)
+- [**closed**] node.types in conflict with mime.types [#51](https://github.com/broofa/mime/issues/51)
+
+---
+
+### v1.2.9 (17/01/2013)
+- [**closed**] Please update "mime" NPM [#49](https://github.com/broofa/mime/issues/49)
+- [**closed**] Please add semicolon [#46](https://github.com/broofa/mime/issues/46)
+- [**closed**] parse full mime types [#43](https://github.com/broofa/mime/issues/43)
+
+---
+
+### v1.2.8 (10/01/2013)
+- [**closed**] /js directory mime is application/javascript. Is it correct? [#47](https://github.com/broofa/mime/issues/47)
+- [**closed**] Add mime types for lua code. [#45](https://github.com/broofa/mime/issues/45)
+
+---
+
+### v1.2.7 (19/10/2012)
+- [**closed**] cannot install 1.2.7 via npm [#41](https://github.com/broofa/mime/issues/41)
+- [**closed**] Transfer ownership to @broofa [#36](https://github.com/broofa/mime/issues/36)
+- [**closed**] it's wrong to set charset to UTF-8 for text [#30](https://github.com/broofa/mime/issues/30)
+- [**closed**] Allow multiple instances of MIME types container [#27](https://github.com/broofa/mime/issues/27)
diff --git a/node_modules/mime/LICENSE b/node_modules/mime/LICENSE
new file mode 100644
index 00000000..d3f46f7e
--- /dev/null
+++ b/node_modules/mime/LICENSE
@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2010 Benjamin Thomas, Robert Kieffer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
diff --git a/node_modules/mime/Mime.js b/node_modules/mime/Mime.js
new file mode 100644
index 00000000..7fe39211
--- /dev/null
+++ b/node_modules/mime/Mime.js
@@ -0,0 +1,95 @@
+'use strict';
+
+/**
+ * @param typeMap [Object] Map of MIME type -> Array[extensions]
+ * @param ...
+ */
+function Mime() {
+ this._types = Object.create(null);
+ this._extensions = Object.create(null);
+
+ for (var i = 0; i < arguments.length; i++) {
+ this.define(arguments[i]);
+ }
+
+ this.define = this.define.bind(this);
+ this.getType = this.getType.bind(this);
+ this.getExtension = this.getExtension.bind(this);
+}
+
+/**
+ * Define mimetype -> extension mappings. Each key is a mime-type that maps
+ * to an array of extensions associated with the type. The first extension is
+ * used as the default extension for the type.
+ *
+ * e.g. mime.define({'audio/ogg', ['oga', 'ogg', 'spx']});
+ *
+ * If a type declares an extension that has already been defined, an error will
+ * be thrown. To suppress this error and force the extension to be associated
+ * with the new type, pass `force`=true. Alternatively, you may prefix the
+ * extension with "*" to map the type to extension, without mapping the
+ * extension to the type.
+ *
+ * e.g. mime.define({'audio/wav', ['wav']}, {'audio/x-wav', ['*wav']});
+ *
+ *
+ * @param map (Object) type definitions
+ * @param force (Boolean) if true, force overriding of existing definitions
+ */
+Mime.prototype.define = function(typeMap, force) {
+ for (var type in typeMap) {
+ var extensions = typeMap[type].map(function(t) {return t.toLowerCase()});
+ type = type.toLowerCase();
+
+ for (var i = 0; i < extensions.length; i++) {
+ var ext = extensions[i];
+
+ // '*' prefix = not the preferred type for this extension. So fixup the
+ // extension, and skip it.
+ if (ext[0] == '*') {
+ continue;
+ }
+
+ if (!force && (ext in this._types)) {
+ throw new Error(
+ 'Attempt to change mapping for "' + ext +
+ '" extension from "' + this._types[ext] + '" to "' + type +
+ '". Pass `force=true` to allow this, otherwise remove "' + ext +
+ '" from the list of extensions for "' + type + '".'
+ );
+ }
+
+ this._types[ext] = type;
+ }
+
+ // Use first extension as default
+ if (force || !this._extensions[type]) {
+ var ext = extensions[0];
+ this._extensions[type] = (ext[0] != '*') ? ext : ext.substr(1)
+ }
+ }
+};
+
+/**
+ * Lookup a mime type based on extension
+ */
+Mime.prototype.getType = function(path) {
+ path = String(path);
+ var last = path.replace(/^.*[/\\]/, '').toLowerCase();
+ var ext = last.replace(/^.*\./, '').toLowerCase();
+
+ var hasPath = last.length < path.length;
+ var hasDot = ext.length < last.length - 1;
+
+ return (hasDot || !hasPath) && this._types[ext] || null;
+};
+
+/**
+ * Return file extension associated with a mime type
+ */
+Mime.prototype.getExtension = function(type) {
+ type = /^\s*([^;\s]*)/.test(type) && RegExp.$1;
+ return type && this._extensions[type.toLowerCase()] || null;
+};
+
+module.exports = Mime;
diff --git a/node_modules/mime/README.md b/node_modules/mime/README.md
new file mode 100644
index 00000000..81c57495
--- /dev/null
+++ b/node_modules/mime/README.md
@@ -0,0 +1,187 @@
+
+# Mime
+
+A comprehensive, compact MIME type module.
+
+[](https://travis-ci.org/broofa/mime)
+
+## Version 2 Notes
+
+Version 2 is a breaking change from 1.x as the semver implies. Specifically:
+
+* `lookup()` renamed to `getType()`
+* `extension()` renamed to `getExtension()`
+* `charset()` and `load()` methods have been removed
+
+If you prefer the legacy version of this module please `npm install mime@^1`. Version 1 docs may be found [here](https://github.com/broofa/mime/tree/v1.4.0).
+
+## Install
+
+### NPM
+```
+npm install mime
+```
+
+### Browser
+
+It is recommended that you use a bundler such as
+[webpack](https://webpack.github.io/) or [browserify](http://browserify.org/) to
+package your code. However, browser-ready versions are available via wzrd.in.
+E.g. For the full version:
+
+
+
+
diff --git a/public/js/scripts.js b/public/js/scripts.js
index de052eae..88ebf121 100755
--- a/public/js/scripts.js
+++ b/public/js/scripts.js
@@ -1,3 +1,69 @@
// Add some Javascript code here, to run on the front end.
-console.log("Welcome to assignment 2!")
\ No newline at end of file
+console.log("Welcome to assignment 2!")
+
+
+/*
+let playerList = []
+let listOrder = {
+ "nickname": 0,
+ "Username": 1,
+ "Password": 2,
+ "Foot": 3,
+ "Positon": 4,
+ "dateJoined": 5,
+}
+
+function deleteItem(id) {
+
+ let entry = document.getElementById(id)
+
+ fetch( 'delete', {
+ method:'POST',
+ body: JSON.stringify({id: id})
+ }).then( function( response) {
+ if(response.status === 200) {
+ alert("Successfully removed");
+ entry.remove();
+ }
+ else {
+ alert("Entry was not removed successfully, try again!")
+ }
+ })
+}
+
+function createUser() {
+ let table = docuent.getElementById('players')
+ fetch('/playerLink',{
+ method:'POST'
+ }).then( function(response) {
+ return response.text();
+}).then(function(text){
+ JSON.parse(text).forEach(item =>{
+ let row = table.insertRow(-1);
+ let id = item.id;
+
+ row.id = id;
+
+ for(let key in listOrder) {
+ let cell = row.insertCell(listOrder[key]);
+ if( item[key] === -1) {
+ cell.innerHTML = 'HIDDEN'
+ cell.classList.add('hidden');
+ }
+ else {
+ cell.innerHTML = item[key];
+ }
+ }
+
+ let deleteButton = document.createElement('button');
+ deleteButton.innerText = "Delete User"
+ deleteButton.onClick = (() => deleteItem(id));
+ let buttonCell = row.insertCell(6);
+ buttonCell.appendChild(deleteButton);
+ });
+})
+}
+
+createUser();
+*/
diff --git a/public/players.html b/public/players.html
new file mode 100644
index 00000000..3db737e2
--- /dev/null
+++ b/public/players.html
@@ -0,0 +1,41 @@
+
+
+
+ Registered Players
+
+
+
+
+
+
+
+