Delete unecessary files

README.md

@@ -1,2 +1,48 @@
-# HangmanGame
-This repository contains the files for execution of a web application to play the Hangman Game
+# Hangman
+
+## Game Objective and Rules
+In the spirit of Halloween, we've spookified this classic game with an educational twist! The objective of our ghoulishly fun game is to enhance the players' knowledge of Computer Science while enjoying the experience of doing so. To add to the excitement, we've crafted three levels of difficulty: Beginner, Intermediate, and Expert, ensuring a hauntingly good time for all.
+
+- You can choose your preferred difficulty level: Beginner, Intermediate, and Expert. After choosing the levels you will be presented with questions related to the field of Computer Science.
+- The goal is to guess the correct response to the question and save the hangman from being hanged.
+- Select an option among the four presented, that you think answers the question correctly.
+- If you guess the answer right, you will learn more about the topic and the question changes.
+- If your guess is wrong, the hangman image changes adding an element of suspense and challenge.
+- Keep guessing until you've either answered all the questions correctly or run out of attempts.
+- Learn more about Computer Science while having fun!
+
+## Technology stacks used
+- HTML
+- CSS
+- JavaScript
+- API for generating questions
+
+## Setup Instructions
+1. Clone this repository to your local machine.
+2. Open the 'index.html' file in your browser.
+3. Start playing the game and enjoy educating and informative experience.
+
+## Credits
+- Computer Science related sourced from the API endpoint for the Open Trivia Database (OpenTDB) API - [Link](https://opentdb.com/api.php?amount=10&category=18&difficulty)
+
+## What worked
+- Collaboration of our team: This team assignment brought together students with diverse skills and perspectives. This collaborative effort allowed us to tackle various aspects of this project efficiently.
+- API Integration: To provide the questions related to Computer Science for users to learn, we decided to integrate an API. The instance where this decision was extremely helpful was when we decided to create a feature for the user to select the desired difficulty level (Beginner, Intermediate, Hard) which is a feature that enhanced the educational aspect of our game. This decision made the task relatively easy, which contributed to catering our game to users with varying levels of expertise thus broadening our game's audience. 
+- Continuous gameplay sessions: One of the key success factors in refining the gaming experience is, playing the game among the team. By playing the game ourselves, we identified areas for improvement on the UI, that range from UI tweaks to better phrasing and making the UI seamless. We gathered feedback and made real-time changes resulting in a more enjoyable user experience.
+- Effective communication: There were a few moments where we had debates about the layout of the interface. Though among the team we had different perspectives regarding design approaches, we had open communication with each other and took everyone's thoughts as input to help improve the development process iteratively. This taught each one of us the power of communication and compromise.
+- Task Breakdown: Breaking down the assignment into smaller tasks contributed to our careful planning and was helpful in assigning the work to teammates effectively. We divided the tasks based on everyone's interests and strengths. Our team made sure that every aspect of this project received attention.
+
+## Challenges faced
+- Managing the API requests and responses was challenging for our team, this called for dynamic planning to stay on track. One situation was where we attempted to fetch numerous questions at once which led to a noticeable lag in loading times. This taught us the importance of optimizing API requests.
+- Error handling was also burdensome as we had issues with undesired responses from the API. To maintain a seamless experience throughout the game, we had to work on it and perform testing and debugging multiple times.
+- Schedule conflicts among the team due to academic commitments which interrupted us to meet up and discuss the progress of the project. To overcome it we sometimes preferred virtual meetings or postponed it till everyone was available. This made us understand the need for adaptability in a team setting.
+- Conflicting opinions regarding the game's layout, and UI's color palette which were resolved by discussing the pros and cons of each. We managed to reach an open ground for all of them through discussions and communicating our thoughts clearly. Rather than considering the differences in perspectives as a weakness, this experience has taught us that they can be a source of strength as well.
+
+## Lessons learned
+- For developing a project, teamwork plays a crucial role This was our first lesson when we initially started on our project.  This teamwork brought out the best in each of us.
+ This experience also made us realize how strong each one of us is, in working as a team. We also realized that by leveraging our individual strengths, we can achieve more collectively. 
+- We discovered how gaming can be a powerful tool to be informative.
+- Working our way through the API is a skill worth learning. Though initially, we struggled with integrating the API, we overcame it by learning the importance of optimizing API requests.
+- User feedback is crucial for any project development. Having knowledge about real-time player/user feedback can be a way to enhance the functionalities or the adding changes to the UI design which will help the developer refine the project.
+- A collaborative working environment enhances the developer's creative synergy which leads to innovative thoughts to resolve the problem at hand. While brainstorming, we explored several ideas and perspectives which made the developing process more interesting.
+- We have learned how Agile methodology helps in addressing the issues adeptly. Whenever we find an issue, we have adapted a development plan to fix it.

main.html

@@ -8,8 +8,8 @@
     <link rel="stylesheet" href="styles.css">
     <style>
         body {
-            background-image: linear-gradient(rgba(233, 142, 13, 0.8), rgba(255,255,255,0.5)), url('images/spider.jpg');
-            background-size: cover;
+            background-image: linear-gradient(rgb(237, 234, 227,0), rgba(255,255,255,1)), url('images/board.png');
+            background-size: 100% 90%;
             background-repeat: no-repeat;
             background-position: center;
             margin: 0;

styles.css

@@ -53,10 +53,10 @@ video {
     background: -webkit-linear-gradient(black, beige);
     -webkit-background-clip: text;
     -webkit-text-fill-color: black;
-    font-size: 105px;
-    font-weight: bolder;
+    font-size: 205px;
+    font-weight: 800;
     font-family: 'Poppins', sans-serif;
-    letter-spacing: 15px;
+    letter-spacing: 0px;
     z-index: 2;
 }
 
@@ -403,9 +403,9 @@ margin-top: 50%;
 }
 
 .option.selected {
-    background-color:#20aaff; /* Change the background color for selected options */
-    color: #fff; /* Change the text color for selected options */
-    font-weight: bold; /* Make the text bold for selected options */
+    background-color:#20aaff; 
+    color: #fff; 
+    font-weight: bold; 
 }
 
 .correct{