From dac4d0b3a05af3c836fe8faf7711aacc33c70c07 Mon Sep 17 00:00:00 2001
From: sidneygoldinger <98048123+sidneygoldinger@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:36:07 -0400
Subject: [PATCH 01/15] Update README.md
---
README.md | 51 ++++++++-------------------------------------------
1 file changed, 8 insertions(+), 43 deletions(-)
diff --git a/README.md b/README.md
index 9b56c216f..db439ac13 100644
--- a/README.md
+++ b/README.md
@@ -1,49 +1,14 @@
-# Final Project
-*Due October 13th (final day of the term)*
-
-For your final project, you'll implement a web application that exhibits understanding of the course materials.
-This project should provide an opportunity to both be creative and to pursue individual research and learning goals.
-
-## General description
-Your project should consist of a complete Web application, exhibiting facets of the three main sections of the course material:
-
-- Static web page content and design. You should have a project that is accessible, easily navigable, and features significant content.
-- Dynamic behavior implemented with JavaScript (TypeScript is also allowed if your group wants to explore it).
-- Server-side programming *using Node.js*. Typically this will take the form of some sort of persistent data (database), authentication, and possibly server-side computation.
-- A video (less than five minutes) where each group member explains some aspect of the project. An easy way to produce this video is for you all the groups members to join a Zoom call that is recorded; each member can share their screen when they discuss the project or one member can "drive" the interface while other members narrate (this second option will probably work better.) The video should be posted on YouTube or some other accessible video hosting service. Make sure your video is less than five minutes, but long enough to successfully explain your project and show it in action. There is no minimum video length.
-
-## Project ideation
-Excellent projects typically serve someone/some group; for this assignment you need to define your users and stakeholders. I encourage you to identify projects that will have impact, either artistically, politically, or in terms of productivity.
-
-### Deliverables
-
-#### Form Team (due 9/25)
-Students are will work in teams of 3-5 students for the project; teams of two can be approved with the permission of the instructor. Working in teams should help enable you to build a good project in a limited amount of time. Use the `#project-logistics` channel in Discord to pitch ideas for final projects and/or find fellow team members as needed.
-
-Teams must be in place by end of day on Sunday, September 25th. If you have not identified a team at this point, you will be assigned a team. You will be given some class time on Monday to work on your proposal, but please plan on reserving additional time outside of class as needed.
-
-#### Proposal (due 9/27)
-Provide an outline of your project direction and the names of associated team members.
-The outline should have enough detail so that staff can determine if it meets the minimum expectations, or if it goes too far to be reasonable by the deadline. Please include a general description of a project, and list of key technologies/libraries you plan on using (e.g. React, Three.js, Svelte, TypeScript etc.). Two to four paragraps should provide enough level of detail. Name the file proposal.md and submit a pull request by Tuesday, September 27th at 11:59 PM (end of day). Only one pull request is required per team.
-
-There are no other scheduled checkpoints for your project.
-
-#### Turning in Your Project
-Submit a second PR on the final project repo to turn in your app and code. Again, only one pull request per team.
-
-Deploy your app, in the form of a webpage, to Glitch/Heroku/Digital Ocean or some other service; it is critical that the application functions correctly wherever you post it.
-
-The README for your second pull request doesn’t need to be a formal report, but it should contain:
-
+#README
1. A brief description of what you created, and a link to the project itself (two paragraphs of text)
+ Link: https://final-project-lnbsr.glitch.me/
+ Description: We created a website on which a user can login and view playlists of the top songs of various genres. They can also add songs to each genre, as well as upvote or downvote individual songs. Users can register, and the songs/votes data is persistent between sessions and users.
2. Any additional instructions that might be needed to fully use your project (login information etc.)
+ Additional Instructions: The project is rather user-friendly. To Register, click the register button to go to the register page, enter your new username and password, and click register again. To sign in, click Sign In, enter your username and password, and click Sign In again. Once signed in, you can view the playlists of songs, and can upvote/downvote songs, as well as click the Add Song button to add a new song to its respective playlist.
3. An outline of the technologies you used and how you used them.
+ We used MongoDB for a database, as well as bootstrap for CSS. We also used express for server-frontend communication. We also used Node.js for the server.
4. What challenges you faced in completing the project.
+ Lexie and Benjamin ran into a number of errors redirecting from the login to the top page. Sidney and Nadiyah ran into some issues finding a good way of showing all the playlists on the same page, as well as showing the songs in tables rather than lists. Ryan ran into some issues getting server communication to work with her page.
5. What each group member was responsible for designing / developing.
+ Benjamin took the lead on creating the server side code and communication with the database. Lexie did the Login page. Sidney and Nadiyah made the Top Songs page. Ryan created the Add Songs page.
6. A link to your project video.
-
-Think of 1,3, and 4 in particular in a similar vein to the design / tech achievements for A1—A4… make a case for why what you did was challenging and why your implementation deserves a grade of 100%.
-
-## FAQs
-
-- **Can I use XYZ framework?** You can use any web-based frameworks or tools available, but for your server programming you need to use Node.js. Your client-side scripting language should be either JavaScript or TypeScript.
+ Video: https://youtu.be/-gz7nBQKlts
From 7cfed760428d026f8defaada416678c0fe0c046b Mon Sep 17 00:00:00 2001
From: sidneygoldinger <98048123+sidneygoldinger@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:36:21 -0400
Subject: [PATCH 02/15] Update README.md
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index db439ac13..165b9bd59 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-#README
+README
1. A brief description of what you created, and a link to the project itself (two paragraphs of text)
Link: https://final-project-lnbsr.glitch.me/
Description: We created a website on which a user can login and view playlists of the top songs of various genres. They can also add songs to each genre, as well as upvote or downvote individual songs. Users can register, and the songs/votes data is persistent between sessions and users.
From f3fc9449a7f0dc08a04332998ce58e1f0ba35079 Mon Sep 17 00:00:00 2001
From: sidneygoldinger <98048123+sidneygoldinger@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:37:03 -0400
Subject: [PATCH 03/15] Update README.md
---
README.md | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/README.md b/README.md
index 165b9bd59..7b049d437 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,26 @@
README
+
1. A brief description of what you created, and a link to the project itself (two paragraphs of text)
+
Link: https://final-project-lnbsr.glitch.me/
+
Description: We created a website on which a user can login and view playlists of the top songs of various genres. They can also add songs to each genre, as well as upvote or downvote individual songs. Users can register, and the songs/votes data is persistent between sessions and users.
+
2. Any additional instructions that might be needed to fully use your project (login information etc.)
+
Additional Instructions: The project is rather user-friendly. To Register, click the register button to go to the register page, enter your new username and password, and click register again. To sign in, click Sign In, enter your username and password, and click Sign In again. Once signed in, you can view the playlists of songs, and can upvote/downvote songs, as well as click the Add Song button to add a new song to its respective playlist.
+
3. An outline of the technologies you used and how you used them.
We used MongoDB for a database, as well as bootstrap for CSS. We also used express for server-frontend communication. We also used Node.js for the server.
+
4. What challenges you faced in completing the project.
+
Lexie and Benjamin ran into a number of errors redirecting from the login to the top page. Sidney and Nadiyah ran into some issues finding a good way of showing all the playlists on the same page, as well as showing the songs in tables rather than lists. Ryan ran into some issues getting server communication to work with her page.
+
5. What each group member was responsible for designing / developing.
+
Benjamin took the lead on creating the server side code and communication with the database. Lexie did the Login page. Sidney and Nadiyah made the Top Songs page. Ryan created the Add Songs page.
+
6. A link to your project video.
+
Video: https://youtu.be/-gz7nBQKlts
From 359b723e79b4d83ab1f9f5d7ed3510cdd334073b Mon Sep 17 00:00:00 2001
From: sidneygoldinger <98048123+sidneygoldinger@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:37:24 -0400
Subject: [PATCH 04/15] Update README.md
---
README.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/README.md b/README.md
index 7b049d437..606350e5b 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,7 @@ README
Additional Instructions: The project is rather user-friendly. To Register, click the register button to go to the register page, enter your new username and password, and click register again. To sign in, click Sign In, enter your username and password, and click Sign In again. Once signed in, you can view the playlists of songs, and can upvote/downvote songs, as well as click the Add Song button to add a new song to its respective playlist.
3. An outline of the technologies you used and how you used them.
+
We used MongoDB for a database, as well as bootstrap for CSS. We also used express for server-frontend communication. We also used Node.js for the server.
4. What challenges you faced in completing the project.
From 5edc2154efcf53539392d25e9e6b00e3e137b04c Mon Sep 17 00:00:00 2001
From: sidneygoldinger <98048123+sidneygoldinger@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:38:34 -0400
Subject: [PATCH 05/15] Create client.js
---
public/client.js | 89 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 89 insertions(+)
create mode 100644 public/client.js
diff --git a/public/client.js b/public/client.js
new file mode 100644
index 000000000..0ec06833b
--- /dev/null
+++ b/public/client.js
@@ -0,0 +1,89 @@
+
+
+
+
+ Submit
+
+
+
+
+
+
Submit a Song
+
+ Enter the song's genre ('Rap', 'Pop', 'R&B', 'Rock', or 'Country'), along
+ with the song's title and artist
+
+ This is the Glitch Hello Node project. You can
+ use it to build your own app. Check out README.md in the editor for
+ more info and next steps you can take!
+